MSPortfolio — MCP-Native Engineering Portfolio
MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence.
| Endpoint | https://msp-portfolio.mansio-dev.workers.dev/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.4 |
| Now | 18 tools · grade C (78) · pin ts_65d808257abc7944a7ff44c3609968ed · protocol 2025-06-18 |
| First / last listed | 2026-10-27 04:24 UTC / 2026-10-27 04:24 UTC |
| Grade over time | 2026-10-27: C (78), 18 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: get_profile get_projects search_projects get_engineering_principles get_timeline get_articles get_commit_history get_antipatterns analyze_stack simulate_architecture get_experiments get_diary get_known_issues get_issue_detail verify_claim verify_repo verify_article verify_package
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. params: none |
get_projects | Get portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag. params: filter |
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. params: query* |
get_engineering_principles | Get engineering principles with real examples and A/B-style counterfactuals. params: none |
get_timeline | Get the engineering decision timeline. params: none |
get_articles | Get recent Dev.to articles with reading time, tags and links. params: none |
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'. params: none |
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. params: none |
analyze_stack | Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage. params: required_skills* |
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. params: project_id*, scenario* |
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. params: none |
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. params: none |
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. params: none |
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. params: id* |
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. params: claim* |
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 che params: repo*, readme |
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 (netw params: query* |
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). params: package* |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.