TheLeaf Threat Observatory
ai.theleaf.observatory/threat-observatoryVersion 2.0.0Read-only honeypot observations and evidence. Invite-only API key; request access on our website.
Status
Sign-in required528 msReachable. It asks for authorization, so we did not look inside.- Last checked
- Nov 14, 2026, 13:34 UTC
- Latency
- 528 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://observatory.theleaf.ai/mcpSign-in required528 msAPI key
Claude Code
This server asks for sign-in. Your client opens the sign-in when it connects.
claude mcp add --transport http threat-observatory https://observatory.theleaf.ai/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: threat-observatory
Remote MCP server URL: https://observatory.theleaf.ai/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"threat-observatory": {
"url": "https://observatory.theleaf.ai/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"threat-observatory","type":"http","url":"https://observatory.theleaf.ai/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
Tools are visible after sign-in; we do not look inside protected servers.
Details
- Registry status
- Active
- Published
- Nov 2, 2026
- Updated
- Nov 2, 2026
- Repository
- Not given
- Categories (suggested)
- SecuritySuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared