Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Shoon A2A Trust Services (pilot)

by ShoonEnterprisesversion 0.1.0i★ –iRuns in the cloud
Registry nameio.github.ShoonEnterprises/shoon-a2a-sandbox

Install

Overview

Description from the maker (original English)

Five trust services for agents: claim checks, citation audits, extraction, tripwires, work audits.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Developer tools
  • You need to fill in: X-API-KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Run this in your terminal

claude mcp add --transport http shoon-a2a-sandbox https://shoon-a2a-sandbox.onrender.com/mcp --header 'X-API-KEY: your-value'

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "shoon-a2a-sandbox": {
      "url": "https://shoon-a2a-sandbox.onrender.com/mcp",
      "headers": {
        "X-API-KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "shoon-a2a-sandbox": {
      "type": "http",
      "url": "https://shoon-a2a-sandbox.onrender.com/mcp",
      "headers": {
        "X-API-KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • X-API-KEY secret HTTP header
    Pilot API key for the human-style flow (header). Omit when using the X-PAYMENT machine flow: quote first via POST /quote, then authorize the quote on POST /execute.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account ShoonEnterprises, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Developer toolsi

  • More stars than 0% of the other 4930 servers in this category
  • Published to the registry more recently than 48% of the other 4930 servers in this category
  • Basic checks equal to or better than 100% of the other 4930 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Shoon A2A Trust Services (pilot) safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: X-API-KEY

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.2KUpdated 5 days ago

Computer or cloud

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 709.6K/wk★ 10.2KUpdated 17 days ago

Runs on your computer

Cloudflare MCP

Cloudflare MCP servers

by cloudflareGrowing★ 4.4KUpdated 14 months ago

Runs in the cloud✓ mcp.cloudflare.com

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

A2A Service System — Phase 0 Sandbox (local test only)

TEST SANDBOX. Everything free ($0.00), testnet semantics, binds to 127.0.0.1 only. No real crypto, no real payments, no external accounts, no money movement. Nothing here is public or commercial.

Run

cd ~/workspace/compound/a2a-economy/sandbox

pip3 install --user --break-system-packages -r requirements.txt

admin secret is REQUIRED — the server refuses to start without it

export A2A_SANDBOX_ADMIN="$(cat ~/.config/a2a-sandbox-admin)" python3 -m uvicorn app:app --host 127.0.0.1 --port 8741

Generate the secret once (stored with owner-only permissions, never in chat/logs):

mkdir -p ~/.config

python3 -c "import secrets; print(secrets.token_hex(32))" > ~/.config/a2a-sandbox-admin chmod 600 ~/.config/a2a-sandbox-admin

Then in another terminal:

# machine-readable catalog (Tier A)

curl -s http://127.0.0.1:8741/v1/catalog.json | head -c 600

public free-slot counter

curl -s http://127.0.0.1:8741/v1/slots

synthetic buyer harness (full loop per service, green/red per stage)

python3 harness.py

human test page

open http://127.0.0.1:8741/test.html in a browser (test API key prefilled)

What is REAL vs STUBBED

Real (protocol fully implemented):

  • POST /quote — free, zero-token, formula-based binding quote, 15-min expiry, input-cap + policy checks, ledger entry
  • POST /execute — 402 without payment (x402-shaped response), mock commit-then-settle authorization verification (structure + quote match + validBefore expiry), 202 + task_id, async job queue, Ed25519-signed deliverables, settle event
  • Quota enforcement: identity required, ≤10 tasks/day/wallet-or-API-key, ≤20/day/service with public slots counter, global daily token budget with auto-pause
  • Kill switch as feature flag (POST /v1/admin/kill / /v1/admin/resume, token via A2A_SANDBOX_ADMIN env — the server refuses to start without it); no auto-resume
  • SSRF protection: task-supplied URLs are resolved and every address must be public (loopback, private LAN, link-local and cloud-metadata ranges refused, including via redirects); non-http(s) schemes refused
  • Append-only JSONL ledger + CSV/JSON tax-export stub (/v1/ledger/export)
  • Per-task privacy (locked per buyer): every task gets a random 256-bit read_token at accept time (returned in the 202 response — keep it secret, treat it like a password). Task status, deliverable, signature check and that task's ledger entries all require it via the Authorization: Bearer header. Header-only by design: tokens in URLs would land in server access logs. No token → 401. The full ledger (all buyers) is admin-only (X-Admin-Token header). Task and quote IDs are 128-bit random; admin token comparisons are constant-time.
  • Persistent quotas: usage counters and pause state live in SQLite (data/quotas.db) — a restart no longer resets daily caps or the kill-switch state.
  • MCP (Model Context Protocol): POST /mcp speaks Streamable HTTP (stateless JSON-RPC 2.0): initialize, tools/list (the 5 services), tools/call (runs quote → accept → wait synchronously, returns the signed deliverable). Two auth flows: human one-step (X-API-KEY header + arguments.input), or machine two-step (POST /quote first, then tools/call with arguments.quote_id and the X-PAYMENT header authorizing that quote). Calls count as mcp origin traffic.
  • Origin tracking: every accepted task is counted by channel — human, machine, mcp — visible at admin-only GET /v1/admin/stats alongside quota usage.
  • Tier A machine-readable files: /v1/catalog.json, /.well-known/agent.json, /llms.txt, /v1/openapi.json, /robots.txt (AI crawlers allowed)
  • Honest service logic: real HTTPS fetches of user-supplied URLs; results plainly labeled

Stubbed / simulated:

  • The EIP-3009 authorization is a mock (base64 JSON in X-PAYMENT header) — verification checks shape, quote match and expiry, not an on-chain signature
  • Settlement is a $0.00 ledger event under "testnet semantics" — no chain interaction, no faucet funds
  • Token budget is simulated (estimated from input bytes), not real LLM tokens
  • News tripwires check on demand; no background scheduler yet
  • No facilitator, no escrow, no webhooks delivery (webhook_url accepted but not called), no Postgres/Inngest
  • Human pilot API keys are fixed test keys, not issued per user

Honesty rules (enforced in code)

  • Every deliverable carries "sandbox": true
  • Claim verification: "supported" = quoted text found verbatim in the cited source, NOT "the claim is true". Uncheckable → "unverified"
  • Citation audit: reports real HTTP status + verbatim text match
  • Proof-of-work: evidence-resolution check only; never claims work was verified
  • QA gate: fails any result missing the sandbox flag or required output keys

Files

  • app.py — FastAPI gateway
  • catalog.py — the 5 service definitions (schemas, caps, slots)
  • services.py — honest minimal service logic + QA gate
  • signing.py — Ed25519 key mgmt
  • ledger.py — append-only JSONL ledger
  • quotas.py — scarcity quotas, token budget, kill switch
  • harness.py — synthetic buyer harness
  • static/ — agent.json, llms.txt, robots.txt, test.html (human page)
  • data/ — keys + ledger.jsonl (created at runtime, git-ignored by convention)
Ask PopNx