Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Metruvo portfolio analysis

REMOTE · METRUVO.COM

Portfolio analysis from published fund data: charges, exposure and overlap. Read-only.

Available components

+3 this week 73 Trust /100

Last scanned (6 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 544 tokens (~136/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 40% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 26 Oct 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://metruvo.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=metruvo.com CN=YR1,O=Let's Encrypt,C=US 14 Sept 2026 13 Dec 2026 RSA 2048 SHA256-RSA 533446698df0be2b7152131190a512eaecb
SANs: metruvo.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of metruvo.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
metruvo.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://metruvo.com/api/mcp Verified 200
http (plaintext) http://metruvo.com/api/mcp HTTPS enforced 308 https://metruvo.com/api/mcp
MCP tools · 4 exposed · ~447 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_funds ~164

Analyze two ETFs as a 50/50 portfolio, with overlap and issuer facts including dated ongoing charges side by side, and each fund's own region and sector exposure. Identify each side with exactly one ISIN or ticker; a ticker can be ambiguous across exchanges. Unknown facts remain null. Returns checkUrl: a shareable link to the same result.

NameTypeReqDescription
isinAstring–ISIN with a valid check digit.
isinBstring–ISIN with a valid check digit.
tickerAstring–Exchange ticker, e.g. VWCE or SWDA.L; may match listings on several exchanges.
tickerBstring–Exchange ticker, e.g. VWCE or SWDA.L; may match listings on several exchanges.

No output schema declared.

No examples provided.

rank_funds ~104

Sort 2 to 10 funds by up to three published facts: ongoing charge, US share, pairwise overlap and holdings count. Rows follow the criteria in order. A missing fact sorts last and stays null; it is never estimated. Rates are decimal fractions (0.07 = 7%). Analysis based on published fund data. Returns checkUrl: a shareable link to the same result.

NameTypeReqDescription
criteriaarrayyes–
isinsarrayyes–

No output schema declared.

No examples provided.

search_funds ~55

Search the published instrument catalogue by name, ISIN or ticker; includes currency and listing identifiers. Returns checkUrl: a shareable link to the same result.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

xray_portfolio ~124

Analyze free-preview ETF overlap/concentration findings, known ongoing charges and regional/sector exposures from published evidence. Identify each holding with exactly one ISIN or ticker; a ticker can be ambiguous across exchanges. Use positive relative weights, values in one base currency, or omit all amounts for equal weights. Never mix weights and values. At most 10 distinct tickers per call. Dates, coverage and all data gaps accompany the result. Returns checkUrl: a shareable link to the same result.

NameTypeReqDescription
baseCurrencystring––
holdingsarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the Metruvo portfolio analysis MCP server?

Metruvo portfolio analysis is a hosted endpoint at https://metruvo.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · metruvo.com

# add to Claude Code
claude mcp add --transport http com-metruvo-fund-comparison 'https://metruvo.com/api/mcp'
Common questions

What is the Metruvo portfolio analysis MCP server?

Metruvo portfolio analysis is an MCP server listed in the public MCP registry as com.metruvo/fund-comparison. Portfolio analysis from published fund data: charges, exposure and overlap. Read-only. This page covers its hosted endpoint (https://metruvo.com/api/mcp).

Is the Metruvo portfolio analysis MCP server safe to use?

Metruvo portfolio analysis scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Metruvo portfolio analysis MCP server expose?

Metruvo portfolio analysis exposes 4 tools: search_funds, xray_portfolio, compare_funds, rank_funds. Their descriptions and schemas cost roughly 447 tokens of context every time the server is loaded.

Does the Metruvo portfolio analysis MCP server require authentication?

No. We connected to Metruvo portfolio analysis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Metruvo portfolio analysis MCP server still maintained?

Metruvo portfolio analysis is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.