Back to Browse

Agent Help Network MCP Server

Developer ToolsModerate5.2MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://agenthelpnetwork.com/mcp

Security Report

5.2
Moderate5.2Moderate Risk

Agent Help Network is a read-only lookup service for robots.txt, llms.txt, official paths and provider status, with the MCP adapter sending only hostnames and enum codes to a configured API base and requiring a key only for optional write operations. No malicious exfiltration or shell execution was observed in the visible code, though the truncated status_refresh.py and README sections were not fully reviewed and the optional observation-reporting tools accept free-text content that the server forwards to a central service. Permissions (outbound HTTP to publisher status and robots endpoints, database access for caching) match the stated purpose. Supply chain analysis found 19 known vulnerabilities in dependencies (1 critical, 10 high severity).

7 files analyzed · 22 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

database

Applies to the server that hosts this plugin, not to your machine.

env_vars

Applies to the server that hosts this plugin, not to your machine.

File System Read

Reads files on the server that hosts it, not on your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "com-agenthelpnetwork-agent-help-network": {
      "url": "https://agenthelpnetwork.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Agent Help Network

English · 한국어

When a web step is blocked (403, login wall, CAPTCHA, 5xx), ask once: what does this host allow agents to do, what is its official path, is it up — and what to do next. Free, read-only, no account. Remote MCP · REST · Claude Code plugin · Python client.

PyPI License MCP Registry

Agent Help Network answers one question for a public hostname: what does this host allow agents to do, what is the official path, and is it up right now — plus any recent observations from other agents. It is meant for an agent whose web step is blocked (access denied, login wall, human verification, service error): instead of retrying blindly or handing the task back to a person sooner than needed, the agent first reads the host's own declared policy and official path. Agents read the answer over REST/OpenAPI or MCP; the human website shows the same answer in English and Korean. Steps that genuinely need a person's confirmation or decision are handed to that person.

Agent Help Network is an independent project. It is not an official service of, and is not affiliated with, endorsed by, or sponsored by, any AI provider or platform, any site it describes, or any provider whose status it links.

Install

Reading is free and needs no account.

Install in your coding agent: remote HTTP server, no account or key. Each client asks you to confirm before saving. Formats are from each vendor's docs: Cursor, VS Code, Cline, Codex.

  • Cursor and VS Code one-click buttons: the connect page (GitHub does not render cursor:// or vscode: links, and the vendors document no https redirect for them)
  • VS Code, in mcp.json: {"servers": {"agent-help-network": {"type": "http", "url": "https://agenthelpnetwork.com/mcp"}}}
  • Cline, in cline_mcp_settings.json: {"mcpServers": {"agent-help-network": {"type": "streamableHttp", "url": "https://agenthelpnetwork.com/mcp"}}}
  • Codex, in ~/.codex/config.toml:
[mcp_servers.agent-help-network]
url = "https://agenthelpnetwork.com/mcp"

The connect page has setup for the Claude Code plugin, Cursor, the OpenAI Agents SDK, and any other remote MCP client.

Claude Code plugin:

claude plugin marketplace add agent-help-network/agent-help-network   # Claude Code plugin (source: plugins/claude-code/ahn)
claude plugin install ahn@agent-help-network

For Python code

pip install ahn-client                                                 # Python client (source: clients/python)
pip install "ahn-client[langchain]"                                    # or [crewai], [openai-agents], [claude-agent-sdk]: framework adapters

For Python code (Playwright, Browser Use, plain HTTP) use the read-only ahn-client package from PyPI, which has no dependencies and sends only a hostname and enum codes. From version 0.3.0 it also has optional adapters that add a one-line answer when a web tool fails inside LangChain v1 ([langchain]), CrewAI ([crewai]), the OpenAI Agents SDK ([openai-agents]) or the Claude Agent SDK ([claude-agent-sdk]), and a Browser Use example. None of these is an official OpenAI, Meta, Anthropic, Muse, or dots integration.

Plugin demo video: watch the Claude Code plugin work (WebM, 1 min 18 s, with English captions; captions file). GitHub does not play WebM inline, so this opens the file; the same video is embedded on the connect page.

A real response

Send the hostname only — never a URL path, query, credential, or conversation text — and avoid sensitive hostnames.

curl "https://agenthelpnetwork.com/v1/incidents/check?site_host=github.com&error_class=site_access"

A response for github.com, captured from the live service on 2026-10-18 and trimmed to the key fields (summary_line is the current sentence of its row, not the captured text): robots.rules held 22 agent-token entries at capture time (it has one entry per token in AGENT_USER_AGENTS in ahn/access_profile.py, and that table has grown since, so agents_blocked and agents_allowed below list only the tokens known then) and is cut to three here, path-sample lists are cut to at most three entries, and each next_checks entry also carries an English text. robots_detail, llms_detail, crawl_delay, the path samples, sitemaps, wildcard_crawl_delay, read_host, and provider_status.error_detail are shown as a fresh read under the current contract returns them (the profile cached at capture time predated them). summary_line and next_action are the short form: read them first. They are computed after the answer is decided and never change recommendation or next_checks, which stay the verdict (D51; fields in the contract).

{
  "site_host": "github.com",
  "summary_line": "An official developer API is listed with a no-sign-up option (official_paths.access.auth). For API work use it, not page automation; for a task in the user's own account, hand the step to your user.",
  "next_action": {"do": "use_official_path", "url": "https://docs.github.com/en/rest", "retry_after_seconds": null},
  "links": {
    "feedback": "https://github.com/agent-help-network/agent-help-network/discussions/categories/field-reports",
    "changelog": "https://github.com/agent-help-network/agent-help-network/blob/main/docs/feedback-changelog.md"
  },
  "current_site_status": "unknown",
  "evidence_level": "no_reports",
  "summary_code": "NO_MATCHING_REPORTS_STATUS_UNKNOWN",
  "observations": [],
  "recommendation": {
    "action": "use_official_path",
    "confidence": "medium",
    "reasons": ["official_path_available"]
  },
  "access_profile": {
    "robots_status": "ok",
    "robots": {
      "rules": [
        {"agent": "ChatGPT-User", "kind": "user_agent", "explicit_group": false, "root_allowed": true, "disallow_count": 162,
         "crawl_delay": null, "disallow_paths": ["/account-login", "/copilot/", "/copilot/c/"]},
        {"agent": "GPTBot", "kind": "training_crawler", "explicit_group": true, "root_allowed": true, "disallow_count": 162,
         "crawl_delay": 1.0, "disallow_paths": ["/account-login", "/copilot/", "/copilot/c/"]},
        {"agent": "Bytespider", "kind": "training_crawler", "explicit_group": true, "root_allowed": false, "disallow_count": 1,
         "crawl_delay": null, "disallow_paths": ["/"]}
      ],
      "wildcard_root_allowed": true,
      "sitemaps": [],
      "wildcard_crawl_delay": null,
      "wildcard_disallow_paths": ["/account-login", "/copilot/", "/copilot/c/"],
      "agents_blocked": ["Bytespider"],
      "agents_allowed": ["OAI-SearchBot", "PerplexityBot", "Bingbot", "GPTBot", "ClaudeBot", "anthropic-ai"]
    },
    "robots_detail": "http_200",
    "llms_txt_status": "present",
    "llms_detail": "too_large",
    "read_host": "github.com",
    "source_urls": {"robots_txt": "https://github.com/robots.txt", "llms_txt": "https://github.com/llms.txt"},
    "fetched_at": "2026-10-18T03:53:58.695938Z",
    "freshness": "fresh"
  },
  "official_paths": {
    "name": "GitHub",
    "api_docs": "https://docs.github.com/en/rest",
    "developer_portal": "https://docs.github.com/",
    "note": null
  },
  "provider_status": {
    "source_name": "GitHub Status",
    "source_url": "https://www.githubstatus.com/",
    "indicator": "none",
    "freshness": "fresh",
    "error_detail": null
  },
  "provider_source_state": "feed_connected",
  "next_checks": [
    {"code": "locate_failure_stage"},
    {"code": "robots_allows_agents"},
    {"code": "llms_txt_present"},
    {"code": "official_path_available"},
    {"code": "provider_clear"},
    {"code": "reports_unknown"}
  ]
}

Values change over time; call the service rather than copying this example. The full field reference is in the API contract (English).

When to call it

Call it after a web step has failed, not before. Look the host up when a fetch or browser step reports a block or an outage: HTTP 401, 402, 403, 407, 408, 429, 451 or 5xx, a login wall, a human-verification page, a timeout, or a refused connection. A 404 or another plain 4xx is not a block and needs no lookup. Ask once per host; do not poll.

RuntimeWhat happens on a failed web stepInstall
Claude CodeThe plugin adds one line after a failed WebFetch or browser step (when a line is added).claude plugin install ahn@agent-help-network
LangChain v1, CrewAI, OpenAI Agents SDK, Claude Agent SDKThe adapter adds one line to the failed tool result (CrewAI: to your callback and the log, not the prompt).pip install "ahn-client[langchain]", [crewai], [openai-agents] or [claude-agent-sdk]
Any other MCP clientYou call the check_incident tool.https://agenthelpnetwork.com/mcp
Plain Python, Playwright, Browser Use, RESTYou call ahn.check() or the REST endpoint in your except block.pip install ahn-client

Limits

  • It acts only after a failure. A tool that returns the text of a 403 page as an ordinary result is not a failure to the framework, so no adapter sees it: make the tool raise (response.raise_for_status()) or report an error. The Claude Code plugin likewise does not look up a browser step that "succeeds" but shows a block page, or curl run through Bash; use the ahn-lookup skill or the MCP tool by hand.
  • A failure that is not a block or an outage (404, 422, a typo in an address) adds nothing, and the run goes on as it would have.
  • The answer is declared policy and published sources, not an access guarantee, and no_reports does not mean a site works (see What the answer contains).
  • The first lookup of a host can come back with access_profile.freshness: pending: ask once more after retry_after_seconds, do not poll. A subdomain or tenant host answers profile_not_read: look up the apex host.
  • It never attempts your task (see What we read and never do).

REST and MCP reference

People can copy the full agent instructions from the Human page and paste them into an agent chat. The public site opens on the agent guide; the Agent | Human switch at the top right leads to the human search page, which shows declared policy, llms.txt, official path, provider status, and observations in that order.

  • REST: GET https://agenthelpnetwork.com/v1/incidents/check?site_host=<public hostname> Optional: error_class (site_access, login_auth, human_verification, service_error), failure_stage (before_target_response, response_observed, access_denial_observed, unknown), task_step (send status_check for a pure up/down check; a lookup after a failure should send error_class and failure_stage instead), window_hours (1–168, default 24), and four optional lookup codes the client already knows: http_status (401, 402, 403, 407, 408, 429, 451 or 500–599), challenge (header, none), retry_after (none, lt_60, 60_3600, gt_3600), via (http_fetch, browser, unknown). They are counted per host and hour and never change the answer (see the contract). One more optional code does change it: agent_vendor (openai, anthropic, google, perplexity, meta, mistral, amazon, microsoft, apple, duckduckgo, diffbot, exa, or other), the vendor whose robots.txt token your own web requests send. The recommendation then reads that vendor's tokens; leave it out when unsure. It is not counted or stored, and a value outside the list is ignored (contract).
  • MCP (streamable HTTP): https://agenthelpnetwork.com/mcp — tool check_incident (read-only, idempotent), rate_last_lookup (optional: after a blocked lookup, sends back its one-time feedback token with whether the next attempt worked; no hostname), the optional report_observation and the read-only find_task_route (see Task routes below).
  • Agent entry points: /llms.txt · /agent-instructions.txt · /openapi.json

What the answer contains

Three layers, read separately:

  1. access_profile — declared policy. Rules per agent token from the host's own robots.txt (RFC 9309 precedence with lenient prefix matching of user-agent names of 3+ characters) and whether it publishes llms.txt. The token table is AGENT_USER_AGENTS in ahn/access_profile.py: each token's spelling and kind (user_agent, search_crawler, training_crawler) follows the vendor's own documentation, whose address is recorded in AGENT_SOURCES; tokens that no vendor page confirms are listed in UNCONFIRMED_AGENT_TOKENS (all training crawlers, so they never count as a block). This is what the host declares, not an access guarantee: CDNs, bot filters, logins, and rate limits can treat a user-directed agent differently from a crawler. If robots_status is not ok, the layer is inconclusive, not a block — except refused (the host's edge refused even a plain robots.txt read), which the recommendation treats as a hint to prefer the official path. access_profile.content_use adds the content-use preferences the same robots.txt declares (Cloudflare Content-Signal, IETF AIPREF Content-Usage), normalized to yes/no/unset; they are information only and never change the recommendation. access_profile.site_declared (D59) lists what the host publishes for agents at standard locations, read only where its robots.txt allows: its API catalog (RFC 9727 /.well-known/api-catalog), its text-and-data-mining reservation (W3C TDMRep /.well-known/tdmrep.json and response headers), and, experimentally, the MCP servers in its AI Catalog (/.well-known/ai-catalog.json); also information only.
  2. official_paths and provider status — the official route and whether it is up. official_paths is a curated table of publisher-owned API documentation and developer portals for sites that people or agents open to do work; CDN, ad-tech, asset, and link-shortener hosts are left out. provider_status is the provider's own status feed (with source and fetch time) when one is verified for the host; official_status_page links a publisher status page that has no readable feed and is never turned into a reading. Both status mappings are curated by hand from pages the publisher owns or links to (how status sources are curated). A missing entry does not mean no official path exists, and listing is not an endorsement or affiliation.
  3. observations — optional reports from other agents. no_reports is the normal case and means no matching published observations, not a healthy site. One failure is not an outage; a later success is not general recovery. current_site_status is always unknown.

Where it applies, a fourth, separate field adds registry facts about the domain: host_facts says which public government domain list names the host (the U.S. .gov list, CC0, or the UK .gov.uk list, Open Government Licence v3.0), the organisation that list gives, and whether the suffix (.gov, .gov.uk, .go.kr) is reserved for government bodies. It is a fact about who registered a name, not a judgement about any site, page or link, and it never changes recommendation. It is left out for every other host.

recommendation.action condenses the declared and official layers into one action. Observations never change it. The first matching row wins:

actionWhenconfidence
hand_off_to_humanerror_class is human_verification and the only reason to wait would be a fresh minor page with one or more active incidents whose worst impact was read as none or minor: reasons human_handoff, provider_scope (D121). A verification screen is the user's step; unknown severity, maintenance, components only and a major or critical page still wait.medium
wait_provider_incidentA fresh provider feed reports an active minor, major, critical, or maintenance status, and it rests on an announced incident or maintenance (provider_status.basis is not components_only), or the page reads major or critical even with nothing announced. Incidents that have had no update for more than 7 days, with no maintenance in progress, are not a reason to wait unless a major or critical page stands above them (provider_incident_stale). Neither is a minor page with no incident list behind it (no basis) from an Instatus or Google Gmail feed (provider_status.source_time: active_items) whose active incidents and maintenances were last updated more than 7 days ago (provider_incident_stale, D54); a page whose time is the page's own (Atlassian Statuspage, incident.io, Better Stack) keeps waiting however old that time is; with no usable update time such a page still waits, with low confidence (provider_update_time_unknown). When every affected component is a region or point of presence (provider_scope_partial), the wait has low confidence. When the status rests only on maintenance in progress and no incident is announced (basis is maintenance, active_incidents is 0), the wait and its confidence are unchanged, and provider_maintenance_only says so (D55). Where we read only a page's public incident history (provider_status.source_kind: history_atom, no severity level), an open incident updated within 7 days waits with low confidence (provider_history_incident, D57); an older one, one with no usable time, or a feed window that may miss incidents (window_blind) does not.medium (low when regional-only, for a minor page with no update time, or from an incident history)
hand_off_to_humanerror_class is human_verification (high) or login_auth (medium).high / medium
use_official_pathA declared block (below) and an official path is listed.high
stop_declared_blockA declared block and no official path is listed. Stop automated retries against pages.medium
use_official_pathThe host's edge refused the robots.txt read (robots_status: refused) and an official path is listed.medium
hand_off_to_humanrefused, no official path is listed, and the caller reported error_class=site_access (no failure_stage or access_denial_observed): reasons edge_refusal_robots, robots_fetch_refused (D85, D98).medium
hand_off_to_humanThe caller reported error_class=service_error (a 5xx or no response) and the answer would be unknown with no page of the site named to try instead (no official path, or only a developer path that is reference), or a customer page on the site that did not answer after no response at all: reasons as before, then no_path_after_failure (D101). The first line tells the user now and says they can open the page themselves; it never offers another try (D111).low
unknownrefused and no official path is listed, with no such failure reported (reason robots_fetch_refused). Page automation from a similar environment may be refused too.medium
use_official_pathA partial block or a wildcard-only disallow (below) and an official path is listed.medium
unknownA partial block or a wildcard-only disallow and no official path is listed (reasons robots_blocks_some_agents, robots_names_vendor_alias, robots_wildcard_disallow). Do not read it as permission.low
use_official_pathAn official path is listed and error_class is absent, site_access, or service_error (with D63, only when a failure signal was sent or robots is not clear; with the D66 mode, which the live service runs, a lookup that sends no failure signal and no task_step of status_check or preflight is treated as if it had sent site_access, so it reaches this row too).medium
hand_off_to_humanThe caller itself reported error_class=site_access (no failure_stage or access_denial_observed; not with task_step status_check or preflight) and the answer would be proceed: reasons caller_reported_refusal, then the proceed reasons (D121). AHN's own home-page refusal (edge_refusal_confirmed, D85, medium) comes first. The first line says not to switch tools or user agents, to tell the user now, and to continue the work that does not need the page.low
proceedrobots.txt was read and declares no block for the tokens the answer was decided on (robots_allows_agents, or robots_blocks_not_your_agent when only other agents' tokens are blocked). Declared allow is still not an access guarantee. Also when no robots.txt is published (absent). proceed means no block is declared, not that nothing blocked you: if a page refused you, that came from your tool, the site's edge or a login, so tell your user (a refusal from the site's own robots.txt or edge is not a reason to retry with another tool or user agent). next_action.url is null for proceed (D65); a curated customer page stays in customer_url. A lookup that only checks whether a site is up, with nothing refused, should send task_step=status_check and gets the answer it would have before D66.low
unknownNo declared policy could be read (reason robots_unknown), or the hostname is a subdomain or tenant host whose policy is not read (reason profile_not_read; look up the apex host). No declaration is known; it is neither a block nor a declaration of no restriction.low

reasons are codes that also appear in next_checks, except caller_reported_refusal (D121), which is a reason only. "An official path is listed" means the official_paths entry has api_docs or developer_portal; an entry with only a note does not count. A declared block (D48) is a robots.txt group that disallows the root and names the governing token of your vendor (agent_vendor: its user-directed fetcher, or its search crawler when it documents none), or, when no vendor was sent, of every listed vendor. When a vendor was not sent and only some vendors are blocked, that is a partial block: the answer is unknown (or the official path with medium confidence) with robots_blocks_some_agents, which means stop if your requests identify as a token in agents_blocked. A group that names a vendor's agent only under a retired or variant name (robots.vendor_aliases_blocked, for example claude-web) gives robots_names_vendor_alias, never proceed. A wildcard-only disallow is a file whose * group disallows the root (User-agent: * with Disallow: /) while at least one agent user-agent or search-crawler token is named by no group and so falls under that wildcard, and no group that names such a token disallows the root (that would be a declared block). Groups that name and allow a token, and training-crawler blocks, do not change this; it is not a declared block, is reported as robots_wildcard_disallow, and is never read as "allows agents". agents_blocked lists every token with an explicit root disallow, including training crawlers, but training crawlers do not count as a declared block. In the example above, Bytespider (a training crawler) is blocked, but because training crawlers do not count as a declared block, the medium-confidence official-path row applies.

What we read and never do

What the service reads, in public operation only (the local development build makes none of these reads):

  • On a site we describe, only these paths: the home page (GET /, from our server, unless the host's robots.txt disallows it for AgentHelpNetwork or *; see the home-page check below), /robots.txt (up to 256 KB) and /llms.txt (presence only, up to 4 KB, requested only when that host's robots.txt allows it for AgentHelpNetwork; otherwise llms_txt_status: not_read), on an eligible apex host or its own www. alias. If the apex robots.txt read fails, is refused, redirects elsewhere, or returns an HTML page, https://www.<host>/robots.txt is read once as a fallback; llms.txt is then read from whichever host supplied robots.txt (read_host).
  • Only the parsed result is stored in host_access_profile: per-token rules, up to six sample Disallow paths per agent token and for the * group (80 characters each), up to five Sitemap URLs, the declared content-use preferences (normalized values, at most 3 sample paths in total, agent names only from the known agent-token table, the parser version and the robots.txt hash), the read status, and provenance: a SHA-256 hash of each file as received, the reader version, the operator, and its declared network vantage. The rest of the file is not stored, and llms.txt content is never stored or passed on.
  • Only eligible public apex hostnames such as example.com or example.co.uk. Eligible means a two-label name under a top-level domain on the fixed list PUBLIC_AGGREGATE_TLDS, or a three-label name under a two-label suffix such as co.uk (PUBLIC_SUFFIXES_2), both in ahn/service.py; a name whose first label starts with xn-- is not eligible. Account-style subdomains are never read or counted. A single leading www. in front of an eligible apex is answered from that apex.
  • Only public addresses. Every resolved address must be a public (global) IP; the connection is pinned to that address.
  • One redirect at most: a single hop from the host to its own www. alias for the same path. Any other redirect is recorded as redirected and not followed.
  • Cached answers, hourly retry of failures. A definitive answer (ok, absent, refused, redirected, invalid, too_large, not_public) is cached for 24 hours. A transport failure (DNS, TLS, connect, timeout, or an unexpected HTTP status) is retried after one hour and never overwrites the last definitive answer. One attempt makes at most five HTTPS requests across the apex and its own www. alias: the apex robots.txt, one hop to the www. alias, the www. fallback, llms.txt, and its hop. Timeouts are short, and requests identify themselves as AgentHelpNetwork/0.2 (+https://agenthelpnetwork.com/en/policy).
  • Almost never while a lookup waits. A lookup answers from the database; the one exception is the home-page check (ahn_check, D67): unless the host's robots.txt disallows it, our server requests the home page and the lookup waits for it at most 3 seconds (only while the operator sets AHN_SITE_PROBE=1; otherwise it is queued and the answer says pending). A missing or expired read is queued in background_reads and done by a small worker inside the web process (AHN_BACKGROUND_READS=0 turns it off) and by the 5-minute review cron, at most two reads per second per process, with at most 2,000 queued reads and a 10-second limit on each file or feed body (ahn/background_reads.py). The first lookup of a new host returns access_profile.freshness: pending, with retry_after_seconds when its read is queued; an expired profile or feed is returned as cached (stale) while it is read again. A failed feed read does not end the last provider statement by itself: it stays fresh (with error_detail) until it is 2 hours old (D46).
  • Seed list read weekly. Hosts on the public seed list ahn/seed_hosts.txt are pre-read by the review cron (10 hosts per 5-minute run by default, AHN_WARM_BATCH, 0 disables) and re-read about once a week, under the same limits (ahn/profile_warm.py). Hosts not yet read go first; a host whose last attempt was a transport failure (for example a name that no longer resolves) is tried again by this pre-read after 24 hours, including a host that already had an answer, so dead names do not use up the batch. A lookup of such a host still retries after an hour.
  • Provider status comes only from verified official status sources: a fixed mapping in ahn/status_refresh.py (SOURCES for feeds a parser reads, OFFICIAL_STATUS_PAGES for links only), or a Statuspage delegation at status.<host> checked in the background after the first lookup and re-checked at most once a day until one is found. Every feed of the fixed mapping is registered and read by the review cron without waiting for a lookup (D44), about hourly and every 15 minutes while it reports an active status; a failing feed is retried at most an hour apart (every 15 minutes while its last statement was active), and a refusal is never retried another way and backs off up to once a day. Feeds discovered for a looked-up host are read on the same schedule. With an Atlassian Statuspage feed (or a page answering the same Statuspage API), a refresh that reads an active status also reads the page's unresolved incidents and maintenances in progress (32 KB cap each) to report their counts, the highest incident impact, at most three affected names, and whether the active status rests on an incident, a maintenance, or component states only (basis); see the API contract. Before any feed is read, we read the status host's own /robots.txt (an answer lasts 24 hours plus up to 2 hours of per-host slack, so a successful read happens at most once per host per day; a read that fails is tried again after an hour; parsed under RFC 9309 by the same code as the declared-policy layer) and request a feed path only if that file allows it for AgentHelpNetwork (ahn/feed_robots.py, D50). Many hosted status pages disallow /api/ for all user agents by default; we do not read those feeds, show no provider status for them, and link the official status page instead. A status host whose robots.txt cannot be fetched (a 5xx answer, 429, a timeout, a connection failure, a redirect we do not follow) is treated as disallowing everything until it can be read, with one exception: a file we read successfully less than 48 hours earlier keeps deciding in the meantime (RFC 9309 section 2.4), and a host with no earlier successful read gets no such grace. A missing file (404), any other 4xx answer (RFC 9309 section 2.3.1.3) and a web page served in place of the file allow; 429 does not, since it is a request to slow down, not an absent file. What is stored per host is the answer for each path, the deciding rule line, how the read ended, a hash of the file and the time it was read, never the file.
  • Government domain lists, downloaded whole. The review cron downloads the U.S. registry's current-full.csv (cisagov/dotgov-data, CC0-1.0) about once a day and GOV.UK's "List of .gov.uk domain names" (found through the GOV.UK content API) about once a month, only from those publishers and never from a site on a list (ahn/gov_registry.py). Stored: the domain name and, for the U.S. list, domain type, organisation, sub-organisation and state; the U.S. file's security contact email and city are dropped. A failed or odd download (changed columns, too few rows, under half the stored rows, over the size cap) keeps the stored data. A lookup joins the stored copy and never waits on a publisher.
  • UK list attribution. Contains public sector information licensed under the Open Government Licence v3.0.

What the service never does:

  • It never attempts the task, follows a link, or touches a login or CAPTCHA page. Apart from the files named above, the only page it requests from a host is the home page (GET /), from our server, with no cookies and no sign-in, unless the host's robots.txt disallows / for AgentHelpNetwork (or for *). It requests it when it needs to and paces itself with its own politeness limits. If the home page answers with a redirect to the host's own www. name, it requests that name's home page once more, only when the www name's robots.txt also allows it; no other redirect is followed. A robots.txt that cannot be read (a server error or a timeout) is treated as disallowing, as everywhere else in this service. It is off unless the operator sets AHN_SITE_PROBE=1 (D67). Only codes are kept, never the page; see ahn/site_probe.py and the privacy policy.
  • It never manufactures failures or invents seed observations, and it does not ask agents to create them.
  • It never claims affiliation with or endorsement by OpenAI, Meta, Anthropic, or any host it describes.
  • In its own reads, on a host we describe or read a status feed from, the service never requests a path that the host's own robots.txt disallows for its user agent — including /llms.txt and every status-feed path — and it never reads the same information through another route to get around such a rule. /robots.txt itself is always read, as RFC 9309 (section 2.2.2) allows. The one other route is a path the host itself allows: where a Statuspage page disallows its status API but allows its public /history.atom, that feed is read only for whether an announced incident is open (provider_status.source_kind: history_atom, indicator always null); an empty feed means unknown, not healthy, and it never changes recommendation (D52). Offline curation of task-route records is not a service read and has its own, narrower scope, described in the privacy policy and in scripts/README.md: curated task-route data is read only from public help and policy pages (help, support, FAQ, terms, returns, refund, shipping, cancellation and warranty policies, claims pages, and a government agency's own pages on how to apply, file or submit); for those pages only, it may read paths that robots.txt disallows; it identifies itself as AgentHelpNetwork-curation, waits at least 3 seconds between requests to a host, stops at a block response (401, 403, 429, challenge), never signs in, submits forms or guesses addresses, keeps short quotations with a link, does not read product, search, cart, account or user-content pages, and removes a site's records on request.
  • It never accepts or logs passwords, cookies, tokens, names, account or claim numbers, personal URLs, or conversation text.

Documentation

The API contract has English and Korean versions; the architecture overview and the decision log are in Korean.

Run it locally (Windows PowerShell)

These steps assume PostgreSQL 17 extracted to %LOCALAPPDATA%\AgentHelpNetwork\postgresql-17 with its data directory at %LOCALAPPDATA%\AgentHelpNetwork\data, listening only on 127.0.0.1:55432. On another machine, install PostgreSQL by following the official PostgreSQL download instructions and adjust the paths and database URLs below. Do not use development trust authentication for real data.

  1. Create the Python virtual environment and install dependencies.

    py -3 -m venv .venv
    .\.venv\Scripts\python.exe -m pip install -r requirements-dev.txt
    
  2. Start PostgreSQL. In an existing development setup use .\scripts\start-local.ps1 -Component Database; initialize a new data directory with initdb first. Create a dedicated test database ahn_test and a regular local database ahn_local.

    & "$env:LOCALAPPDATA\AgentHelpNetwork\postgresql-17\bin\createdb.exe" -h 127.0.0.1 -p 55432 ahn_local
    & "$env:LOCALAPPDATA\AgentHelpNetwork\postgresql-17\bin\createdb.exe" -h 127.0.0.1 -p 55432 ahn_test
    

    Do not recreate databases that already exist. The tests reset only a database named exactly ahn_test. Never put real data in it.

  3. Put the settings outside the repository in %LOCALAPPDATA%\AgentHelpNetwork\local-config.json, with this structure. key_pepper is a cryptographically random string of at least 32 characters; the two reporter keys are generated by the CLI below. Never use the example strings as real secrets.

    {
      "database_url": "postgresql://postgres@127.0.0.1:55432/ahn_local",
      "test_database_url": "postgresql://postgres@127.0.0.1:55432/ahn_test",
      "key_pepper": "REPLACE_WITH_RANDOM_SECRET_AT_LEAST_32_CHARS",
      "muse_key": "REPLACE_WITH_FIRST_LOCAL_TEST_KEY",
      "dots_key": "REPLACE_WITH_SECOND_LOCAL_TEST_KEY"
    }
    
  4. In the same PowerShell window, run the migrations and create two test reporter keys. Save each printed key in the matching JSON field and keep it out of terminal logs and the repository.

    $cfg = Get-Content "$env:LOCALAPPDATA\AgentHelpNetwork\local-config.json" -Raw | ConvertFrom-Json
    $env:AHN_DATABASE_URL = $cfg.database_url
    $env:AHN_KEY_PEPPER = $cfg.key_pepper
    .\.venv\Scripts\python.exe -m ahn.cli migrate
    .\.venv\Scripts\python.exe -m ahn.cli create-reporter local-muse-test
    .\.venv\Scripts\python.exe -m ahn.cli create-reporter local-dots-test
    
  5. Start each component in its own PowerShell window, in this order. All services bind to local addresses.

    .\scripts\start-local.ps1 -Component Api
    .\scripts\start-local.ps1 -Component Mcp
    .\scripts\start-local.ps1 -Component Monitor
    

    Web: http://127.0.0.1:8875/en/ and /ko/; agent guide: /en/agents; OpenAPI: /openapi.json; MCP: http://127.0.0.1:8876/mcp; operator monitor: http://127.0.0.1:8877/. The monitor runs as a separate process with a loopback request restriction; never put it behind a public proxy.

  6. Run .\scripts\start-local.ps1 -Component Test against the test database. With the API and MCP running, also run the synthetic .test host round trip:

Documentation truncated — see the full README on GitHub.

Reviews

No reviews yet

Be the first to review this server!