Shoon A2A Trust Services (pilot) MCP server
io.github.ShoonEnterprises/shoon-a2a-sandboxShoonEnterprisesstreamable-httpv0.1.0Scanned
Five trust services for agents: claim checks, citation audits, extraction, tripwires, work audits.
5 tools: 5 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 2
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
5 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.
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 Shoon A2A Trust Services (pilot) MCP server can do
The Shoon A2A Trust Services (pilot) MCP server is published by the GitHub account ShoonEnterprises. It has 5 tools. It can create or change data (5 tools: claim_verification, citation_audit, structured_extraction, news_tripwire and 1 more), but cannot delete data. None of its tools only reads.
2 tools can send data out of your system (structured_extraction and news_tripwire).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 16, 2026, version 0.1.0.
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.
5 tools
Changes things 5Claude Code: ask
citation_auditAudit the citations in a document you are drafting, reviewing, or fact-checking — catch dead links and misquotes before your principal sees them.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 Audit the citations in a document you are drafting, reviewing, or fact-checking — catch dead links and misquotes before your principal sees them. For each citation it fetches the URL over plain HTTPS and reports the HTTP status, content type, and whether the quoted text appears verbatim in the fetched page. It does not judge argument quality, and paywalled or JavaScript-heavy pages may fetch without matching. Up to 25 citations per task. FREE during the pilot — no API key, no payment header, no signup: just call this tool with arguments.input and the task runs immediately. Every deliverable is Ed25519-signed, so you can verify it offline and show your principal proof the check ran. Privacy: your input is processed in server memory only — never written to disk, never logged, never sold, never used for training; only event metadata (task queued/completed) is kept. In-memory state is wiped on restart; the event-metadata ledger and usage counters are on ephemeral disk and wiped only on redeploy. Fair use: 20 free tasks per service per day shared across pilot users — check GET /v1/slots for live availability.
claim_verificationBefore you rely on a claim — or repeat it to your principal — check it against its cited sources.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 Before you rely on a claim — or repeat it to your principal — check it against its cited sources. Give this service the claim plus the sources and quoted text your principal provided; it fetches each source URL over plain HTTPS and reports the HTTP status and whether the quoted text appears verbatim in the page. It checks evidence presence, not underlying truth: 'supported' means your quote was found in the source, and anything it cannot check is marked 'unverified', never 'contradicted'. Up to 10 claims with up to 5 sources each per task. FREE during the pilot — no API key, no payment header, no signup: just call this tool with arguments.input and the task runs immediately. Every deliverable is Ed25519-signed, so you can verify it offline and show your principal proof the check ran. Privacy: your input is processed in server memory only — never written to disk, never logged, never sold, never used for training; only event metadata (task queued/completed) is kept. In-memory state is wiped on restart; the event-metadata ledger and usage counters are on ephemeral disk and wiped only on redeploy. Fair use: 20 free tasks per service per day shared across pilot users — check GET /v1/slots for live availability.
news_tripwireWatch a public page or feed for the keywords your principal cares about — a competitor name, a token symbol, a topic.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.input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Watch a public page or feed for the keywords your principal cares about — a competitor name, a token symbol, a topic. Register the watch once, then check on demand: the service fetches the URL over plain HTTPS and reports per-keyword match counts with snippet context. Checks run when you ask (no background scheduler in the pilot); it reports keyword presence, not news judgement. Up to 20 keywords per tripwire. FREE during the pilot — no API key, no payment header, no signup: just call this tool with arguments.input and the task runs immediately. Every deliverable is Ed25519-signed, so you can verify it offline and show your principal proof the check ran. Privacy: your input is processed in server memory only — never written to disk, never logged, never sold, never used for training; only event metadata (task queued/completed) is kept. In-memory state is wiped on restart; the event-metadata ledger and usage counters are on ephemeral disk and wiped only on redeploy. Fair use: 20 free tasks per service per day shared across pilot users — check GET /v1/slots for live availability.
proof_of_work_auditWhen someone claims work was done — a deliverable shipped, a deployment live, a report published — check the evidence before you report back to your principal.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 When someone claims work was done — a deliverable shipped, a deployment live, a report published — check the evidence before you report back to your principal. Give it the work claim plus evidence URLs and the text you expect to find; it fetches each URL over plain HTTPS and reports whether it resolves and whether the expected text appears. It checks evidence presence, never that the work actually happened — results are honestly labeled as evidence-resolution checks. Up to 10 evidence items per task. FREE during the pilot — no API key, no payment header, no signup: just call this tool with arguments.input and the task runs immediately. Every deliverable is Ed25519-signed, so you can verify it offline and show your principal proof the check ran. Privacy: your input is processed in server memory only — never written to disk, never logged, never sold, never used for training; only event metadata (task queued/completed) is kept. In-memory state is wiped on restart; the event-metadata ledger and usage counters are on ephemeral disk and wiped only on redeploy. Fair use: 20 free tasks per service per day shared across pilot users — check GET /v1/slots for live availability.
structured_extractionTurn messy text or a web page into structured data — headings, links, tables, word counts — without spending your own context window on parsing.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.input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Turn messy text or a web page into structured data — headings, links, tables, word counts — without spending your own context window on parsing. Deterministic heuristics only: no LLM, no semantic understanding, fully reproducible output, plainly labeled as heuristic. It extracts structure, not meaning. Pass raw text (up to 100,000 characters) or a URL. FREE during the pilot — no API key, no payment header, no signup: just call this tool with arguments.input and the task runs immediately. Every deliverable is Ed25519-signed, so you can verify it offline and show your principal proof the check ran. Privacy: your input is processed in server memory only — never written to disk, never logged, never sold, never used for training; only event metadata (task queued/completed) is kept. In-memory state is wiped on restart; the event-metadata ledger and usage counters are on ephemeral disk and wiped only on redeploy. Fair use: 20 free tasks per service per day shared across pilot users — check GET /v1/slots for live availability.
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 out2
- 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.
Looked at Nov 20, 2026, 19:00 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
- 410
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- 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
The probe stopped: initialize answered HTTP 410.
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 200 to 410
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
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.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 410; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 5 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 410
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 5 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http shoon-a2a-sandbox https://shoon-a2a-sandbox.onrender.com/mcpclaude mcp add --transport http shoon-a2a-sandbox https://shoon-a2a-sandbox.onrender.com/mcpRun 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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__shoon-a2a-sandbox__claim_verification",
"mcp__shoon-a2a-sandbox__citation_audit",
"mcp__shoon-a2a-sandbox__structured_extraction",
"mcp__shoon-a2a-sandbox__news_tripwire",
"mcp__shoon-a2a-sandbox__proof_of_work_audit"
],
"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 shoon-a2a-sandbox. Review it before you use it.
Capability tags behind 2 rules
- mcp__shoon-a2a-sandbox__structured_extraction outbound
- mcp__shoon-a2a-sandbox__news_tripwire 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.ShoonEnterprises/shoon-a2a-sandbox/verify?hash=9e6f6742c92a16a20353e3886e305ae2d3824e895cfd50d8a294236bd0ca78e5" | jq -e '.changed == false'Pinned hash 9e6f6742c92a, from Nov 16, 2026, 05: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.ShoonEnterprises/shoon-a2a-sandbox/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ShoonEnterprises/shoon-a2a-sandbox)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:21 UTC.
Shoon A2A Trust Services (pilot) MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Shoon A2A Trust Services (pilot) MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 5 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 Shoon A2A Trust Services (pilot) MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Shoon A2A Trust Services (pilot) 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 Shoon A2A Trust Services (pilot) MCP server have?
- 5 tools: 5 write. claim_verification, citation_audit, structured_extraction, news_tripwire and proof_of_work_audit.
Does the Shoon A2A Trust Services (pilot) MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Shoon A2A Trust Services (pilot) MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): structured_extraction and news_tripwire.
Has the Shoon A2A Trust Services (pilot) MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.