Agent Help Network
REMOTE · AGENTHELPNETWORK.COM
Web step blocked? Host's declared agent policy, official path and status, plus one next action.
Available components
Last scanned (21 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1299 tokens (~433/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 21% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- Tool coverage: 15% → 21% ▲ functional
- “check_incident” added an optional parameter “failed_at” cosmetic
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_incident” rewrote its description, which is the text the model reads security
- Schema quality: 308 → 411 ▼ functional
- Tool coverage: 10% → 15% ▲ functional
- New tool “rate_last_lookup” functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +7
- Authorization: fail → partial ▲ security
- Tool “check_incident” rewrote its description, which is the text the model reads security
- Tool “report_observation” no longer declares itself destructive security
- Schema quality: 206 → 308 ▼ functional
- Schema quality: 206 → 258 ▼ functional
- Tool coverage: 0% → 10% ▲ functional
- Tool coverage: 0% → 11% ▲ functional
- “check_incident” added an optional parameter “agent_vendor” cosmetic
- “check_incident” added an optional parameter “challenge” cosmetic
- “check_incident” added an optional parameter “http_status” cosmetic
- “check_incident” added an optional parameter “retry_after” cosmetic
- “check_incident” added an optional parameter “via” cosmetic
- 20 Oct 26 0
- Tool “check_incident” rewrote its description, which is the text the model reads security
- Schema quality: 185 → 206 ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://agenthelpnetwork.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agenthelpnetwork.com | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ba5475491d361bba1372326863f60967 |
| SANs: agenthelpnetwork.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agenthelpnetwork.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| agenthelpnetwork.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://agenthelpnetwork.com/mcp | Verified | 200 | |
| http (plaintext) | http://agenthelpnetwork.com/mcp | HTTPS enforced | 301 | https://agenthelpnetwork.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_incident ~637
Call 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), 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 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, and whenever unsure. It selects robots.txt groups (not stored). The answer: summary_line, next_action (do, url, retry_after_seconds), recommendation.action, access_profile (declared policy), official_paths, provider_status and observations. A no_reports result means no observations, not a healthy site. Then follow next_action: it may say to continue, wait for the provider, 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 st…
| Name | Type | Req | Description |
|---|---|---|---|
| agent_vendor | string | – | – |
| challenge | string | – | – |
| error_class | string | – | – |
| failed_at | string | – | When the step failed, as an ISO 8601 time such as 2026-11-01T07:10:00Z (UTC if no offset). Leave it out for a failure that just happened. Only used to choose the cause shown in the answer; not stored. |
| failure_stage | string | – | – |
| http_status | integer | – | HTTP status the site returned: 401, 402, 403, 407, 408, 429, 451 or 500-599. Leave out if unknown. |
| retry_after | string | – | – |
| site_host | string | yes | – |
| task_step | string | – | – |
| via | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| access_profile | – | – | – |
| ahn_check | – | – | – |
| cause | – | – | – |
| current_site_status | string | yes | – |
| data_horizon_hours | integer | yes | – |
| evidence_level | string | yes | – |
| failure_stage | – | – | – |
| failures | integer | yes | – |
| feedback_token | – | – | – |
| generated_at | string | yes | – |
| host_facts | – | – | – |
| links | – | – | – |
| lookup_activity | – | – | – |
| next_action | – | – | – |
| next_checks | array | – | – |
| observations | array | yes | – |
| official_paths | – | – | – |
| official_status_page | – | – | – |
| provider_discovery_attempted_at | – | – | – |
| provider_source_state | string | yes | – |
| provider_status | – | – | – |
| recommendation | – | – | – |
| reporting_sources | integer | yes | – |
| site_host | string | yes | – |
| successes | integer | yes | – |
| summary | string | yes | – |
| summary_code | string | yes | – |
| summary_line | – | – | – |
| synthetic | boolean | yes | – |
| window_hours | integer | yes | – |
No examples provided.
rate_last_lookup ~174
If 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.
| Name | Type | Req | Description |
|---|---|---|---|
| outcome | string | yes | – |
| path | string | – | – |
| token | string | yes | The feedback_token.token value from the check_incident answer, unchanged. |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | yes | – |
No examples provided.
report_observation ~59
Submit 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.
| Name | Type | Req | Description |
|---|---|---|---|
| observation | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| incident_id | string | yes | – |
| observation_id | string | yes | – |
| review_state | string | yes | – |
| synthetic | boolean | yes | – |
| withdrawal_token | – | – | – |
No examples provided.
How do I install the Agent Help Network MCP server?
Agent Help Network is a hosted endpoint at https://agenthelpnetwork.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · agenthelpnetwork.com
claude mcp add --transport http com-agenthelpnetwork-agent-help-network 'https://agenthelpnetwork.com/mcp'
What is the Agent Help Network MCP server?
Agent Help Network is an MCP server listed in the public MCP registry as com.agenthelpnetwork/agent-help-network. Web step blocked? Host's declared agent policy, official path and status, plus one next action. This page covers its hosted endpoint (https://agenthelpnetwork.com/mcp).
Is the Agent Help Network MCP server safe to use?
Agent Help Network scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Help Network MCP server expose?
Agent Help Network exposes 3 tools: check_incident, rate_last_lookup, report_observation. Their descriptions and schemas cost roughly 870 tokens of context every time the server is loaded.
Does the Agent Help Network MCP server require authentication?
No. We connected to Agent Help Network without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Help Network MCP server still maintained?
Agent Help Network is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.