Skip to content

MSPortfolio — MCP-Native Engineering Portfolio

io.github.ManSio/msp-portfolioManSiostreamable-httpv1.0.4Scanned

MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence.

18 tools: 5 change things and 13 only read.

Tools: 0 delete, 0 irreversible, 5 write, 13 read.
  • Reads private data · 2
  • Reads text others write · 7
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 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 MSPortfolio — MCP-Native Engineering Portfolio can do

The MSPortfolio — MCP-Native Engineering Portfolio is published by the GitHub account ManSio. It has 18 tools. It can create or change data (5 tools: simulate_architecture, verify_claim, verify_repo, verify_article and 1 more), but cannot delete data. 13 tools only read.

2 tools read private data (get_profile and get_commit_history); 7 tools bring in text other people can write (get_articles, get_commit_history, get_known_issues and 4 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.4.

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.

18 tools

Changes things 5Claude Code: ask
  • simulate_architectureSimulate how a project's architecture behaves under a scenario (load spike, node loss, cache cold, LLM saturation).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
    Simulate how a project's architecture behaves under a scenario (load spike, node loss, cache cold, LLM saturation). Returns latency percentiles per load and bottleneck analysis.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • verify_articleVerify an article against the primary source (Dev.to): does the owner have a published article matching the query?Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Verify an article against the primary source (Dev.to): does the owner have a published article matching the query? Fetches the live Dev.to API for the owner's articles and returns the real title/date/reactions/url when found — or an honest 'not found'. Use it to ground claims like 'he wrote about agent memory' in the platform's data instead of the portfolio's own words. Read-only, open world (network fetch).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • verify_claimGround a claim about the owner against the portfolio's data (profile, projects, principles, timeline, antipatterns, experiments, diary, known issues).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
    Ground a claim about the owner against the portfolio's data (profile, projects, principles, timeline, antipatterns, experiments, diary, known issues). Deterministic: returns the evidence records that support the claim (with source paths) and a supported verdict. Use it before asserting a fact about the owner, or to check what an answer was based on.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • verify_packageVerify an npm package against the primary source (registry.npmjs.org): does it exist, latest version, publish date, description, license, maintainers — and is the owner among them?Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Verify an npm package against the primary source (registry.npmjs.org): does it exist, latest version, publish date, description, license, maintainers — and is the owner among them? Use it to ground claims like 'he published an npm package' in the registry's data instead of the portfolio's. Honest 'not found' when the package does not exist. Read-only, open world (network fetch).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • verify_repoVerify a GitHub repository against the primary source: fetches the actual repo metadata (exists, language, description, topics, stars, last push) from the GitHub API and cross-chec…Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Verify a GitHub repository against the primary source: fetches the actual repo metadata (exists, language, description, topics, stars, last push) from the GitHub API and cross-checks it with the portfolio's project record when the repo is one of the owner's projects (language/stack agreement). With readme:true it also returns the actual README text, so claims about what the project does can be checked against the repository's own words. Use it to ground claims like 'the repo is Python' or 'he maintains mscodebase-intelligence' with live data instead of trusting the claim. Read-only, open world (network fetch).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 13Show 13 read-only tools
  • analyze_stackCompare the owner's stack against a job's required skills.No findings

    Why it is in this group

    • The name "analyze_stack" says "analyze": a word for reading.
    Description, as the server wrote it
    Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_antipatternsGet the owner's antipattern museum — real engineering mistakes with why they were bad, how they were fixed, and the lesson.No findings

    Why it is in this group

    • The name "get_antipatterns" says "get": a word for reading.
    Description, as the server wrote it
    Get the owner's antipattern museum — real engineering mistakes with why they were bad, how they were fixed, and the lesson. Read-only, closed world.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_articlesGet recent Dev.to articles with reading time, tags and links.Reads text others writeNo findings

    Why it is in this group

    • The name "get_articles" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Get recent Dev.to articles with reading time, tags and links.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • get_commit_historyGet recent commit history across the owner's public repos.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_commit_history" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_commit_history" says "get" and "commit": it reads repositories.
    • private-dataThe description's first sentence says "get" and "commit": it reads repositories.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Get recent commit history across the owner's public repos. Reads the deployed snapshot and reports its `fetchedAt` and `ageMinutes`, so 'how current is this?' is answered by the payload instead of by trusting this description. Use it to answer 'what has he been building lately' or 'show the hardest bugs he has fixed'.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • get_diaryGet the owner's engineering diary — incidents, root causes, fixes and guards, each tagged with a pattern (NEW vs recurring).No findings

    Why it is in this group

    • The name "get_diary" says "get": a word for reading.
    Description, as the server wrote it
    Get the owner's engineering diary — incidents, root causes, fixes and guards, each tagged with a pattern (NEW vs recurring). Use it to answer 'what broke and how did you fix it' or 'show your hardest debugging session'. Read-only, closed world.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_engineering_principlesGet engineering principles with real examples and A/B-style counterfactuals.No findings

    Why it is in this group

    • The name "get_engineering_principles" says "get": a word for reading.
    Description, as the server wrote it
    Get engineering principles with real examples and A/B-style counterfactuals.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_experimentsGet the owner's engineering experiments — hypothesis, command, raw result and verdict (confirmed/refuted/partial) for each.No findings

    Why it is in this group

    • The name "get_experiments" says "get": a word for reading.
    Description, as the server wrote it
    Get the owner's engineering experiments — hypothesis, command, raw result and verdict (confirmed/refuted/partial) for each. Use it to answer 'what did you measure' or 'show me an experiment you ran'. Includes negative results (approaches that failed). Read-only, closed world.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_issue_detailGet the full detail of a single known issue by its ID (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "get_issue_detail" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_issue_detail" says "get" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "get" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    Get the full detail of a single known issue by its ID (e.g. 'KI-109'). Drills into one open problem: status, temperature, owner, linked source and the raw problem statement. Returns a clear not-found with the available IDs if the ID does not match. Read-only, closed world.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_known_issuesGet the owner's known-issues board — open debt with status, temperature (stable/watching) and deadlines.Reads text others writeNo findings

    Why it is in this group

    • The name "get_known_issues" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_known_issues" says "get" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "get" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    Get the owner's known-issues board — open debt with status, temperature (stable/watching) and deadlines. Use it to answer 'what's still broken' or 'what are you working on'. Read-only, closed world.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_profileGet the owner's professional profile summary, plus nextSteps — concrete ways to continue (contact channels, GitHub, MCP connect).Reads private dataNo findings

    Why it is in this group

    • The name "get_profile" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "get" and "contact": it reads contacts.
    Description, as the server wrote it
    Get the owner's professional profile summary, plus nextSteps — concrete ways to continue (contact channels, GitHub, MCP connect). Use it as the first tool in an interview.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_projectsGet portfolio projects with stack, highlights, and decision logs.No findings

    Why it is in this group

    • The name "get_projects" says "get": a word for reading.
    Description, as the server wrote it
    Get portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_timelineGet the engineering decision timeline.No findings

    Why it is in this group

    • The name "get_timeline" says "get": a word for reading.
    Description, as the server wrote it
    Get the engineering decision timeline.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • search_projectsFree-text search across portfolio projects — name, tagline, description, stack and decision-log rationale.No findings

    Why it is in this group

    • The name "search_projects" says "search": a word for reading.
    Description, as the server wrote it
    Free-text search across portfolio projects — name, tagline, description, stack and decision-log rationale. Returns matched projects with a score and the fields that matched. Use when a fixed stack-tag filter is too narrow (e.g. 'RAG', 'latency', 'Zed'). Read-only, closed world.

    Annotations the server declares

    • readOnlyHint: 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 outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
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 20, 2026, 18:59 UTC, unchanged since Oct 22, 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
5
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 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://msp-portfolio.mansio-dev.workers.dev/mcp: tools/list returned 18 tools to an anonymous client, including simulate_architecture (write), verify_claim (write), verify_repo (write), verify_article (write), verify_package (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http msp-portfolio https://msp-portfolio.mansio-dev.workers.dev/mcp
claude mcp add --transport http msp-portfolio https://msp-portfolio.mansio-dev.workers.dev/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__msp-portfolio__get_profile",
      "mcp__msp-portfolio__get_projects",
      "mcp__msp-portfolio__search_projects",
      "mcp__msp-portfolio__get_engineering_principles",
      "mcp__msp-portfolio__get_timeline",
      "mcp__msp-portfolio__get_articles",
      "mcp__msp-portfolio__get_commit_history",
      "mcp__msp-portfolio__get_antipatterns",
      "mcp__msp-portfolio__analyze_stack",
      "mcp__msp-portfolio__get_experiments",
      "mcp__msp-portfolio__get_diary",
      "mcp__msp-portfolio__get_known_issues",
      "mcp__msp-portfolio__get_issue_detail"
    ],
    "ask": [
      "mcp__msp-portfolio__simulate_architecture",
      "mcp__msp-portfolio__verify_claim",
      "mcp__msp-portfolio__verify_repo",
      "mcp__msp-portfolio__verify_article",
      "mcp__msp-portfolio__verify_package"
    ],
    "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 msp-portfolio. Review it before you use it.

