Skip to content

Agent Help Network MCP server

com.agenthelpnetwork/agent-help-networkagenthelpnetwork.comstreamable-httpv0.1.3Scanned

Web step blocked? Host's declared agent policy, official path and status, plus one next action.

3 tools: 3 change things.

Tools: 0 delete, 0 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Agent Help Network MCP server can do

The Agent Help Network MCP server is published by agenthelpnetwork.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: check_incident, rate_last_lookup and report_observation), but cannot delete data. None of its tools only reads.

2 tools bring in text other people can write (check_incident and report_observation).

The fixed checks matched 4 findings (credentials-mention, long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 0.1.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

3 tools

Changes things 3Claude Code: ask
  • 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), whe…Reads text others write3 findings

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...ic hostname, never a URL path, query or credentials; add codes only when you observed them:..."

      What this check looks for
    • Info

      The description is 2,041 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ummary; next_action gives the step to take, and recommendation stays the verdict."

      What this check looks for
    • Warn

      The server marks "check_incident" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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), 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 take, and recommendation stays the verdict.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Check host access profile
  • rate_last_lookupIf an earlier check_incident answer gave you a feedback token and you then tried again, say whether it worked.1 finding

    Why it is in this group

    • The name "rate_last_lookup" says "lookup": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "rate_last_lookup" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "rate_last_lookup" says "lookup": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: false
    • title: Rate the last lookup
  • report_observationSubmit one de-identified firsthand observation under your own operating authority and platform rules.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "submit": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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. 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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Report an authorized observation

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:33 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://agenthelpnetwork.com/mcp: tools/list returned 5 tools to an anonymous client, including check_incident (write), rate_last_lookup (write), report_observation (write), find_task_route (write), report_task_route (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • Tools that change things, listed without credentials: 3 to 5
  2. Nov 6, 2026
    • Tools that change things, listed without credentials: 2 to 3

Findings

Matches of fixed checks, with the text they matched.

2 warn2 info
  • The server marks "check_incident" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "call": a word for a change.

    What this check looks for
  • The server marks "rate_last_lookup" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "rate_last_lookup" says "lookup": a word for reading.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...ic hostname, never a URL path, query or credentials; add codes only when you observed them:..."

    What this check looks for
  • The description is 2,041 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ummary; next_action gives the step to take, and recommendation stays the verdict."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 5.View diff
    • Tools that change things, listed without credentials: 3 to 5
  2. Tools1 added, 2 changed.+1 added~2 changedView diff
  3. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
    • Tools that change things, listed without credentials: 2 to 3
  4. Tools2 changed.~2 changedView diff

Install

Pinned to version 0.1.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-help-network https://agenthelpnetwork.com/mcp
claude mcp add --transport http agent-help-network https://agenthelpnetwork.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__agent-help-network__check_incident",
      "mcp__agent-help-network__rate_last_lookup",
      "mcp__agent-help-network__report_observation"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-help-network. Review it before you use it.

Capability tags behind 2 rules
  • mcp__agent-help-network__check_incident untrusted-input
  • mcp__agent-help-network__report_observation untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.agenthelpnetwork/agent-help-network/verify?hash=053b7eec27f5eb3c5d796d745f77783206e93515180dccc7f035f8ae3f9750dc" | jq -e '.changed == false'

Pinned hash 053b7eec27f5, from Nov 8, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.agenthelpnetwork/agent-help-network/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.agenthelpnetwork/agent-help-network
[![Anlyon Radar](https://radar.anlyon.com/badge/com.agenthelpnetwork/agent-help-network.svg)](https://radar.anlyon.com/servers/com.agenthelpnetwork/agent-help-network)

Source: MCP Registry · repository. Synced Oct 22, 2026, 19:17 UTC.

Agent Help Network MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Agent Help Network MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Agent Help Network MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Agent Help Network MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Agent Help Network MCP server have?

3 tools: 3 write. check_incident, rate_last_lookup and report_observation.

Does the Agent Help Network MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Agent Help Network MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Agent Help Network MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.