Near Hydra MCP Server
near-hydra-mcp
npm
v0.5.0
Published by nikshepsvn — 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.
MCP server exposing the NEAR stack (accounts, Chain Signatures, NEAR Intents) as agent tools.
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
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([hydra_swap_execute]) co-exist with external-action tools ([hydra_swap_quote, hydra_send_evm, hydra_swap_execute]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [hydra_swap_execute] → sinks [hydra_swap_quote, hydra_send_evm, hydra_swap_execute]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow hydra_swap_execute → hydra_swap_quote
Tools 21
Each tool and what it can reach — statically extracted from the published source.
hydra_swap_executeingests untrusted inputnetwork egresshydra_send_evmnetwork egresshydra_swap_quotenetwork egresshydra_account_balance_all_chainsno sensitive capabilityhydra_account_viewno sensitive capabilityhydra_address_balanceno sensitive capabilityhydra_address_deriveno sensitive capabilityhydra_config_showno sensitive capabilityhydra_contract_callno sensitive capabilityhydra_contract_viewno sensitive capability
Show 11 more tools ↓
hydra_create_agent_keyno sensitive capabilityhydra_ensure_gasno sensitive capabilityhydra_send_btcno sensitive capabilityhydra_send_ftno sensitive capabilityhydra_send_nearno sensitive capabilityhydra_send_solanano sensitive capabilityhydra_send_splno sensitive capabilityhydra_sign_messageno sensitive capabilityhydra_swap_statusno sensitive capabilityhydra_swap_submit_depositno sensitive capabilityhydra_swap_tokensno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (21 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.5.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-08 |
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 near-hydra-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.