Skip to content

Portfolio Optimizer Pro MCP server

com.portfoliooptimizerpro/portfolio-checkupportfoliooptimizerpro.comstreamable-httpv1.0.3Scanned

Free A–F portfolio grade with reasons, fund fees and overlap. Educational, not advice.

4 tools: 3 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 3 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Portfolio Optimizer Pro MCP server can do

The Portfolio Optimizer Pro MCP server is published by portfoliooptimizerpro.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (3 tools: grade_portfolio, fund_fee_cost and check_overlap), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 3Claude Code: ask
  • check_overlapChecks a list of holdings for known index overlap and related fund mandates, using issuer reference records (asset class, region, structure).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Checks a list of holdings for known index overlap and related fund mandates, using issuer reference records (asset class, region, structure). Findings are worded exactly as the Portfolio Optimizer Pro grade states them. Overlap here is category-based (similar stated mandates); it is not a measured percentage of shared underlying holdings, and the result says so.

    Annotations the server declares

    • title: Check fund overlap
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • fund_fee_costComputes the weighted expense ratio of a list of holdings from dated issuer fee records, and the fee cost over 10 and 30 years on a flat $100,000 balance (before growth), using the…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Computes the weighted expense ratio of a list of holdings from dated issuer fee records, and the fee cost over 10 and 30 years on a flat $100,000 balance (before growth), using the same formula as the Portfolio Optimizer Pro expense ratio calculator. Single companies count as 0% fund fee. If any fund fee is not verified the weighted fee is null and the ticker is listed, rather than estimated.

    Annotations the server declares

    • title: Fund fee cost
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • grade_portfolioRuns the free Portfolio Optimizer Pro checkup on a list of holdings and weights.1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "grade_portfolio" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Runs the free Portfolio Optimizer Pro checkup on a list of holdings and weights. Returns the A+ to F structural grade, the 0-100 score, any structural ceiling (cap) applied, each factor's sub-score with its measured fact, the top findings that held the grade down, the price-history dates used, a disclaimer and full_breakdown_url, a link that opens the same graded checkup on the website. Grades describe diversification, cost and past risk; they are educational, not advice or a forecast. Unknown tickers are listed in unknown_tickers, never guessed.

    Annotations the server declares

    • title: Grade a portfolio
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • explain_gradingReturns how the Portfolio Optimizer Pro grade works: the four factors and how each is scored, how they combine, every structural ceiling (cap) with its threshold, the A-range crite…No findings

    Why it is in this group

    • The name "explain_grading" says "explain": a word for reading.
    Description, as the server wrote it
    Returns how the Portfolio Optimizer Pro grade works: the four factors and how each is scored, how they combine, every structural ceiling (cap) with its threshold, the A-range criteria, the letter bands, the risk reference bands, the data source, limitations and pricing. Takes no input.

    Annotations the server declares

    • title: Explain the grading
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:18 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://portfoliooptimizerpro.com/mcp: tools/list returned 4 tools to an anonymous client, including grade_portfolio (write), fund_fee_cost (write), check_overlap (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "grade_portfolio" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "run": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http portfolio-checkup https://portfoliooptimizerpro.com/mcp
claude mcp add --transport http portfolio-checkup https://portfoliooptimizerpro.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__portfolio-checkup__explain_grading"
    ],
    "ask": [
      "mcp__portfolio-checkup__grade_portfolio",
      "mcp__portfolio-checkup__fund_fee_cost",
      "mcp__portfolio-checkup__check_overlap"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as portfolio-checkup. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.portfoliooptimizerpro/portfolio-checkup/verify?hash=a53b5d55f4bf1eebfb71e5c507a157b5ee2f60ce64e2e3748ce810e9c68bd22f" | jq -e '.changed == false'

Pinned hash a53b5d55f4bf, from Nov 14, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.portfoliooptimizerpro/portfolio-checkup/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.portfoliooptimizerpro/portfolio-checkup
[![Anlyon Radar](https://radar.anlyon.com/badge/com.portfoliooptimizerpro/portfolio-checkup.svg)](https://radar.anlyon.com/servers/com.portfoliooptimizerpro/portfolio-checkup)

Source: MCP Registry. Synced Nov 14, 2026, 16:17 UTC.

Portfolio Optimizer Pro MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Portfolio Optimizer Pro MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Portfolio Optimizer Pro MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Portfolio Optimizer Pro MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Portfolio Optimizer Pro MCP server have?

4 tools: 3 write, 1 read. grade_portfolio, fund_fee_cost, check_overlap and explain_grading.

Does the Portfolio Optimizer Pro MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Portfolio Optimizer Pro MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Portfolio Optimizer Pro MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.