MSPortfolio — MCP-Native Engineering Portfolio

io.github.ManSioPublished by GitHub account ManSiov1.0.4Updated Oct 24, 2026

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

The publisher's own server: PortfolioFit

VerifiedStreamable HTTPWeb executableKnowledge & MemoryData & Analytics

Overview

AI-generated overview

Lets an assistant query and verify one engineer's portfolio data, including projects, principles, experiments and known issues.

What you can do
Provides read-only tools over one engineer's portfolio: profile, projects with decision logs, engineering principles, timeline, articles, commit history, antipatterns, experiments, diary entries and a known-issues board. Additional tools compare a stack against job skills, simulate architecture behavior under scenarios such as load spikes, and verify claims, repositories, articles and npm packages against external sources.
When to use it
Use it when you want answers about this engineer grounded in verifiable data, such as interview preparation, project review, or checking claims about their projects, articles and packages.
Requirements
Remote HTTP endpoint; no packages, environment variables or authentication needed. Some verification tools call external APIs such as GitHub, Dev.to and the npm registry, so network access is required.
Before you install
Most tools are read-only, but verify_repo, verify_article and verify_package send queries to GitHub, Dev.to and the npm registry, which may reveal what you are looking up. Data comes from a deployed snapshot and may not be current.

Installation

In SourceWeft

  1. Open MSPortfolio — MCP-Native Engineering Portfolio in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ManSio%2Fmsp-portfolio/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "msportfolio-native-engineering-portfolio": {
      "type": "http",
      "url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
    }
  }
}

Tools

18

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.

Takes no parameters.

get_projects

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

Parametersfilter

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.

Parametersqueryrequired

get_engineering_principles

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

Takes no parameters.

get_timeline

Get the engineering decision timeline.

Takes no parameters.

get_articles

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

Takes no parameters.

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

Takes no parameters.

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.

Takes no parameters.

analyze_stack

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

Parametersrequired_skillsrequired

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.

Parametersscenariorequiredproject_idrequired

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.

Takes no parameters.

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.

Takes no parameters.

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.

Takes no parameters.

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.

Parametersidrequired

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.

Parametersclaimrequired

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

Parametersreporequiredreadme

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

Parametersqueryrequired

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

Parameterspackagerequired

Version history

1
  1. v1.0.4LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Portfolio integrations

PortfolioFit

fit.portfolioOfficial publisher

PortfolioFit is a remote MCP server that lets an assistant check normalized portfolios against mandates and compute allocation constraints and statistics.

Streamable HTTPWeb executable
Finance10 toolsOct 24, 2026

Cameron Rye Portfolio MCP Server

dev.ryeOfficial publisher

Remote MCP endpoint exposing Cameron Rye's blog, portfolio projects, bio, reading list and live site stats, plus contact and newsletter tools.

Streamable HTTPWeb executable
Knowledge & Memory12 toolsOct 24, 2026

Shlok Bam's portfolio

Published by GitHub account shlokbam

Shlok Bam's portfolio's hosted MCP server; no sign-in required; Streamable HTTP; 10 tools.

Streamable HTTPWeb executable
Finance10 toolsNov 3, 2026

Harshith Nayaka L portfolio docs

Published by GitHub account HarshithNayakaL

Read-only MCP server exposing the developer documentation for a portfolio site's JSON API, MCP, A2A and NLWeb endpoints.

Streamable HTTPWeb executable
Knowledge & Memory3 toolsOct 30, 2026

Harshith Nayaka L portfolio

Published by GitHub account HarshithNayakaL

Read-only MCP access to Harshith Nayaka L's portfolio site, letting an assistant look up his profile, projects, case studies, FAQ and agent skills.

Streamable HTTPWeb executable
Web Search & Scraping6 toolsOct 30, 2026