# Metruvo portfolio analysis (remote · metruvo.com)

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

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `metruvo.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/com-metruvo-fund-comparison/api-mcp.md), [page](https://verifymcp.io/servers/com-metruvo-fund-comparison/api-mcp)

## Channel facts

- Endpoint: `https://metruvo.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 80/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 40% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-metruvo-fund-comparison 'https://metruvo.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-metruvo-fund-comparison": {
      "url": "https://metruvo.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-metruvo-fund-comparison": {
      "type": "http",
      "url": "https://metruvo.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-metruvo-fund-comparison]
url = "https://metruvo.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-metruvo-fund-comparison": {
      "type": "remote",
      "url": "https://metruvo.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-metruvo-fund-comparison --url 'https://metruvo.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-metruvo-fund-comparison:
    url: "https://metruvo.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-metruvo-fund-comparison": {
      "Transport": "http",
      "Url": "https://metruvo.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-metruvo-fund-comparison -t streamable-http -u 'https://metruvo.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-metruvo-fund-comparison": {
      "type": "http",
      "url": "https://metruvo.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 73, +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.

### 2026-11-03 (score 72, +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.

### 2026-10-31 (score 71, +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.

### 2026-10-29 (score 70, +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.

### 2026-10-27 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 68)

First indexed and scored.

## MCP tools (4)

### `search_funds` (~55 tokens)

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

Input parameters:

- `limit` (integer)
- `query` (string, required)

### `xray_portfolio` (~124 tokens)

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.

Input parameters:

- `baseCurrency` (string)
- `holdings` (array, required)

### `compare_funds` (~164 tokens)

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.

Input parameters:

- `isinA` (string): ISIN with a valid check digit.
- `isinB` (string): ISIN with a valid check digit.
- `tickerA` (string): Exchange ticker, e.g. VWCE or SWDA.L; may match listings on several exchanges.
- `tickerB` (string): Exchange ticker, e.g. VWCE or SWDA.L; may match listings on several exchanges.

### `rank_funds` (~104 tokens)

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.

Input parameters:

- `criteria` (array, required)
- `isins` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-metruvo-fund-comparison/api-mcp#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 71
- 2026-10-30: 70
- 2026-10-29: 70
- 2026-10-28: 69
- 2026-10-27: 69
- 2026-10-26: 68

## 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.

### What did VerifyMCP test on the Metruvo portfolio analysis MCP server?

VerifyMCP ran 13 checks on Metruvo portfolio analysis, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://metruvo.com/api/mcp
- Website: https://metruvo.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-metruvo-fund-comparison/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-metruvo-fund-comparison/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-metruvo-fund-comparison/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-metruvo-fund-comparison/api-mcp