Thred MCP Server
thred-mcp
npm
v0.3.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
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 − 5 = 95. 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 |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
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 56
Each tool and what it can reach — statically extracted from the published source.
get_accountingests untrusted inputget_billingests untrusted inputget_bill_paymentingests untrusted inputget_businessingests untrusted inputget_financial_documentingests untrusted inputarchive_accountno sensitive capabilityarchive_businessno sensitive capabilityarchive_customerno sensitive capabilityarchive_vendorno sensitive capabilitycreate_accountno sensitive capability
Show 46 more tools ↓
create_billno sensitive capabilitycreate_bill_paymentno sensitive capabilitycreate_businessno sensitive capabilitycreate_customerno sensitive capabilitycreate_invoiceno sensitive capabilitycreate_invoice_paymentno sensitive capabilitycreate_vendorno sensitive capabilitydelete_bill_paymentno sensitive capabilitydelete_invoice_paymentno sensitive capabilityget_ap_agingno sensitive capabilityget_ar_agingno sensitive capabilityget_balance_sheetno sensitive capabilityget_cash_flowno sensitive capabilityget_chart_of_accounts_hierarchyno sensitive capabilityget_customerno sensitive capabilityget_financial_summaryno sensitive capabilityget_invoiceno sensitive capabilityget_invoice_paymentno sensitive capabilityget_journal_entryno sensitive capabilityget_profit_and_lossno sensitive capabilityget_vendorno sensitive capabilitylist_bill_paymentsno sensitive capabilitylist_billsno sensitive capabilitylist_businessesno sensitive capabilitylist_chart_of_accountsno sensitive capabilitylist_customersno sensitive capabilitylist_financial_documentsno sensitive capabilitylist_invoice_paymentsno sensitive capabilitylist_invoicesno sensitive capabilitylist_journal_entriesno sensitive capabilitylist_tax_codesno sensitive capabilitylist_vendorsno sensitive capabilitythred-mcpno sensitive capabilityunarchive_customerno sensitive capabilityunarchive_vendorno sensitive capabilityupdate_accountno sensitive capabilityupdate_billno sensitive capabilityupdate_bill_paymentno sensitive capabilityupdate_businessno sensitive capabilityupdate_customerno sensitive capabilityupdate_invoiceno sensitive capabilityupdate_invoice_paymentno sensitive capabilityupdate_vendorno sensitive capabilityupload_documentno sensitive capabilityvoid_billno sensitive capabilityvoid_invoiceno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (56 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.3.0 latest |
A 95/100 | 0 | 1.8.0 | 2026-07-23 |
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 thred-mcp --onlineMore in Finance & Commerce
Security scan results for the 1money MCP server.
Security scan results for the Actual MCP server.
Security scan results for the Actual Budget MCP server.
Security scan results for the Adyen MCP server.
Security scan results for the Aelf Node Skill MCP server.
Security scan results for the Agent Skills MCP server.