# MSPortfolio — MCP-Native Engineering Portfolio (remote · msp-portfolio.mansio-dev.workers.dev)

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

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `msp-portfolio.mansio-dev.workers.dev`: 62/100 (this document), [markdown](https://verifymcp.io/servers/mansio-msp-portfolio/msp-portfolio.md), [page](https://verifymcp.io/servers/mansio-msp-portfolio/msp-portfolio)

## Channel facts

- Endpoint: `https://msp-portfolio.mansio-dev.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1069 tokens (~66/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

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

### Codex

```toml
[mcp_servers.mansio-msp-portfolio]
url = "https://msp-portfolio.mansio-dev.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mansio-msp-portfolio": {
      "type": "remote",
      "url": "https://msp-portfolio.mansio-dev.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mansio-msp-portfolio --url https://msp-portfolio.mansio-dev.workers.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mansio-msp-portfolio:
    url: "https://msp-portfolio.mansio-dev.workers.dev/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-20 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-18 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-16 (score 60, +1)

- [security] Tool “get_profile” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 46 → 66
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] New tool “verify_article”
- [functional] New tool “verify_package”
- [functional] New tool “verify_repo”

### 2026-08-15 (score 59)

First indexed and scored.

## MCP tools (16)

### `get_profile` (~43 tokens)

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_projects` (~38 tokens)

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

Input parameters:

- `filter` (string): Filter projects by stack tag.

### `get_engineering_principles` (~27 tokens)

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

### `get_timeline` (~15 tokens)

Get the engineering decision timeline.

### `get_articles` (~21 tokens)

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

### `get_commit_history` (~45 tokens)

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_antipatterns` (~42 tokens)

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` (~42 tokens)

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

Input parameters:

- `required_skills` (array, required): Skills the job requires.

### `simulate_architecture` (~65 tokens)

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.

Input parameters:

- `project_id` (string, required): Project to simulate.
- `scenario` (string, required): Scenario to apply.

### `get_experiments` (~68 tokens)

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_diary` (~62 tokens)

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_known_issues` (~56 tokens)

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.

### `verify_claim` (~106 tokens)

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.

Input parameters:

- `claim` (string, required): The claim to verify, e.g. "built an MCP server with LanceDB hybrid search".

### `verify_repo` (~205 tokens)

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

Input parameters:

- `readme` (boolean): Also fetch the repository README (first ~1200 chars) for claim checks against the project's own description.
- `repo` (string, required): Repository name, e.g. "mscodebase-intelligence" (owner defaults to ManSio) or full "owner/name" or a github.com URL.

### `verify_article` (~119 tokens)

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

Input parameters:

- `query` (string, required): Article title fragment or keyword, e.g. "agent memory" or an exact title.

### `verify_package` (~115 tokens)

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

Input parameters:

- `package` (string, required): npm package name, e.g. "msp-portfolio" (lowercase).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mansio-msp-portfolio/msp-portfolio#diagnostics

## Score history

- 2026-08-20: 62
- 2026-08-19: 61
- 2026-08-18: 61
- 2026-08-17: 60
- 2026-08-16: 60
- 2026-08-15: 59

## Links

- Remote endpoint: https://msp-portfolio.mansio-dev.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/mansio-msp-portfolio/msp-portfolio.xml
- Changelog JSON feed: https://verifymcp.io/servers/mansio-msp-portfolio/msp-portfolio.json
- HTML version of this page: https://verifymcp.io/servers/mansio-msp-portfolio/msp-portfolio