Hood MCP Server
hood-mcp
npm
v0.1.1
Published by nirholas — 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 servers for Robinhood Chain (chain ID 4663): a zero-config read-only data server (Stock Token quotes, multiplier-correct portfolios, memecoin launches, chain stats) and an explicitly opt-in trading server (guarded swaps + USDG trans
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 − 1 = 99. 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 |
|---|---|
| −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 2
medium Dynamic module load from a non-literal (dist/data-server.js)MTC-SRC-005
In the server's implementation (`dist/data-server.js:665`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ; const mod = await import(specifier); if (typeof mod.paywall !== "function") return passthrough; return mod
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 dist/data-server.js
medium Dynamic module load from a non-literal (dist/index.js)MTC-SRC-005
In the server's implementation (`dist/index.js:685`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ; const mod = await import(specifier); if (typeof mod.paywall !== "function") return passthrough; return mod
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 dist/index.js
Tools 13
Each tool and what it can reach — statically extracted from the published source.
execute_swapno sensitive capabilityget_chain_statsno sensitive capabilityget_coinno sensitive capabilityget_my_portfoliono sensitive capabilityget_portfoliono sensitive capabilityget_recent_launchesno sensitive capabilityget_stock_quoteno sensitive capabilityget_swap_quoteno sensitive capabilitylist_stock_tokensno sensitive capabilitylist_trending_coinsno sensitive capability
Show 3 more tools ↓
search_tokenno sensitive capabilitytransfer_usdgno sensitive capabilitywatch_launchesno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (13 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.1 latest |
A 99/100 | 2 | 1.13.0 | 2026-09-07 |
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 hood-mcp --onlineMore 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.