Metavault MCP Server
metavault-mcp
npm
v2.1.0
Published by finanzgoblin — 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.
MetaVault MCP — multi-protocol yield intelligence for AI agents (Spectra, Morpho, Pendle)
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 Hardcoded egress to an external endpoint (build/tools/calibration.js)MTC-SRC-003
In the server's implementation (`build/tools/calibration.js:265`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: arketRaw = await (await fetch(`https://api-v2.pendle.finance/core/v1/${chainId}/markets/${addr}`, { signal: AbortSignal.
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 build/tools/calibration.js
Tools 55
Each tool and what it can reach — statically extracted from the published source.
merkl_list_campaignsno sensitive capabilitymorpho_get_historyno sensitive capabilitymorpho_get_market_suppliersno sensitive capabilitymorpho_get_positionsno sensitive capabilitymorpho_get_rateno sensitive capabilitymorpho_list_marketsno sensitive capabilitymorpho_list_vaultsno sensitive capabilitymorpho_monitor_riskno sensitive capabilitymv_check_ibt_healthno sensitive capabilitymv_compare_yieldno sensitive capability
Show 45 more tools ↓
mv_get_calibrationno sensitive capabilitymv_get_curator_portfoliono sensitive capabilitymv_get_position_mapno sensitive capabilitymv_get_protocol_contextno sensitive capabilitymv_plan_rolloverno sensitive capabilitymv_scan_curator_opportunitiesno sensitive capabilitypendle_get_best_fixed_yieldsno sensitive capabilitypendle_get_looping_strategyno sensitive capabilitypendle_get_market_capacityno sensitive capabilitypendle_get_market_detailsno sensitive capabilitypendle_get_market_historyno sensitive capabilitypendle_get_portfoliono sensitive capabilitypendle_get_protocol_statsno sensitive capabilitypendle_get_yield_curveno sensitive capabilitypendle_list_expiring_marketsno sensitive capabilitypendle_list_marketsno sensitive capabilitypendle_quote_tradeno sensitive capabilitypendle_scan_opportunitiesno sensitive capabilitypendle_scan_yt_arbitrageno sensitive capabilitypendle_simulate_tradeno sensitive capabilityspectra_compare_yieldno sensitive capabilityspectra_get_address_activityno sensitive capabilityspectra_get_best_fixed_yieldsno sensitive capabilityspectra_get_curator_dashboardno sensitive capabilityspectra_get_gauge_votesno sensitive capabilityspectra_get_looping_strategyno sensitive capabilityspectra_get_onchain_activityno sensitive capabilityspectra_get_pool_activityno sensitive capabilityspectra_get_pool_capacityno sensitive capabilityspectra_get_pool_volumeno sensitive capabilityspectra_get_portfoliono sensitive capabilityspectra_get_protocol_statsno sensitive capabilityspectra_get_pt_detailsno sensitive capabilityspectra_get_ve_infono sensitive capabilityspectra_get_yield_curveno sensitive capabilityspectra_list_chainsno sensitive capabilityspectra_list_expiring_poolsno sensitive capabilityspectra_list_metavaultsno sensitive capabilityspectra_list_poolsno sensitive capabilityspectra_model_metavaultno sensitive capabilityspectra_quote_tradeno sensitive capabilityspectra_scan_opportunitiesno sensitive capabilityspectra_scan_yt_arbitrageno sensitive capabilityspectra_simulate_tradeno sensitive capabilityspectra_stress_test_vaultno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (55 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 |
|---|---|---|---|---|
v2.1.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 metavault-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.