MSPortfolio — MCP-Native Engineering Portfolio

Name: MSPortfolio — MCP-Native Engineering Portfolio
Author: ManSio

MCP serverMCP

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

by ManSiov1.0.4

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"msportfolio-mcp-native-engineering-portfolio","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability110/110 checks ok

when	check	result	http	latency	detail
2 h ago	mcp initialize	ok	200	157 ms	server msp-portfolio 1.0.0 · protocol 2025-06-18 · 18 tools
9 h ago	mcp initialize	ok	200	353 ms	server msp-portfolio 1.0.0 · protocol 2025-06-18 · 18 tools
15 h ago	mcp initialize	ok	200	237 ms	server msp-portfolio 1.0.0 · protocol 2025-06-18 · 18 tools
22 h ago	mcp initialize	ok	200	181 ms	server msp-portfolio 1.0.0 · protocol 2025-06-18 · 18 tools
28 h ago	mcp initialize	ok	200	246 ms	server msp-portfolio 1.0.0 · protocol 2025-06-18 · 18 tools
34 h ago	mcp initialize	ok	200	97 ms	server msp-portfolio 1.0.0 · protocol 2025-06-18 · 18 tools
2 d ago	mcp initialize	ok	200	221 ms	server msp-portfolio 1.0.0 · protocol 2025-06-18 · 18 tools
2 d ago	mcp initialize	ok	200	232 ms	server msp-portfolio 1.0.0 · protocol 2025-06-18 · 18 tools
2 d ago	mcp initialize	ok	200	270 ms	server msp-portfolio 1.0.0 · protocol 2025-06-18 · 18 tools
3 d ago	mcp initialize	ok	200	165 ms	server msp-portfolio 1.0.0 · protocol 2025-06-18 · 18 tools

Tools observed via MCP handshake

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
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
get_engineering_principles — Get engineering principles with real examples and A/B-style counterfactuals.
get_timeline — Get the engineering decision timeline.
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. Reads the deployed snapshot and reports its `fetchedAt` and `ageMinutes`, so 'how current is this?' i
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.
analyze_stack — Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.
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 bot
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 measu
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 ho
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
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 probl
verify_claim — Ground a claim about the owner against the portfolio's data (profile, projects, principles, timeline, antipatterns, experiments, diary, known issues). Determini
verify_repo — Verify a GitHub repository against the primary source: fetches the actual repo metadata (exists, language, description, topics, stars, last push) from the GitHu
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 a
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 t

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.ManSio/msp-portfolio

first seen 1 mo ago · fetched 31 h agoopen ↗

Field history (5 recent events)

1 mo ago · declared · summary → "MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence."
1 mo ago · declared · description → "MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence."
1 mo ago · declared · publisherName → "ManSio"
1 mo ago · declared · version → "1.0.4"
1 mo ago · declared · protocols → ["mcp"]

MSPortfolio — MCP-Native Engineering Portfolio

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from