Connect-MCP

MSPortfolio — MCP-Native Engineering Portfolio

io.github.ManSio/msp-portfolio · v1.0.4

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

MCPremoteno credentialsDeveloper tools

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 18 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

A 92/100

What it does: 18 tools · 18 read, 0 write · Developer tools

Test call get_profile: worked (1,040 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +2
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +20
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

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

Tools

18 tools listed at last check
  • 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.
  • 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.
  • 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?' 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
  • 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 bottleneck analysis.
  • 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.
  • 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.
  • 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_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.
  • 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
  • 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
  • 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 ag
  • 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 'n

Badge

Connect-MCP badge for io.github.ManSio/msp-portfolio

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.ManSio/msp-portfolio.svg)](https://clawy.uk/mcp/s/io.github.ManSio/msp-portfolio)