Uk Due Diligence MCP Server
uk-due-diligence-mcp
PyPI
v1.3.0
Published by paulieb89 — 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.
UK due diligence MCP server — Companies House, Charity Commission, HMLR, Gazette, HMRC VAT
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 1
low Shell/command execution in packaging/dev tooling (tests/test_packaging.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_packaging.py:40`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: "install" build = subprocess.run( ["uv", "build", "--wheel", "-o", str(dist_dir)], cwd=REPO_ROOT,
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server tests/test_packaging.py
Tools 18
Each tool and what it can reach — statically extracted from the published source.
fetchingests untrusted inputcharity_profileno sensitive capabilitycharity_searchno sensitive capabilitycompany_chargesno sensitive capabilitycompany_filing_documentno sensitive capabilitycompany_filing_historyno sensitive capabilitycompany_officersno sensitive capabilitycompany_profileno sensitive capabilitycompany_pscno sensitive capabilitycompany_searchno sensitive capability
Show 8 more tools ↓
disqualified_profileno sensitive capabilitydisqualified_searchno sensitive capabilitygazette_insolvencyno sensitive capabilitygazette_noticeno sensitive capabilityland_title_searchno sensitive capabilityofficer_appointmentsno sensitive capabilitysanctions_screenno sensitive capabilitysearchno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (18 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 4
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.3.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-08-25 |
v1.2.0 |
A 96/100 | 0 | 1.12.1 | 2026-07-31 |
v1.1.1 |
A 96/100 | 0 | 1.12.1 | 2026-07-29 |
v1.0.8 |
A 96/100 | 0 | 1.12.1 | 2026-07-27 |
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 uk-due-diligence-mcp --online --registry pypiMore in Data Science & ML
MCP server for 2s.io — 575+ pay-per-call tools for AI agents — ground-truth data, AI gateway, and agent infra (storage, locks, queues, watchers). x402 USDC on Base/Solana, no API keys, upto usage billing, free trials.
ArXiv preprints + Google Scholar papers, with citation counts in one query.
Add MCP servers to your favorite coding agents with a single command.
Help agents automatically write and test stories for your UI components
Model Context Protocol server for AI-Archive platform - enables AI agents to discover, submit, and review research papers
MCP server for Semantic Scholar research workflows with stdio and Streamable HTTP transports.