MSPortfolio — MCP-Native Engineering Portfolio
MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence.
Connect Remote server
claude mcp add --transport http msp-portfolio https://msp-portfolio.mansio-dev.workers.dev/mcp
{
"mcpServers": {
"msp-portfolio": {
"url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
}
}
}
{
"servers": {
"msp-portfolio": {
"type": "http",
"url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://msp-portfolio.mansio-dev.workers.dev/mcp
Tools 18 found in our last check
get_profileGet 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_projectsGet portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag.
search_projectsFree-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.
get_engineering_principlesGet engineering principles with real examples and A/B-style counterfactuals.
get_timelineGet the engineering decision timeline.
get_articlesGet recent Dev.to articles with reading time, tags and links.
get_commit_historyGet 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'…
get_antipatternsGet the owner's antipattern museum — real engineering mistakes with why they were bad, how they were fixed, and the lesson. Read-only, closed world.
analyze_stackCompare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.
simulate_architectureSimulate 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.
get_experimentsGet 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.
get_diaryGet 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.
get_known_issuesGet 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_issue_detailGet 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.
verify_claimGround 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 as…
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-checks it with the portfolio's project record when the repo is one of the owner's projects (language/st…
verify_articleVerify 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 li…
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? Use it to ground claims like 'he published an npm package' in the registry's data instead of the p…
Details
| Endpoint | https://msp-portfolio.mansio-dev.workers.dev/mcp (Streamable HTTP) |
| First published | 15 Aug 2026 |
| Last updated | 15 Aug 2026 |
| Registry name | io.github.ManSio/msp-portfolio |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
