Enrich your MCP servers and agents with custom metadata for organization, compliance tracking, and integration purposes. All metadata is fully searchable via semantic search.
{
"team": "data-platform",
"owner": "alice@example.com",
"department": "engineering"
}Search by: "team:data-platform servers", "alice@example.com owned services"
{
"compliance_level": "PCI-DSS",
"data_classification": "confidential",
"regulatory_requirements": ["GDPR", "HIPAA"],
"audit_logging": true
}Search by: "PCI-DSS compliant servers", "HIPAA regulated services"
{
"cost_center": "analytics-dept",
"project_code": "AI-2024-Q1",
"budget_allocation": "R&D"
}Search by: "cost center analytics", "project AI-2024-Q1"
{
"deployment_region": "us-east-1",
"environment": "production",
"jira_ticket": "MCPGW-123",
"version": "2.1.0"
}Search by: "us-east-1 deployed services", "JIRA MCPGW-123", "version 2.1.0"
curl -X POST https://registry.example.com/api/services/register \
-H "Content-Type: application/json" \
-d '{
"name": "payment-processor",
"description": "Payment processing service",
"path": "/payment-processor",
"proxy_pass_url": "http://payment:8080",
"metadata": {
"team": "finance-platform",
"owner": "alice@example.com",
"compliance_level": "PCI-DSS",
"cost_center": "finance-ops",
"deployment_region": "us-east-1"
}
}'curl -X POST https://registry.example.com/api/agents/register \
-H "Content-Type: application/json" \
-d '{
"name": "analytics-agent",
"description": "Data analytics agent",
"metadata": {
"team": "data-science",
"owner": "bob@example.com",
"version": "3.2.1",
"cost_center": "analytics-dept"
}
}'# Find servers by team
curl "https://registry.example.com/api/search?q=team:finance-platform"
# Find PCI-DSS compliant services
curl "https://registry.example.com/api/search?q=PCI-DSS compliant services"
# Find services by owner
curl "https://registry.example.com/api/search?q=alice@example.com owned"
# Find services in specific region
curl "https://registry.example.com/api/search?q=us-east-1 deployed"- Flexible Schema: Store any JSON-serializable data (strings, numbers, booleans, nested objects, arrays)
- Fully Searchable: All metadata included in semantic search embeddings
- Backward Compatible: Optional field - existing registrations work without modification
- Type-Safe: Pydantic validation ensures data integrity
- REST API: Full CRUD support via standard API endpoints