Skip to content

AIDNode | AI Agent Support Network MCP server

io.github.AIDNodeOfficial/aidnodeAIDNodeOfficialstreamable-httpv0.4.0-engines-betaScanned

Five AI-agent MCP tools: Repair, Verify, Witness, Monitor, Recovery. Free beta; no billing.

6 tools: 6 change things.

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

Tools listed without sign-in. Remote posture

With Anlyon

6 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 AIDNode | AI Agent Support Network MCP server can do

The AIDNode | AI Agent Support Network MCP server is published by the GitHub account AIDNodeOfficial. It has 6 tools. It can create or change data (6 tools: repair, verify, witness, monitor and 2 more), but cannot delete data. None of its tools only reads.

3 tools can send data out of your system (verify, witness and monitor).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

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

Last scanned Nov 15, 2026, version 0.4.0-engines-beta.

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.

6 tools

Changes things 6Claude Code: ask
  • monitorAIDNode Monitor v2: live independent HTTP HEAD/GET health and optional content digest check of approved public HTTPS hosts.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    AIDNode Monitor v2: live independent HTTP HEAD/GET health and optional content digest check of approved public HTTPS hosts. On-demand only.
  • recoveryAIDNode Recovery v2: dependency-aware safe resume plan for failed agent workflows with idempotency and uncertain outcomes.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    AIDNode Recovery v2: dependency-aware safe resume plan for failed agent workflows with idempotency and uncertain outcomes. No actions executed.
  • repairAIDNode Repair v2: classify HTTP/transport failures, retry safety, idempotency, Retry-After, bounded backoff.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    AIDNode Repair v2: classify HTTP/transport failures, retry safety, idempotency, Retry-After, bounded backoff. Advisory only.
  • submit_beta_feedbackOptional and free.No findings

    Why it is in this group

    • The name "submit_beta_feedback" says "submit": a word for a change.
    Description, as the server wrote it
    Optional and free. Report whether AIDNode helped and whether your operator might consider the proposed $0.005/use price. A bot answer is NOT purchase authorization. Feedback is stored privately and is not a testimonial.
  • verifyAIDNode Verify v2: text diff/hash, canonical JSON change paths, or independent digest of retrieved public HTTPS source from strict host allowlist.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    AIDNode Verify v2: text diff/hash, canonical JSON change paths, or independent digest of retrieved public HTTPS source from strict host allowlist.
  • witnessAIDNode Witness v2: validate supplied structured evidence and issue HMAC-signed, hash-based validation receipt; not real-world action attestation.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.external_evidence.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    AIDNode Witness v2: validate supplied structured evidence and issue HMAC-signed, hash-based validation receipt; not real-world action attestation.

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 untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
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 16, 2026, 14:19 UTC, unchanged since Nov 16, 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
6
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 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://botstop-dev.botstop-dev-lab-2026.workers.dev/mcp: tools/list returned 6 tools to an anonymous client, including repair (write), verify (write), witness (write), monitor (write), recovery (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. Tools2 added, 3 changed.+2 added~3 changedView diff
    • Added:monitorChanges things
    • Added:recoveryChanges things
    • Changed:repairChanges thingsdescriptioninputSchema
    • Changed:verifyChanges thingsdescriptioninputSchema
    • Changed:witnessChanges thingsdescriptioninputSchema

Install

Pinned to version 0.4.0-engines-beta. Values in angle brackets are yours to fill in.

claude mcp add --transport http aidnode https://botstop-dev.botstop-dev-lab-2026.workers.dev/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http aidnode https://botstop-dev.botstop-dev-lab-2026.workers.dev/mcp --header 'Authorization: <your-authorization>'

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__aidnode__repair",
      "mcp__aidnode__verify",
      "mcp__aidnode__witness",
      "mcp__aidnode__monitor",
      "mcp__aidnode__recovery",
      "mcp__aidnode__submit_beta_feedback"
    ],
    "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 aidnode. Review it before you use it.

Capability tags behind 3 rules
  • mcp__aidnode__verify outbound
  • mcp__aidnode__witness outbound
  • mcp__aidnode__monitor outbound

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/io.github.AIDNodeOfficial/aidnode/verify?hash=e3e838a7c7ced5aa747993b9d25ecaf96996a5ad24d81599c26d1b406c290562" | jq -e '.changed == false'

Pinned hash e3e838a7c7ce, from Nov 15, 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/io.github.AIDNodeOfficial/aidnode/changes.xml

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

Badge

Anlyon Radar badge for io.github.AIDNodeOfficial/aidnode
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.AIDNodeOfficial/aidnode.svg)](https://radar.anlyon.com/servers/io.github.AIDNodeOfficial/aidnode)

Source: MCP Registry · repository. Synced Nov 15, 2026, 16:17 UTC.

AIDNode | AI Agent Support Network MCP server: questions and answers

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

Is the AIDNode | AI Agent Support Network MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 6 of which can change, send or delete something, and 0 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 AIDNode | AI Agent Support 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 AIDNode | AI Agent Support 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 AIDNode | AI Agent Support Network MCP server have?

6 tools: 6 write. repair, verify, witness, monitor, recovery and submit_beta_feedback.

Does the AIDNode | AI Agent Support Network MCP server need sign-in or OAuth?

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

Does the AIDNode | AI Agent Support Network MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): verify, witness and monitor.

Has the AIDNode | AI Agent Support Network MCP server changed its tools?

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