# Mansio Msp Portfolio MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.mansio%2Fmsp-portfolio
Registry id: `mcp-registry/io.github.mansio/msp-portfolio`
Status: unknown (checked 2026-10-26T19:06:09.524Z)

## Measurements (30 days)

- Uptime: 98.42%
- Checks: 633
- Outages (90 days): 5

## Install

```json
{
  "mcpServers": {
    "mansio-msp-portfolio-mcp-server": {
      "type": "http",
      "url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http mansio-msp-portfolio-mcp-server https://msp-portfolio.mansio-dev.workers.dev/mcp
```

## Tools (18)

- `analyze_stack`: Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.
- `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.
- `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?' i
- `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 ho
- `get_engineering_principles`: Get engineering principles with real examples and A/B-style counterfactuals.
- `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 measu
- `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 probl
- `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
- `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
- `get_projects`: Get portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag.
- `get_timeline`: Get the engineering decision timeline.
- `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 
- `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 bot
- `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 a
- `verify_claim`: Ground a claim about the owner against the portfolio's data (profile, projects, principles, timeline, antipatterns, experiments, diary, known issues). Determini
- `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 t
- `verify_repo`: Verify a GitHub repository against the primary source: fetches the actual repo metadata (exists, language, description, topics, stars, last push) from the GitHu

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.