Capability tags behind 8 rules
  • mcp__msp-portfolio__get_profile private-data
  • mcp__msp-portfolio__get_articles untrusted-input
  • mcp__msp-portfolio__get_commit_history private-data, untrusted-input
  • mcp__msp-portfolio__get_known_issues untrusted-input
  • mcp__msp-portfolio__get_issue_detail untrusted-input
  • mcp__msp-portfolio__verify_repo untrusted-input
  • mcp__msp-portfolio__verify_article untrusted-input
  • mcp__msp-portfolio__verify_package untrusted-input

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/io.github.ManSio/msp-portfolio/verify?hash=fd419fe0d3cfe29f7363c9756e99819bb3d122211a603c8e1ca3ed56e1951be1" | jq -e '.changed == false'

Pinned hash fd419fe0d3cf, from Nov 16, 2026, 19:17 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.ManSio/msp-portfolio/changes.xml

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

Badge

Anlyon Radar badge for io.github.ManSio/msp-portfolio
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ManSio/msp-portfolio.svg)](https://radar.anlyon.com/servers/io.github.ManSio/msp-portfolio)

Source: MCP Registry. Synced Oct 21, 2026, 18:17 UTC.

MSPortfolio — MCP-Native Engineering Portfolio: questions and answers

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

Is the MSPortfolio — MCP-Native Engineering Portfolio safe?

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

Can the MSPortfolio — MCP-Native Engineering Portfolio delete data?

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

Can the MSPortfolio — MCP-Native Engineering Portfolio 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 MSPortfolio — MCP-Native Engineering Portfolio have?

18 tools: 5 write, 13 read. simulate_architecture, verify_claim, verify_repo, verify_article, verify_package, get_profile, get_projects, search_projects and 10 more.

Does the MSPortfolio — MCP-Native Engineering Portfolio need sign-in or OAuth?

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

Does the MSPortfolio — MCP-Native Engineering Portfolio send data to outside services?

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

Has the MSPortfolio — MCP-Native Engineering Portfolio changed its tools?

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