https://mcp.receiptor.ai/mcp ↗
Receiptor connects AI agents to your bookkeeping workspace so they can find, review, and organize financial documents such as receipts, bills, and invoices. Use it to inspect workspace context, monitor intake sources, review extracted document data, check integrations, and prepare accountant-ready workflows through secure OAuth access to Receiptor AI.
Receiptor MCP is a remote MCP server published at mcp.receiptor.ai. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 524 ms, a delay an agent will notice. It exposes a broad tool surface of 79 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
activity_search — Description truncated mid-sentence, losing critical context about email source matching logic.documents_list-duplicates — Functionally overlaps with 'documents_scan-duplicates' without clear differentiation.integrations_unlink — Irreversible action not explicitly highlighted as a risk in description.Risk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/receiptor-ai-receiptor-mcp)<a href="https://mcpmetrics.io/servers/receiptor-ai-receiptor-mcp"><img src="https://mcpmetrics.io/badge/receiptor-ai/receiptor-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 15:07:20 | Dual-era | 200 | 524 | 200 | 526 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07 |
| 2026-09-11 13:13:33 | Dual-era | 200 | 745 | 200 | 744 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07 |
| 2026-09-11 11:20:19 | Dual-era | 200 | 467 | 200 | 465 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07 |
| 2026-09-11 09:28:19 | Dual-era | 200 | 742 | 200 | 738 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07 |
| 2026-09-11 07:35:54 | Dual-era | 200 | 212 | 200 | 219 | 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 341 | 401 | 391 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.