Skip to content
Agentmart
Submit a tool

MSPortfolio — MCP-Native Engineering Portfolio

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

Connector by ManSio · GitHub account verified by the MCP Registry

IndexedLicense unknownRemote (HTTP)
Write a review

Install

Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/mansio-msp-portfolio

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

  • https://msp-portfolio.mansio-dev.workers.dev/mcp Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
18 read · 0 write · 0 deleteRead-only
Secrets
None asked for
Install scripts
Nothing to install (hosted)
Runs as
Hosted (remote endpoint)

Tools by what they do 18

From the running server's own tool list (tools/list) on Oct 25, 2026.

Read 18 · Look things up without changing anything.

  • analyze_stack
  • get_antipatterns
  • get_articles
  • get_commit_history
  • get_diary
  • get_engineering_principles
  • get_experiments
  • get_issue_detail
  • get_known_issues
  • get_profile
  • get_projects
  • get_timeline
Show 6 more tools
  • search_projects
  • simulate_architecture
  • verify_article
  • verify_claim
  • verify_package
  • verify_repo

Network hosts it talks to 1

  • msp-portfolio.mansio-dev.workers.dev · found in remote endpoint, install command

Tools (18)

As the server listed them on Oct 25, 2026. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • analyze_stackread-only

    Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.

  • get_antipatternsread-only

    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_articlesread-only

    Get recent Dev.to articles with reading time, tags and links.

  • get_commit_historyread-only

    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'.

  • get_diaryread-only

    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_engineering_principlesread-only

    Get engineering principles with real examples and A/B-style counterfactuals.

  • get_experimentsread-only

    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_issue_detailread-only

    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.

  • get_known_issuesread-only

    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_profileread-only

    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_projectsread-only

    Get portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag.

  • get_timelineread-only

    Get the engineering decision timeline.

  • search_projectsread-only

    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.

  • simulate_architectureread-only

    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.

  • verify_articleread-only

    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 (network fetch).

Show 3 more tools
  • verify_claimread-only

    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.

  • verify_packageread-only

    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).

  • verify_reporead-only

    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 checked against the repository's own words. Use it to ground claims like 'the repo is Python' or 'he maintains mscodebase-intelligence' with live data instead of trusting the claim. Read-only, open world…

Signals

Last release
Aug 15, 2026 (2 months ago)

Details

Registry name
io.github.ManSio/msp-portfolio
Version
1.0.4
Auth
Auth not stated
License
License unknown
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
Official MCP Registry
Cite this page

MSPortfolio — MCP-Native Engineering Portfolio. Agent Mart. https://agentmart.dev/connectors/mansio-msp-portfolio (last updated 2026-10-24)