Recite MCP Server
recite-mcp
PyPI
v0.1.12
Published by rivradev — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Local MCP server for Recite receipt processing
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 57
Each tool and what it can reach — statically extracted from the published source.
create_webhooknetwork egressdelete_webhooknetwork egressadd_ledger_correctionno sensitive capabilitycreate_categoryno sensitive capabilitycreate_projectno sensitive capabilitycreate_reconciliation_linkno sensitive capabilitycreate_ruleno sensitive capabilitycreate_transactionno sensitive capabilitycreate_vendorno sensitive capabilitydelete_bank_statementno sensitive capability
Show 47 more tools ↓
delete_bank_transactionno sensitive capabilitydelete_categoryno sensitive capabilitydelete_projectno sensitive capabilitydelete_reconciliation_linkno sensitive capabilitydelete_ruleno sensitive capabilitydelete_transactionno sensitive capabilitydelete_vendorno sensitive capabilityexport_bank_statementno sensitive capabilityexport_ledgerno sensitive capabilityexport_reconciliationno sensitive capabilityexport_transactionsno sensitive capabilityget_bank_statementno sensitive capabilityget_bank_transactionno sensitive capabilityget_batch_scan_resultsno sensitive capabilityget_batch_scan_statusno sensitive capabilityget_categoriesno sensitive capabilityget_configno sensitive capabilityget_reconciliation_recommendationsno sensitive capabilityget_reconciliation_summaryno sensitive capabilityget_scanno sensitive capabilityget_summaryno sensitive capabilityget_transactionno sensitive capabilityget_usageno sensitive capabilityget_vendorsno sensitive capabilityimport_transactionsno sensitive capabilitylist_bank_statementsno sensitive capabilitylist_bank_transactionsno sensitive capabilitylist_memoryno sensitive capabilitylist_projectsno sensitive capabilitylist_reconciliation_linksno sensitive capabilitylist_rulesno sensitive capabilitylist_transactionsno sensitive capabilitylist_webhooksno sensitive capabilityprocess_receiptno sensitive capabilityprocess_receipts_batchno sensitive capabilityrun_auto_matchno sensitive capabilityscan_receiptno sensitive capabilitysubmit_batch_scansno sensitive capabilitysummarize_ledgerno sensitive capabilityupdate_bank_transactionno sensitive capabilityupdate_memoryno sensitive capabilityupdate_projectno sensitive capabilityupdate_reconciliation_linkno sensitive capabilityupdate_ruleno sensitive capabilityupdate_transactionno sensitive capabilityupload_bank_statementno sensitive capabilityvalidate_setupno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (57 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.12 latest |
A 96/100 | 0 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan recite-mcp --online --registry pypiMore in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.