PortfolioFit
REMOTE · PORTFOLIO.FIT · SCANNED SEP 20
Check normalized portfolios against mandates and calculate allocation constraints.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 203 tokens (~101/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the PortfolioFit MCP server?
PortfolioFit is a hosted endpoint at https://portfolio.fit/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 · portfolio.fit
claude mcp add --transport http fit-portfolio-portfoliofit 'https://portfolio.fit/mcp'
{
"mcpServers": {
"fit-portfolio-portfoliofit": {
"url": "https://portfolio.fit/mcp"
}
}
} {
"servers": {
"fit-portfolio-portfoliofit": {
"type": "http",
"url": "https://portfolio.fit/mcp"
}
}
} [mcp_servers.fit-portfolio-portfoliofit] url = "https://portfolio.fit/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fit-portfolio-portfoliofit": {
"type": "remote",
"url": "https://portfolio.fit/mcp",
"enabled": true
}
}
} openclaw mcp add fit-portfolio-portfoliofit --url 'https://portfolio.fit/mcp' --transport streamable-http
mcp_servers:
fit-portfolio-portfoliofit:
url: "https://portfolio.fit/mcp" {
"McpServers": {
"fit-portfolio-portfoliofit": {
"Transport": "http",
"Url": "https://portfolio.fit/mcp"
}
}
} assistant mcp add fit-portfolio-portfoliofit -t streamable-http -u 'https://portfolio.fit/mcp'
{
"mcpServers": {
"fit-portfolio-portfoliofit": {
"type": "http",
"url": "https://portfolio.fit/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 2 Sept 26 +1
- Stability: 0.97 → pass security
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.1.3 → 0.1.4 functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
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 20 Sept 2026 · Probed https://portfolio.fit/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=portfolio.fit | CN=WE1,O=Google Trust Services,C=US | 25 Aug 2026 | 23 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f4ef90098facc8890e177cba5d74ddbe |
| SANs: portfolio.fit, *.portfolio.fit | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of portfolio.fit. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fit. | present | 61939 | 8 | Verified |
| portfolio.fit. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://portfolio.fit/mcp | Verified | 200 | |
| http (plaintext) | http://portfolio.fit/mcp | HTTPS enforced | 301 | https://portfolio.fit/mcp |
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 →
calculate_portfolio_constraints Calculate portfolio constraints ~80
Calculate explicit portfolio constraints deterministically from normalized holdings. Use this for arithmetic checks, not for interpreting natural-language mandates.
| Name | Type | Req | Description |
|---|---|---|---|
| base_currency | string | – | – |
| composition_scope | string | – | – |
| constraints | array | yes | – |
| holdings | array | yes | – |
| idempotency_key | string | yes | – |
| source_warnings | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
evaluate_portfolio_alignment Evaluate portfolio alignment ~97
Compare a clean mandate with normalized holdings. Do not send PDF, CSV, spreadsheet, or factsheet files; extract them before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| base_currency | string | – | – |
| composition_scope | string | – | – |
| holdings | array | yes | – |
| idempotency_key | string | yes | – |
| mandate | string | – | – |
| portfolio_name | string | – | – |
| rules | – | – | – |
| source_warnings | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the PortfolioFit MCP server?
PortfolioFit is an MCP server listed in the public MCP registry as fit.portfolio/portfoliofit. Check normalized portfolios against mandates and calculate allocation constraints. This page covers its hosted endpoint (https://portfolio.fit/mcp).
Is the PortfolioFit MCP server safe to use?
PortfolioFit scores 80 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 PortfolioFit MCP server expose?
PortfolioFit exposes 2 tools: evaluate_portfolio_alignment, calculate_portfolio_constraints. Their descriptions and schemas cost roughly 177 tokens of context every time the server is loaded.
Does the PortfolioFit MCP server require authentication?
No. We connected to PortfolioFit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PortfolioFit MCP server still maintained?
PortfolioFit is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.