I
iwasinnam2/metrecept-opensource
★ 1·updated 2026-10-27
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 1 ★ · iwasinnam2/metrecept-opensource · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
iwasinnam2/metrecept-opensource;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Metrecept — open client tools
Excerpted from the repository README (abridged)
Proof, not trust. Metrecept issues a signed Ed25519 receipt (compact JWS) for every call an autonomous AI agent makes through it — model completions, compliant public-web fetches, and calls to third-party business APIs — and can roll a whole agent run into one signed session receipt. Anyone can verify a receipt against Metrecept's published public keys, with no account and no Metrecept code.
Metrecept is a recorder, not a governor: it does not stop a bad call, and a receipt does not grade the work. It proves what was called, when, and what it cost. It is built for autonomous AI agent companies that need a record a customer or auditor can check, and for stablecoin and settlement firms that need a verifiable record of each agent-initiated call.
Site: https://metrecept.co.uk · API: https://api.metrecept.co.uk/v1 · Docs: https://metrecept.co.uk/docs
## What's in this repo
This is the public, MIT-licensed thin client for Metrecept — an MCP server (23 metrecept_ tools in three toolsets: core, cache, receipts), Python and TypeScript SDK helpers, an n8n node, receipt verifiers and demos, plus a redacted tour of the architecture behind the hosted gateway. The hosted gateway is proprietary, and every real call needs a Metrecept API key. Nothing here requires trusting prose: every claim below links to a command you can run yourself.
| Path | What it is |
| docs/ | Architecture exhibition — how the gateway is built, what a signed receipt is, how compliant web fetch works, why this shape instead of a routing proxy |
| demo/ | Runnable scripts that prove the claims against the live hosted API — no Metrecept code required to verify a receipt |
| sdks/python/ | Python OpenAI base_url helper (at-utility-sdk on PyPI) |
| sdks/typescript/ | TypeScript/JS helper (@at-utility/sdk on npm) |
| packages/metrecept-mcp/ | MCP server for Cursor/Claude agents (pip install metrecept-mcp; command metrecept-mcp) |
| templates/ | Ready-to-clone agent integration templates |
| actions/receipt-link/ | GitHub Action: comment the run's signed session receipt on a pull request as a link (https://metrecept.co.uk/verify# ) — whoever opens it checks the Ed25519 signature in their browser against the public key directory, no account |
## What's not in this repo
The gateway (gateway-rs Rust edge + Python control plane), the cache engine internals, the adaptive model routing, and the billing/compliance core are proprietary and stay closed — no self-hosting option, and that's a deliberate, permanent split, not a staged reveal. What's below is a genuine architectural tour of how the gateway is shaped and what it commits to publicly, not a copy of the implementation. See LICENSE and NOTICE for the exact split.
## Architecture at a glance
mermaid
flowchart TB
clients["Clients Shell · MCP · SDK"]
subgraph ephemeral ["Ephemeral Side"]
edge["Edge (Rust) HIT path"]
trees["Cache trees"]
end
subgraph pipeline ["Pipeline System"]
auth["Tenant / keys / org"]
meters["Meters -> ledger"]
ingest["Compliance ingest"]
route["Provider route"]
trust["Signed receipts (JWKS)"]
end
labs["Upstream labs (BYOK)"]
web["Public web"]
clients --> edge
edge -->|HIT| trust
Metrecept is a recorder, not a governor: it does not stop a bad call, and a receipt does not grade the work. It proves what was called, when, and what it cost. It is built for autonomous AI agent companies that need a record a customer or auditor can check, and for stablecoin and settlement firms that need a verifiable record of each agent-initiated call.
Site: https://metrecept.co.uk · API: https://api.metrecept.co.uk/v1 · Docs: https://metrecept.co.uk/docs
## What's in this repo
This is the public, MIT-licensed thin client for Metrecept — an MCP server (23 metrecept_ tools in three toolsets: core, cache, receipts), Python and TypeScript SDK helpers, an n8n node, receipt verifiers and demos, plus a redacted tour of the architecture behind the hosted gateway. The hosted gateway is proprietary, and every real call needs a Metrecept API key. Nothing here requires trusting prose: every claim below links to a command you can run yourself.
| Path | What it is |
| docs/ | Architecture exhibition — how the gateway is built, what a signed receipt is, how compliant web fetch works, why this shape instead of a routing proxy |
| demo/ | Runnable scripts that prove the claims against the live hosted API — no Metrecept code required to verify a receipt |
| sdks/python/ | Python OpenAI base_url helper (at-utility-sdk on PyPI) |
| sdks/typescript/ | TypeScript/JS helper (@at-utility/sdk on npm) |
| packages/metrecept-mcp/ | MCP server for Cursor/Claude agents (pip install metrecept-mcp; command metrecept-mcp) |
| templates/ | Ready-to-clone agent integration templates |
| actions/receipt-link/ | GitHub Action: comment the run's signed session receipt on a pull request as a link (https://metrecept.co.uk/verify# ) — whoever opens it checks the Ed25519 signature in their browser against the public key directory, no account |
## What's not in this repo
The gateway (gateway-rs Rust edge + Python control plane), the cache engine internals, the adaptive model routing, and the billing/compliance core are proprietary and stay closed — no self-hosting option, and that's a deliberate, permanent split, not a staged reveal. What's below is a genuine architectural tour of how the gateway is shaped and what it commits to publicly, not a copy of the implementation. See LICENSE and NOTICE for the exact split.
## Architecture at a glance
mermaid
flowchart TB
clients["Clients Shell · MCP · SDK"]
subgraph ephemeral ["Ephemeral Side"]
edge["Edge (Rust) HIT path"]
trees["Cache trees"]
end
subgraph pipeline ["Pipeline System"]
auth["Tenant / keys / org"]
meters["Meters -> ledger"]
ingest["Compliance ingest"]
route["Provider route"]
trust["Signed receipts (JWKS)"]
end
labs["Upstream labs (BYOK)"]
web["Public web"]
clients --> edge
edge -->|HIT| trust
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/iwasinnam2-metrecept-opensource/)
- Source
- awesome · https://github.com/iwasinnam2/metrecept-opensource
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.