agent-services-mcp
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@agent-services-mcpshow me the quality rubric"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
agent-services-mcp
A single thin MCP (Model Context Protocol) server that exposes two existing services as discoverable tools, so AI agents and MCP-compatible clients can find and use them through one connection:
provenance-receipts — certifies content origin; returns an Ed25519-signed receipt.
quality-gate — scores content quality against a published rubric; returns an Ed25519-signed score receipt.
It is a thin wrapper. Every tool forwards an HTTP call to the underlying Worker and returns its response verbatim. It does not reimplement signing, scoring, or payment logic — those live in the two services. The honesty about what each service proves carries through to the tool descriptions.
What the wrapped services prove (and do not)
Provenance: proves the content is unmodified (SHA-256 hash) and the receipt was issued by the service's key. The
generator_metadatais caller-attested — it proves you claimed it, not that a specific model ran. Not AI-detection, not a truth guarantee.Quality: a reproducible score against the published rubric (clarity, completeness, internal consistency, obvious-error freedom). Not absolute truth, not an external standard, not a fact-check. Read the rubric via the
get_quality_rubrictool.
Related MCP server: protect-mcp
Tools
Tool | Forwards to | Paid? | Input |
| provenance-receipts | yes (x402) |
|
| provenance-receipts | no |
|
| quality-gate | yes (x402) |
|
| quality-gate | no |
|
| quality-gate | no | none |
Full descriptions and Zod input schemas: src/tools.ts. Each
tool returns the service's raw JSON (or markdown, for the rubric) as text. A
non-2xx response from a service (including a 402 Payment Required) is surfaced
with isError: true and the response body preserved, so the caller can react.
Configuration
The two service URLs are environment-configurable (no secrets — just base URLs):
Env var | Live (deployed) | Local dev fallback |
|
|
|
|
|
|
.env.example and the client config below point at the live deployments. If
the vars are unset, the server falls back to localhost for local wrangler dev
(both Workers default to :8787, so run quality-gate on :8788 to avoid a clash).
Against the live services, the paid tools (
certify_provenance,score_quality) require x402 — this wrapper forwards the request and holds no wallet, so without anX-PAYMENTthey return a402(the payment requirements) surfaced asisError. The free tools work as normal.
Quickstart (local)
# 1. Build the MCP server
npm install
npm run build # -> dist/index.js
# 2. In separate terminals, run the two services (free; payments off)
# (provenance-receipts) npm run dev # http://localhost:8787
# (quality-gate) npx wrangler dev --port 8788 # http://localhost:8788
# 3a. Smoke-test the free tool paths through an MCP stdio client
node scripts/test-client.mjs
# 3b. (optional, costs ~$0.012) prove the paid score_quality path end-to-end
node scripts/test-score.mjs
# 3c. Smoke-test the wrapper against the LIVE deployed services (free — the
# paid tools return a forwarded 402; no payment, no scoring call)
node scripts/test-live.mjsscripts/test-client.mjs exercises the free tools locally; scripts/test-score.mjs
makes one real Anthropic scoring call through score_quality;
scripts/test-live.mjs points the wrapper at the deployed workers.dev URLs and
asserts the free tools work and the paid tools forward the x402 402.
Connecting an MCP client (stdio)
This server speaks MCP over stdio (stdin/stdout). Any MCP client launches it
as a subprocess. Example for a Claude Desktop / Claude Code style
mcpServers config:
{
"mcpServers": {
"agent-services": {
"command": "node",
"args": ["C:\\Users\\Gareth\\agent-services-mcp\\dist\\index.js"],
"env": {
"PROVENANCE_URL": "https://provenance-receipts.gpmiddleton71.workers.dev",
"QUALITY_GATE_URL": "https://quality-gate.gpmiddleton71.workers.dev"
}
}
}
}Run
npm run buildfirst sodist/index.jsexists.The client connects, calls
tools/list(it will see the 5 tools above), and invokes them viatools/call.The underlying services must be reachable at the configured URLs when a tool is called.
Logs go to stderr; stdout is reserved for the MCP protocol.
Programmatically, connect with the SDK's Client + StdioClientTransport
(command: "node", args: ["dist/index.js"]) — see scripts/test-client.mjs.
x402 payments (forwarded, not handled here)
The paid endpoints (/v1/certify, /v1/score) are gated by
x402 on the underlying services. This wrapper
forwards requests and does not hold a wallet. If a service has payments
enabled and no valid X-PAYMENT is supplied, it returns 402 with the payment
requirements — the wrapper surfaces that as isError with the requirements body
intact. Settling a payment (signing an x402 authorization) is the client's
responsibility against the underlying service. See each service's README.md /
docs/API.md for the x402 details. Base Sepolia testnet only — no mainnet.
Verifying receipts independently
The receipts returned by certify_provenance and score_quality are
Ed25519-signed and verifiable without trusting any of these services — re-hash
the content and check the signature against the service's public key. Each service
ships a runnable independent verifier and recipe: see
provenance-receipts/docs/VERIFYING.md
and quality-gate/docs/VERIFYING.md.
Build status
Step 1 — skeleton + tool definitions (
src/tools.ts)Step 2 — tool handlers (HTTP forwarding) + local smoke test
Step 3 — README: what it is, the tools, and how an MCP client connects
Live — pointed at the deployed services (
*.gpmiddleton71.workers.dev) and verified end-to-end viascripts/test-live.mjs: free tools work; paid tools forward the x402402.
All five tool paths verified locally (including one paid score_quality call
end-to-end through the wrapper) and against the live deployments.
Stack
Official MCP SDK:
@modelcontextprotocol/sdkv1.29.0 (TypeScript), stdio transport,zodinput schemas.Node ESM + TypeScript (
tsc→dist/).
Project layout
agent-services-mcp/
├── src/
│ ├── index.ts # MCP server: registers tools, forwards HTTP, stdio transport
│ └── tools.ts # the 5 tool definitions (names, descriptions, Zod schemas)
├── scripts/
│ ├── test-client.mjs # MCP stdio client — free tool smoke test (local)
│ ├── test-score.mjs # MCP stdio client — one paid score_quality e2e check
│ └── test-live.mjs # MCP stdio client — against the live deployed services
├── package.json
├── tsconfig.json
├── .gitignore
└── .env.example # PROVENANCE_URL, QUALITY_GATE_URLMaintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Gareth1953/agent-services-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server