Agent Help Network
com.agenthelpnetwork/agent-help-networkVersion 0.1.3Web step blocked? Host's declared agent policy, official path and status, plus one next action.
Status
Responds457 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:45 UTC
- Latency
- 457 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://agenthelpnetwork.com/mcpResponds457 msNo sign-in
Claude Code
claude mcp add --transport http agent-help-network https://agenthelpnetwork.com/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: agent-help-network
Remote MCP server URL: https://agenthelpnetwork.com/mcpCursor
{
"mcpServers": {
"agent-help-network": {
"url": "https://agenthelpnetwork.com/mcp"
}
}
}VS Code
code --add-mcp '{"name":"agent-help-network","type":"http","url":"https://agenthelpnetwork.com/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
3 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
check_incidentCall this when a web step is blocked or failing for no clear reason (a 403 or access denied, a 429, a 5xx or a timeout, a login wall, a "verify you are human" or CAPTCHA page), when sign-in failed or an extra verification step appeared (a code, app approval, new-device check; error_class=login_auth), or when asked "is this site down?" or whether its robots rules block agents. Skip it when the page opened normally or your own tool or platform already said why it refused (e.g. robots.txt or platform policy). Look the host up once per blocked step, before deciding whether to retry. Send the public hostname, never a URL path, query or credentials; add codes only when you observed them: error_class (site_access, login_auth, human_verification, service_error), failure_stage (before_target_response, response_observed, access_denial_observed, unknown), http_status, challenge, retry_after, via. Send agent_vendor only when you know which vendor's documented robots.txt token your requests send: openai, anthropic (Claude-User), google, perplexity, meta, mistral, amazon, microsoft, apple, duckduckgo, diffbot, exa, or other if none. Browser automation usually sends a normal browser user agent, so robots.txt agent tokens may not apply; leave agent_vendor out then. The answer: summary_line, next_action (do, url, retry_after_seconds), recommendation.action, access_profile, official_paths, provider_status and observations. no_reports is not a healthy site. Then follow next_action (continue, wait, use a listed official path, hand the step to the user, stop retrying, or look up once more). On 'pending', look up once more after retry_after_seconds; do not poll. Read-only: it may fetch the host's public robots.txt, llms.txt and status feed, and the home page unless robots.txt bars it (ahn_check), never changes the target site or your data; lookups and the codes you send are counted anonymously per host and hour. The first text block is a one-line summary; next_action gives the step to ta | No | Yes | Yes | Yes |
rate_last_lookupIf an earlier check_incident answer gave you a feedback token and you then tried again, say whether it worked. Sends only the token and the outcome code, no hostname. outcome: succeeded (the next attempt worked), still_blocked, handed_off (you handed the step to the user) or gave_up. path: official_path (you used the official path the answer pointed to), same_site (you retried the same site) or unknown. A token works once and expires one hour after the lookup; do not send one for an attempt you did not make. The outcome is counted anonymously per host and hour and does not change any answer. | No | No | Yes | No |
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 conversation text. Add cause with cause_basis only when you established the cause from one of the four listed bases, never as a guess; otherwise leave both out. | No | No | No | Yes |
Details
- Registry status
- Active
- Published
- Oct 22, 2026
- Updated
- Oct 22, 2026
- Categories
- Uncategorized
- GDPR
- Not declared