Register an MCP Server

This guide registers an MCP server, sets its trust and classification, and approves it.

1. Register the 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": "github-mcp",
    "owner": "[email protected]",
    "endpointUrl": "https://mcp.company.com/github",
    "authMethod": "OAUTH",
    "environment": "PRODUCTION",
    "exposedTools": "create_issue, list_repos, read_file",
    "trustLevel": "INTERNAL",
    "securityClassification": "INTERNAL",
    "approvalStatus": "PENDING",
    "healthStatus": "HEALTHY"
  }'

Capture the returned mcpId. New servers default to PENDING and surface in Discovery.

2. Review and approve#

curl -X PUT "https://your-company.authspoke.com/api/v1/ai/mcp-servers/$MCP_ID" \
  -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  -d '{ "name": "github-mcp", "approvalStatus": "APPROVED", "trustLevel": "VERIFIED" }'

3. Confirm it's governed#

curl "https://your-company.authspoke.com/api/v1/ai/mcp-servers" -H "Authorization: Bearer $TOKEN"

Once approved with a non-UNTRUSTED trust level, the server drops out of the shadow-AI view and counts toward your governed estate.

Tips#

• Keep exposedTools accurate — it feeds the Relationships graph and risk context.
• Classify honestly. RESTRICTED servers reaching sensitive systems should be VERIFIED and tightly owned.

See the MCP Registry API for every field.