MCP endpoint for API keys, in the key's organization
const url = 'https://example.com/v1/mcp';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"jsonrpc":"2.0","id":"example","method":"initialize","params":{}}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/v1/mcp \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "jsonrpc": "2.0", "id": "example", "method": "initialize", "params": {} }'The graph as Model Context Protocol tools, and agent proposals for a person to decide (propose_vex, propose_cpe_mapping, propose_unit_release_link, get_proposal and list_proposals, members only for the first three), over stateless Streamable HTTP (protocol version 2026-07-28). One JSON-RPC 2.0 request per POST, answered with one application/json response; no sessions, no server-sent events, no batches. Each request names the version and the client capabilities in params._meta and sends MCP-Protocol-Version, Mcp-Method and (tools/call) Mcp-Name; a missing or different header answers 400 with JSON-RPC error -32020, an unsupported version 400 with -32022 and the supported versions in data. Methods: server/discover, tools/list, tools/call, prompts/list and prompts/get (the workflows assess_release, investigate_vulnerability, triage_product and review_proposals, filtered by role); any other answers 404 with -32601. A request without that _meta is served as protocol 2025-11-25 or 2025-06-18, with initialize and ping as well. Notifications get 202. A request with an Origin header the deployment doesn’t allow answers 403. The API key names the organization; user tokens answer 400 org.required. Bearer credentials only: the session cookie answers 401. OAuth access tokens are refused here (401 with WWW-Authenticate error=“invalid_token” and a detail naming /v1/orgs/{org}/mcp, the only route that takes them); this route’s 401 has no resource_metadata. tools/call is charged to the traversal budget (propose_vex, propose_cpe_mapping and propose_unit_release_link to write, as POST /v1/orgs/{org}/proposals) and a refusal is a tool error request.rateLimited with params budget and retry_after; the other methods are charged to read. Tool errors (isError true) carry the problem codes of the graph and proposal routes in structuredContent (code, params, detail). Requests up to 64 KiB.
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”object
Absent for a notification
object
Responses
Section titled “Responses”The JSON-RPC response, a result or a JSON-RPC error
object
For tools/call: content (one text block composed from our own fields), structuredContent (the graph envelope, GraphResponse) and isError.
object
object
-32700 parse, -32600 invalid request, -32601 unknown method, -32602 invalid params or unknown tool, -32603 internal
Example
{ "jsonrpc": "2.0"}A notification was received; no body
Not a JSON-RPC request, a batch, a missing or mismatched MCP header (-32020), missing _meta fields (-32602) or an unsupported protocol version (-32022); a JSON-RPC error body
Missing or invalid bearer credential, an OAuth access token (use /v1/orgs/{org}/mcp), or the session cookie
An Origin header the deployment doesn’t allow (a JSON-RPC error body)
Another organization’s or no organization (problem details), or, for a 2026-07-28 request, a JSON-RPC method the server doesn’t have (a JSON-RPC error -32601 body)
Any method but POST (GET has no stream to open)
Request body over 64 KiB (a JSON-RPC parse error body)
Over the operation’s rate-limit budget (x-affectra-budget): code request.rateLimited with params.budget. Wait Retry-After seconds before trying again.
Every error answer, Content-Type
application/problem+json. The web app and integrations translate code; detail is English,
for people reading curl output or CI logs, and may change wording at
any time. Match on code, never on detail.
object
The HTTP status
Stable error codes. A code is never renamed; new ones may be added, so
a client falls back to detail for a code it doesn’t know. Another
organization’s object answers notFound, the same as a missing one.
What went wrong
Values the code’s message needs, e.g. {“field”: “version”}. Only values the caller sent or may see. Empty when the message needs none.
object
Example
{ "code": "notFound"}Headers
Section titled “Headers”Seconds until a request would be allowed again, at least 1