Usage policy for the
MCP

Crosses: the public teaser of every mandate and your own authenticated account data —your alerts, your pipeline, your NDA requests and your processes, and if you are an adviser, your firm’s mandates and analytics—.

Never crosses: any data-room document, the content of messaging (only the message count and the date of the last one), or another person’s identity or contact details —name, email or phone of an investor, seller or adviser who is not you—.

Nothing with legal effect is executed through the MCP: requesting, approving or rejecting an NDA only return the information and a link to godeal.es, where you complete it with your own session. Nor is a mandate published, a listing approved or a role changed through here.

Every low-risk write —saving an alert, writing in a deal room with an already approved NDA, requesting a teaser draft— follows the same pattern: the first call only shows the exact proposal, writing nothing, and a second, explicit call is needed for it to run.

The access token lasts one hour; the refresh token, 30 days, and it rotates on every use. Dead OAuth artefacts —expired codes, revoked or expired tokens, registered clients that never reached a grant— are purged after 30 days.

From godeal.es/cuenta/conexiones you see which clients have access, with what permissions and when they were last used, and revoke them whenever you want. Revocation takes effect on the client’s next call.

Every tool call is logged: who, when, with which client and grant, which tool, and whether it succeeded or failed. The call’s arguments and its response are never stored.

Whoever acts through the MCP is you, with your own role and your own permissions —the same row-level protection as on the web—. GoDeal never uses the service key to serve an authenticated MCP call.