MCP Registry
Register and govern MCP servers as first-class AI resources — tools, trust level, classification, approval and health.
The MCP Registry is the enterprise catalog for your AI infrastructure. Every MCP server an agent can call is a governed resource with an owner, exposed tools, trust level and approval state.
The MCP server model#
| Field | Notes |
|---|---|
name, description, owner | Identity and accountability. |
endpointUrl | Where the server lives. |
authMethod | OAUTH · API_KEY · MTLS · NONE. |
environment | DEVELOPMENT · STAGING · PRODUCTION. |
exposedTools | Comma-separated tool names the server publishes. |
trustLevel | UNTRUSTED · INTERNAL · VERIFIED. |
securityClassification | PUBLIC · INTERNAL · CONFIDENTIAL · RESTRICTED. |
approvalStatus | PENDING · APPROVED · REJECTED. |
healthStatus | HEALTHY · DEGRADED · DOWN · UNKNOWN. |
Register a server#
curl -X POST "https://your-company.authspoke.com/api/v1/ai/mcp-servers" \
-H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
-d '{
"name": "sap-mcp",
"owner": "[email protected]",
"endpointUrl": "https://mcp.company.com/sap",
"authMethod": "MTLS",
"environment": "PRODUCTION",
"exposedTools": "read_invoice, post_ledger, list_vendors",
"trustLevel": "VERIFIED",
"securityClassification": "RESTRICTED",
"approvalStatus": "APPROVED"
}'
Approval workflow#
New servers default to PENDING. They surface in Discovery until a provider or admin approves them. Approve by updating approvalStatus to APPROVED — which emits an audit event.
Why register MCP servers#
Registration makes the relationship explicit: which agents call which servers, exposing which tools, reaching which data. That powers the Relationships graph and contributes to each agent's risk score.
API#
See the MCP Registry API.