Cortex — remote MCP server

The counterparty-relationship system of record, as an MCP connector. Version 0.2.0.

Connect it

Add a custom connector with this URL:

https://cortex-mcp.paymentbrains.com/mcp

You will be asked to sign in with your own Cortex email and password. There is no shared service account: the tools you are offered are the API routes your role can reach, and everything you do is attributed to you in Cortex's audit trail.

No self-signup. An ADMINISTRATION user invites you from the Cortex panel. A first sign-in asks you to set a permanent password; an MFA-enrolled account asks for its authenticator code.

What a connected session gets

Nothing needs to be handed over by an operator. That is the point.

What no role can do here

Every route below exists in the API and has no tool on this surface, whoever you are:

GET /api/v1/credentials/{credentialId}/material
INV-4 and POP-d462 §7.3.
POST /ingress/email
Wrapping an ingress would let a caller forge SYSTEM-attributed captured provenance — a message that reads as something the counterparty sent.
POST /ingress/telegram
Same as /ingress/email — captured provenance must not be forgeable.
DELETE /api/v1/messages/{messageId}
D-418-4(b), operator decision.
POST /api/v1/users
D-418-4(c), operator decision: user management is READS ONLY here.
PUT /api/v1/users/{userId}/role
D-418-4(c).
DELETE /api/v1/users/{userId}
D-418-4(c).

Endpoints