MSPortfolio — MCP-Native Engineering Portfolio
REMOTE · MSP-PORTFOLIO.MANSIO-DEV.WORKERS.DEV
MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence.
Available components
Last scanned (11 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1291 tokens (~71/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Sept 26 0
- Tool “get_commit_history” rewrote its description, which is the text the model reads security
- 28 Sept 26 +6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Schema quality: 1069 → 1259 ▼ functional
- New tool “get_issue_detail” functional
- New tool “search_projects” functional
- 16 Aug 26 0
- Tool “get_profile” rewrote its description, which is the text the model reads security
- Schema quality: 46 → 66 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- New tool “verify_article” functional
- New tool “verify_package” functional
- New tool “verify_repo” functional
- 15 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://msp-portfolio.mansio-dev.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mansio-dev.workers.dev | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | eb621eb9681143a80eb3ea114581af3f |
| SANs: mansio-dev.workers.dev, *.mansio-dev.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of msp-portfolio.mansio-dev.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://msp-portfolio.mansio-dev.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://msp-portfolio.mansio-dev.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_stack ~42
Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| required_skills | array | yes | Skills the job requires. |
No output schema declared.
No examples provided.
get_antipatterns ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_articles ~21
Get recent Dev.to articles with reading time, tags and links.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_commit_history ~77
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'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_diary ~62
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_engineering_principles ~27
Get engineering principles with real examples and A/B-style counterfactuals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_experiments ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_issue_detail ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The issue ID, e.g. 'KI-109' (case-insensitive). |
No output schema declared.
No examples provided.
get_known_issues ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_profile ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_projects ~38
Get portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | Filter projects by stack tag. |
No output schema declared.
No examples provided.
get_timeline ~15
Get the engineering decision timeline.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_projects ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search terms, e.g. 'RAG' or 'latency Zed'. |
No output schema declared.
No examples provided.
simulate_architecture ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | Project to simulate. |
| scenario | string | yes | Scenario to apply. |
No output schema declared.
No examples provided.
verify_article ~119
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).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Article title fragment or keyword, e.g. "agent memory" or an exact title. |
No output schema declared.
No examples provided.
verify_claim ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The claim to verify, e.g. "built an MCP server with LanceDB hybrid search". |
No output schema declared.
No examples provided.
verify_package ~115
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).
| Name | Type | Req | Description |
|---|---|---|---|
| package | string | yes | npm package name, e.g. "msp-portfolio" (lowercase). |
No output schema declared.
No examples provided.
verify_repo ~205
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).
| Name | Type | Req | Description |
|---|---|---|---|
| readme | boolean | – | Also fetch the repository README (first ~1200 chars) for claim checks against the project's own description. |
| repo | string | yes | Repository name, e.g. "mscodebase-intelligence" (owner defaults to ManSio) or full "owner/name" or a github.com URL. |
No output schema declared.
No examples provided.
How do I install the MSPortfolio — MCP-Native Engineering Portfolio server?
MSPortfolio — MCP-Native Engineering Portfolio is a hosted endpoint at https://msp-portfolio.mansio-dev.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · msp-portfolio.mansio-dev.workers.dev
claude mcp add --transport http mansio-msp-portfolio 'https://msp-portfolio.mansio-dev.workers.dev/mcp'
What is the MSPortfolio — MCP-Native Engineering Portfolio server?
MSPortfolio — MCP-Native Engineering Portfolio is listed in the public MCP registry as io.github.ManSio/msp-portfolio. MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence. This page covers its hosted endpoint (https://msp-portfolio.mansio-dev.workers.dev/mcp).
Is the MSPortfolio — MCP-Native Engineering Portfolio server safe to use?
MSPortfolio — MCP-Native Engineering Portfolio scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MSPortfolio — MCP-Native Engineering Portfolio server expose?
MSPortfolio — MCP-Native Engineering Portfolio exposes 18 tools: get_profile, get_projects, search_projects, get_engineering_principles, get_timeline, and 13 more. Their descriptions and schemas cost roughly 1,291 tokens of context every time the server is loaded.
Does the MSPortfolio — MCP-Native Engineering Portfolio server require authentication?
No. We connected to MSPortfolio — MCP-Native Engineering Portfolio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MSPortfolio — MCP-Native Engineering Portfolio server still maintained?
MSPortfolio — MCP-Native Engineering Portfolio is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.