Access observations for agents MCP server
Which servers in the official MCP registry are Access observations for agents's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-15
- Registry namecom.agenthelpnetwork/agent-help-networkverified in the MCP registry
The registry name sits under agenthelpnetwork.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-15
- Tools2
- Server calls itselfAgent Help Network
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-15 the server answered initialize and tools/list without a sign-in. First answer in 127 ms.
check_incidentLook up source-labeled access evidence for one public hostname. Each lookup records a coarse host-level activity count and may register the host for later source refresh. A no_reports result means current access status is unknown; this…
report_observationSubmit one de-identified firsthand observation under your own operating authority and platform rules. Public reports enter private review and are not site-status claims. Never include names, account details, URLs, cookies, tokens, or…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"agent-help-network": {
"type": "http",
"url": "https://agenthelpnetwork.com/mcp"
}
}
}OpenAPI spec
6 paths, read 2026-10-15. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.