MCP server

Vendorica ships a Model Context Protocol server, so an AI agent can read your compliance posture, controls, vendors and incidents as tools rather than by you pasting exports into a chat window.

POST https://api.vendorica.com/mcp

Stateless Streamable HTTP, plain JSON responses. Every request is a complete JSON-RPC exchange — there is no session to keep alive and nothing to reconnect.

Note

Professional and Enterprise. On other plans the endpoint authenticates and then returns 402 BILLING_FEATURE_REQUIRED — the request was understood and the credential was valid; the plan is what refused it.

Two ways to authenticate

Both resolve to the same principal, and both carry your organization’s scopes.

Credential	Looks like	Use it for
API key	vnd_live_…	your own agents and scripts
OAuth access token	vnd_mcp_at_…	connecting a hosted assistant

For the OAuth path the server implements discovery, dynamic client registration and PKCE, so a client that speaks MCP can connect without anyone pre-registering it:

GET /.well-known/oauth-authorization-server
POST /mcp/oauth/register
GET  /mcp/oauth/authorize     ← the human consents here
POST /mcp/oauth/token

A 401 from POST /mcp carries a WWW-Authenticate header pointing at the protected-resource metadata, which is how a client discovers where to authorize. That header is part of the contract, not an implementation detail.

The tools

Tool	What it answers
get_compliance_posture	overall readiness, by framework
get_control_status	one control in full, or a search by name — status, owner, domain, and the framework citations it satisfies
query_vendor_risk	vendors with their open risk scenarios, scores and approval status
search_regulatory_requirements	the regulatory knowledge base
get_incident_context	one incident: classification, severity, status, reporter, timeline
run_gap_analysis	per-citation gaps for a framework, worst first, with the counts behind each score
get_audit_evidence	evidence for a control — automated test results and manual uploads together
draft_policy	a policy draft grounded in the knowledge base, returned with its citations

Plus resources for the regulatory texts themselves:

regulation://dora/articles
regulation://mica/articles

What an agent can and cannot do

Scopes bind the agent exactly as they bind a key. A tool call runs with the scopes of the credential behind it, so a read-only key stays read-only through MCP. get_audit_evidence additionally excludes evidence flagged sensitive for agent connections.

draft_policy does not save anything. It returns markdown and the citations it was grounded in; a human reviews it and creates the policy in Vendorica. AI suggests, people confirm — and that boundary is in the server, not in a prompt.

Every tool call is logged. Each invocation writes an audit row, and an OAuth-token call also records the human who granted the connection, so “the agent did it” is never the end of the trail.

Rate limit

120/min, keyed per client — deliberately tighter than the /v1 read budget because one tool call fans out into several kernel queries. Not overridable. See rate limits.