MSPortfolio — MCP-Native Engineering Portfolio is an MCP server with 18 tools an agent can call, among them analyze_stack, get_antipatterns, get_articles. It answers at https://msp-portfolio.mansio-dev.workers.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 20 October 2026, succeeded.
MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
analyze_stack | Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage. Inputs: required_skills |
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. |
get_articles | Get recent Dev.to articles with reading time, tags and links. |
get_commit_history | Get recent commit history across the owner's public repos (hourly snapshot). Use it to answer 'what has he been building lately' or 'show the hardest bugs he has fixed'. |
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 wo |
get_engineering_principles | Get engineering principles with real examples and A/B-style counterfactuals. |
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 th |
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 no Inputs: id |
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. |
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. |
get_projects | Get portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag. Inputs: filter |
get_timeline | Get the engineering decision timeline. |
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', 'late Inputs: query |
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. Inputs: project_id, scenario |
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 Inputs: query |
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) an Inputs: claim |
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' Inputs: package |
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 o Inputs: repo, readme |
Every block below points at https://msp-portfolio.mansio-dev.workers.dev/mcp. Pick your client and copy.
claude mcp add --transport http msportfolio-mcp-native-engineeri https://msp-portfolio.mansio-dev.workers.dev/mcp
{
"mcpServers": {
"msportfolio-mcp-native-engineeri": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://msp-portfolio.mansio-dev.workers.dev/mcp"]
}
}
}{
"mcpServers": {
"msportfolio-mcp-native-engineeri": {
"url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
}
}
}{
"servers": {
"msportfolio-mcp-native-engineeri": {
"type": "http",
"url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
}
}
}{
"context_servers": {
"msportfolio-mcp-native-engineeri": {
"url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
}
}
}{
"mcpServers": {
"msportfolio-mcp-native-engineeri": {
"serverUrl": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
}
}
}{
"mcpServers": {
"msportfolio-mcp-native-engineeri": {
"url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
}
}
}name: MSPortfolio — MCP-Native Engineering Portfolio
version: 0.0.1
schema: v1
mcpServers:
- name: MSPortfolio — MCP-Native Engineering Portfolio
type: streamable-http
url: https://msp-portfolio.mansio-dev.workers.dev/mcp{
"mcpServers": {
"msportfolio-mcp-native-engineeri": {
"httpUrl": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
}
}
}{
"mcpServers": {
"msportfolio-mcp-native-engineeri": {
"type": "http",
"url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
}
}
}{
"mcpServers": {
"msportfolio-mcp-native-engineeri": {
"url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmsp-portfolio.mansio-dev.workers.dev%2Fmcp&type=streamable_http&id=msportfolio-mcp-native-engineeri&name=MSPortfolio%20%E2%80%94%20MCP-Native%20Engineering%20Portfolio
It answered our last check on 20 October 2026 in 310 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
18, as returned by the server's own tools/list on 12 September 2026: analyze_stack, get_antipatterns, get_articles, get_commit_history, get_diary, get_engineering_principles, get_experiments, get_issue_detail, and 10 more.
It answered our last check on 20 October 2026 in 310 ms. Over 6 checks since 11 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://msp-portfolio.mansio-dev.workers.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.mansio. Endpoint host: msp-portfolio.mansio-dev.workers.dev. ARD identifier: urn:air:io.github.mansio:mcp:msp-portfolio.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.