MSPortfolio — MCP-Native Engineering Portfolio MCP server

• analyze_stackFree

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

• get_antipatternsFree

  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_articlesFree

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

• get_commit_historyFree

  Get recent commit history across the owner's public repos (hourly snapshot). Use it to answer 'what has he been building lately' or 'show the hardest bugs he has fixed'.

• get_diaryFree

  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_principlesFree

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

• get_experimentsFree

  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_detailFree

  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_issuesFree

  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_profileFree

  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_projectsFree

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

• get_timelineFree

  Get the engineering decision timeline.

• search_projectsFree

  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_architectureFree

  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_articleFree

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

• verify_claimFree

  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_packageFree

  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_repoFree

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

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1468ms20/20
• Tool poisoning18 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenanceno repository listed3/15
• Maintainer identityno repository or website to verify2/10

MSPortfolio — MCP-Native Engineering Portfolio: common questions

Is MSPortfolio — MCP-Native Engineering Portfolio MCP server safe?

With care: it is graded C, so read the findings first (67/100). Read the MSPortfolio — MCP-Native Engineering Portfolio safety report

How do I install MSPortfolio — MCP-Native Engineering Portfolio?

It runs remotely at msp-portfolio.mansio-dev.workers.dev. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does MSPortfolio — MCP-Native Engineering Portfolio need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is MSPortfolio — MCP-Native Engineering Portfolio maintained?

The latest release is v1.0.4.

Is MSPortfolio — MCP-Native Engineering Portfolio up?

100% of our last 20 checks got an answer. We check remote servers about four times a day.