Matcher MCP Server
@lerianstudio/matcher-mcp
npm
v1.4.1
Published by @lerianstudio — 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.
Model Context Protocol server for the Matcher reconciliation engine
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 90
Each tool and what it can reach — statically extracted from the published source.
context_getingests untrusted inputdispute_getingests untrusted inputexception_getingests untrusted inputexception_historyingests untrusted inputfee_rule_getingests untrusted inputfee_schedule_getingests untrusted inputfield_map_getingests untrusted inputingestion_job_getingests untrusted inputmatch_rule_getingests untrusted inputmatch_run_getingests untrusted input
Show 80 more tools ↓
source_getingests untrusted inputcontext_archiveno sensitive capabilitycontext_createno sensitive capabilitycontext_listno sensitive capabilitycontext_restoreno sensitive capabilitycontext_setup_progressno sensitive capabilitycontext_updateno sensitive capabilitydashboard_aggregatesno sensitive capabilitydashboard_cash_impactno sensitive capabilitydashboard_match_rateno sensitive capabilitydashboard_metricsno sensitive capabilitydashboard_slano sensitive capabilitydashboard_source_breakdownno sensitive capabilitydashboard_volumeno sensitive capabilitydispute_closeno sensitive capabilitydispute_listno sensitive capabilitydispute_submit_evidenceno sensitive capabilityexception_add_commentno sensitive capabilityexception_adjust_entryno sensitive capabilityexception_bulk_assignno sensitive capabilityexception_bulk_dispatchno sensitive capabilityexception_bulk_resolveno sensitive capabilityexception_delete_commentno sensitive capabilityexception_dispatchno sensitive capabilityexception_force_matchno sensitive capabilityexception_listno sensitive capabilityexception_list_commentsno sensitive capabilityexception_open_disputeno sensitive capabilityfee_rule_createno sensitive capabilityfee_rule_deleteno sensitive capabilityfee_rule_listno sensitive capabilityfee_rule_updateno sensitive capabilityfee_schedule_createno sensitive capabilityfee_schedule_deleteno sensitive capabilityfee_schedule_listno sensitive capabilityfee_schedule_simulateno sensitive capabilityfee_schedule_updateno sensitive capabilityfield_map_createno sensitive capabilityfield_map_deleteno sensitive capabilityfield_map_listno sensitive capabilityfield_map_updateno sensitive capabilityingestion_job_errors_listno sensitive capabilityingestion_job_transactions_listno sensitive capabilityingestion_jobs_listno sensitive capabilityingestion_transaction_ignoreno sensitive capabilityingestion_transactions_searchno sensitive capabilityingestion_uploadno sensitive capabilityingestion_upload_beginno sensitive capabilitymatch_rule_createno sensitive capabilitymatch_rule_deleteno sensitive capabilitymatch_rule_listno sensitive capabilitymatch_rule_reorderno sensitive capabilitymatch_rule_updateno sensitive capabilitymatch_run_groupsno sensitive capabilitymatch_run_listno sensitive capabilitymatch_run_startno sensitive capabilitymatcher_describe_operationno sensitive capabilitymatcher_invokeno sensitive capabilitymatcher_list_operationsno sensitive capabilitymcp_pingno sensitive capabilitymcp_whoamino sensitive capabilitynext_stepno sensitive capabilityreport_count_exceptionsno sensitive capabilityreport_count_matchedno sensitive capabilityreport_count_transactionsno sensitive capabilityreport_count_unmatchedno sensitive capabilityreport_export_exceptionsno sensitive capabilityreport_export_matchedno sensitive capabilityreport_export_summaryno sensitive capabilityreport_export_unmatchedno sensitive capabilityreport_export_varianceno sensitive capabilityreport_matchedno sensitive capabilityreport_summaryno sensitive capabilityreport_unmatchedno sensitive capabilityreport_varianceno sensitive capabilitysource_archiveno sensitive capabilitysource_createno sensitive capabilitysource_listno sensitive capabilitysource_restoreno sensitive capabilitysource_updateno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (90 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 2
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 |
|---|---|---|---|---|
v1.4.1 latest |
A 96/100 | 0 | 1.13.0 | 2026-09-07 |
v1.4.0 |
A 96/100 | 0 | 1.12.1 | 2026-08-02 |
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 @lerianstudio/matcher-mcp --onlineMore in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.