MCP Observatory: one read only walk over every https endpoint in the official registry
Public record of one read only walk over the official MCP registry: who answered, tools, who pays.
¿Debería usar esto?
Calidad y seguridad
Hallazgos (1)
- LOWTool 'mcp_observatory_disclosure_guide' name length outside 3-30 rangeen mcp_observatory_disclosure_guide
Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.
Costo de contexto
Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.
Instalar
Instalación con un clic
Agrega esto a tu archivo `claude_desktop_config.json`:
{
"mcpServers": {
"hs-mcp-observatory": {
"url": "https://observatory.horizonshield.dev/mcp"
}
}
}Puntos de conexión remotos
https://observatory.horizonshield.dev/mcpstreamable-httpQué puede hacer
Inventario de herramientas
Herramientas (6)
🟢mcp_observatory_state
What was measured, when, over what population, and what the measurement cannot tell you. Read this before quoting any number from this server.
Esquema de entrada
{
"type": "object",
"properties": {}
}⚪mcp_observatory_summary
The counts, as published and as corrected. How many addresses answered, how many tools they exposed, how many stated who compensates their operator.
Esquema de entrada
{
"type": "object",
"properties": {}
}⚪mcp_observatory_lookup(address, host)
What happened when we contacted one address, or an aggregate for one host. Returns the record hash and the procedure to recompute it. There is no tool here that lists addresses; you must already hold the one you are asking about.
Esquema de entrada
{
"type": "object",
"properties": {
"address": {
"type": "string",
"description": "The full declared endpoint, e.g. https://example.com/mcp"
},
"host": {
"type": "string",
"description": "A host, e.g. example.com. Returns counts for that host, not a roster."
}
}
}⚪mcp_observatory_disclosure_guide
How the 152 servers that stated who compensates their operator actually did it - the field names observed in the wild, with counts. Not a specification we invented.
Esquema de entrada
{
"type": "object",
"properties": {}
}🟡mcp_observatory_measure_now(address)
Contact one https address now and report what we see: whether it speaks MCP, whether it carries an agent card, and whether that card names who compensates the operator. Read only; no tool is called. robots.txt is read first and honoured. This does NOT change the published record - the next full walk does that. Rate limited, because it contacts somebody else's server on your behalf.
Esquema de entrada
{
"type": "object",
"properties": {
"address": {
"type": "string",
"description": "https endpoint, e.g. https://example.com/mcp"
}
},
"required": [
"address"
]
}⚪mcp_observatory_method
How the walk was run, what we got wrong and corrected, and the four rules the report holds itself to.
Esquema de entrada
{
"type": "object",
"properties": {}
}Comunidad
Evidencia