MSPortfolio — MCP-Native Engineering Portfolio MCP Server

by mansio Your server? Claim it

answering

MSPortfolio — MCP-Native Engineering Portfolio is answering right now. Last checked 7 min ago. It exposes 18 tools.

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

Uptime history 78 days of history · worst day 92%

78 days agonow

100.0%

Uptime 24h

59 of 59 checks

Tools

read from the server

334 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 September 2026. No other catalogue keeps this.

1 Oct a tool description was rewritten get_commit_history

1 Sep 2 tools appeared get_issue_detail, search_projects

Nothing serious here today

Today is the operative word: we check MSPortfolio — MCP-Native Engineering Portfolio every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add msp-portfolio --transport http https://msp-portfolio.mansio-dev.workers.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://msp-portfolio.mansio-dev.workers.dev/mcp

~/.codex/config.toml

[mcp_servers.msp-portfolio]
url = "https://msp-portfolio.mansio-dev.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "msp-portfolio": {
      "url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "msp-portfolio": {
      "type": "http",
      "url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
    }
  }
}

Available tools 18

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

verify

verify_article

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

verify_claim

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.

verify_package

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

verify_repo

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

projects

get_projects

Get portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag.

search_projects

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.

analyze

analyze_stack

Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.

antipatterns

get_antipatterns

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.

articles

get_articles

Get recent Dev.to articles with reading time, tags and links.

commit

get_commit_history

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

diary

get_diary

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.

engineering

get_engineering_principles

Get engineering principles with real examples and A/B-style counterfactuals.

experiments

get_experiments

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.

issue

get_issue_detail

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.

known

get_known_issues

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.

profile

get_profile

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.

simulate

simulate_architecture

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.

timeline

get_timeline

Get the engineering decision timeline.

Endpoints

URL	Transport	State	Latency	Checked
https://msp-portfolio.mansio-dev.workers.dev/mcp	streamable-http	answering	446 ms	7 min ago

Alternatives to MSPortfolio — MCP-Native Engineering Portfolio

same job, measured the same way

Allstacks Analytics MCP Server

by allstacks

Provides 208+ tools for AI-native engineering intelligence via Allstacks API.

200 installs/wk local only

Nuxt I18n MCP

by fabkho

MCP server for managing i18n translations in Nuxt projects.

82 installs/wk local only

Neon

by neon

Official Neon MCP server for managing Neon projects and Lakebase Postgres databases.

answering

Betterprompt MCP

by aungmyokyaw

MCP server for AI-enhanced prompt engineering and request conversion.

58 installs/wk local only

Project Gumball

by gumballtools

One MCP server exposing every tool in the Gumball portfolio.

25 tools answering

Assay MCP Server

by rul1an

Policy-enforcing MCP proxy with portable evidence output.

local only

Roamer MCP

by mathismeadows

Hosted MCP server and Agent Skills for specs, engineering threads, and project memory.

answering

Office Oxide MCP

by aimino-tech

Rust-native MCP server for Office document processing

93 installs/wk local only

MSPortfolio — MCP-Native Engineering Portfolio — questions

Answers built from our own checks of this server.

What can MSPortfolio — MCP-Native Engineering Portfolio do?

It exposes 18 tools, read directly from the server on our last check. Among them: analyze_stack, get_antipatterns, get_articles, get_commit_history, get_diary, get_engineering_principles and 12 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is MSPortfolio — MCP-Native Engineering Portfolio mostly used for?

Its tools cluster around verify and projects. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is MSPortfolio — MCP-Native Engineering Portfolio working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 59 of 59 checks got a reply (100.0%), average response time 334 ms. The bar chart above shows every period we have measured.

How do I connect MSPortfolio — MCP-Native Engineering Portfolio?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does MSPortfolio — MCP-Native Engineering Portfolio need an API key?

No. MSPortfolio — MCP-Native Engineering Portfolio completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 18 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is MSPortfolio — MCP-Native Engineering Portfolio?

It answers our handshake in 334 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.