MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence.
Abgeleitet aus den Transporten, die dieser Eintrag deklariert (streamable-http). Ein Client, der hier nicht steht, ist damit nicht ausgeschlossen — Forge kann ihn nur nicht bestätigen.
Die Verifizierung bestätigt die Identität des Publishers (die Inhaberschaft am Repo), nicht die Sicherheit des Codes. Der Sicherheits-Scan deckt bekannte CVEs und verdächtige Installationsskripte ab.
Aus einem echten MCP-Handshake initialize → tools/list gegen den deklarierten Endpunkt gelesen. Es wurde nie ein Tool aufgerufen — tools/list ist der lesende Introspektionsaufruf, den das Protokoll dafür vorsieht. Es spiegelt wider, was der Server in diesem Moment angeboten hat; ein gehosteter Endpunkt ist an keine Version gebunden und kann sich ohne Ankündigung ändern.
https://msp-portfolio.mansio-dev.workers.dev/mcp18 Tools · 1169 msget_profileGet 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 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.
Für dieses Tool wurde kein Eingabeschema veröffentlicht.
get_projectsGet portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag.Get portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag.
| Parameter | Typ | Beschreibung |
|---|---|---|
| filter | string | Filter projects by stack tag. |
search_projectsFree-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.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.
| Parameter | Typ | Beschreibung |
|---|---|---|
| query* | string | Search terms, e.g. 'RAG' or 'latency Zed'. |
get_engineering_principlesGet engineering principles with real examples and A/B-style counterfactuals.Get engineering principles with real examples and A/B-style counterfactuals.
Für dieses Tool wurde kein Eingabeschema veröffentlicht.
get_timelineGet the engineering decision timeline.Get the engineering decision timeline.
Für dieses Tool wurde kein Eingabeschema veröffentlicht.
get_articlesGet recent Dev.to articles with reading time, tags and links.Get recent Dev.to articles with reading time, tags and links.
Für dieses Tool wurde kein Eingabeschema veröffentlicht.
get_commit_historyGet 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 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'.
Für dieses Tool wurde kein Eingabeschema veröffentlicht.
get_antipatternsGet 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 the owner's antipattern museum — real engineering mistakes with why they were bad, how they were fixed, and the lesson. Read-only, closed world.
Für dieses Tool wurde kein Eingabeschema veröffentlicht.
analyze_stackCompare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.
| Parameter | Typ | Beschreibung |
|---|---|---|
| required_skills* | array | Skills the job requires. |
simulate_architectureSimulate 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.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.
| Parameter | Typ | Beschreibung |
|---|---|---|
| project_id* | string | Project to simulate. |
| scenario* | string | Scenario to apply. |
get_experimentsGet 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 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.
Für dieses Tool wurde kein Eingabeschema veröffentlicht.
get_diaryGet 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 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.
Für dieses Tool wurde kein Eingabeschema veröffentlicht.
get_known_issuesGet 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.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.
Für dieses Tool wurde kein Eingabeschema veröffentlicht.
get_issue_detailGet 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.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.
| Parameter | Typ | Beschreibung |
|---|---|---|
| id* | string | The issue ID, e.g. 'KI-109' (case-insensitive). |
verify_claimGround 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…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…
| Parameter | Typ | Beschreibung |
|---|---|---|
| claim* | string | The claim to verify, e.g. "built an MCP server with LanceDB hybrid search". |
verify_repoVerify 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…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…
| Parameter | Typ | Beschreibung |
|---|---|---|
| repo* | string | Repository name, e.g. "mscodebase-intelligence" (owner defaults to ManSio) or full "owner/name" or a github.com URL. |
| readme | boolean | Also fetch the repository README (first ~1200 chars) for claim checks against the project's own description. |
verify_articleVerify 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 a…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 a…
| Parameter | Typ | Beschreibung |
|---|---|---|
| query* | string | Article title fragment or keyword, e.g. "agent memory" or an exact title. |
verify_packageVerify 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 '…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 '…
| Parameter | Typ | Beschreibung |
|---|---|---|
| package* | string | npm package name, e.g. "msp-portfolio" (lowercase). |
18 von 18 Tools haben eine Beschreibung veröffentlicht.
Tool-Namen und -Beschreibungen stammen vom Publisher und werden wortgetreu als inerter Text angezeigt. Es sind die Zeichenketten, die ein MCP-Client an ein Modell übergibt, deshalb prüft Forge sie auf Prompt-Injection-Muster — jeder Befund erscheint oben beim Sicherheits-Scan. „Privilegiert“ ist ein Schlagwort-Treffer im Tool-Namen, keine Prüfung dessen, was das Tool tut: ein harmlos klingender Name kann trotzdem alles tun.
MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence.
Verlinkte Namen öffnen den Forge-Index aller Einträge, bei denen dieses Tool beobachtet wurde. Alle indexierten Tools durchsuchen.
Dieser Eintrag veröffentlicht kein npm-Paket, daher hat Forge keinen Abhängigkeitsbaum dafür. Das ist eine Lücke in der Abdeckung — keine Aussage, dass er keine Abhängigkeiten hat.