Reference Source · MCP server health

sh.agentbeacon/agentbeacon

AgentBeacon: create a live beacon about what you have or need; any AI agent can find and message it.

2 endpoints on the official MCP registry. Probed at most once every 7 days.

https://api.agentbeacon.sh/mcp/search

answered, tools listed

Last 30 probes
Last seen healthy2026-11-15
Completed sessions— of our visits in the last 7 days · 95.7% in the last 30
Handshake latencymedian 228 ms, 95th 452 ms
Tools listed2
Tool contractc04f88e0fe14 — last moved 2026-10-26 (1 changed in place, against 2026-10-25), and on 2 of the days probed
Protocol answered2025-06-18
Transportstreamable-http

https://api.agentbeacon.sh/mcp

needs credentials

Last 30 probes
Last seen healthynot once, in the days we have probed
Completed sessions— of our visits in the last 7 days · 0% in the last 30
Handshake latencymedian 208 ms, 95th 479 ms
Tools listed—
Protocol answered—
Transportstreamable-http
Last detailHTTP 401

Embed the badge

[![MCP](https://referencesource.org/mcp-health/badge/sh-agentbeacon-agentbeacon.svg)](https://referencesource.org/mcp-health/server/sh-agentbeacon-agentbeacon/)

The badge shows the most recent probe. It is generated from the same file this page is, updates after each day's pass, and needs no key. This entry publishes 2 endpoints, and the badge reports the best result among them — the question a badge answers is whether a client can reach this project at all, and one dead spare URL is not a reason to call the project down. The per-endpoint verdicts are above, each with its own link.

What was actually measured

One HTTP POST carrying a JSON-RPC initialize, and if that succeeds, a tools/list. Nothing here is a score, a rating or a judgement about whether the server is any good — only whether an ordinary MCP client could complete a session with it on the day we asked. “Needs credentials” is not a fault: it means the endpoint wants an account, which is a perfectly reasonable thing for it to want.

The tool contract row is a digest of what tools/list returned — each tool's name, description and input schema, hashed — so that a rename, a newly-required field or a rewritten description can be spotted even though none of them breaks the connection. We keep the digests and nothing else: no tool name, description or schema of anybody's is stored or republished here, which is also why this can say that a contract moved and by how much, but not what it now says.

The method and the day-by-day totals · every server we probe, A–Z · feed.json · licence · corrections and removals: contact@referencesource.org