# io.github.ManSio/msp-portfolio

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.4
- **Author:** io.github.ManSio
- **License:** Unknown
- **Endpoints:** streamable-http https://msp-portfolio.mansio-dev.workers.dev/mcp
- **Source:** https://msp-portfolio.mansio-dev.workers.dev/mcp
- **Endpoint health:** reachable (last checked 2026-09-26T11:48:17.606Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-26T11:48:17.606Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

18 declared. Observed from a live `tools/list` probe.
- `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.
- `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 
- `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 (hourly snapshot). Use it to answer 'what has he been building lately' or 'show the hardest bugs he ha
- `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 bot
- `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_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_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_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
- `verify_claim` — Ground a claim about the owner against the portfolio's data (profile, projects, principles, timeline, antipatterns, experiments, diary, known issues). Determini
- `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
- `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_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

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"msp-portfolio\": {\n      \"type\": \"http\",\n      \"url\": \"https://msp-portfolio.mansio-dev.workers.dev/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.ManSio%2Fmsp-portfolio
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.ManSio%2Fmsp-portfolio/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.ManSio%2Fmsp-portfolio
- HTML page: https://forgeregistry.com/registry/io.github.ManSio%2Fmsp-portfolio
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.