MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence.
Déduit des transports déclarés par cette annonce (streamable-http). Un client absent de cette liste n’est pas écarté pour autant — c’est simplement quelque chose que Forge ne peut pas confirmer.
La vérification confirme l’identité de l’éditeur (la propriété du dépôt), pas la sûreté du code. L’analyse de sécurité couvre les CVE connues et les scripts d’installation suspects.
Lu depuis un véritable échange MCP initialize → tools/list contre l’endpoint déclaré. Aucun outil n’a été invoqué — tools/list est l’appel d’introspection en lecture seule que le protocole prévoit pour cela. Cela reflète ce que le serveur annonçait à cet instant ; un endpoint hébergé n’est figé sur aucune version et peut changer sans préavis.
https://msp-portfolio.mansio-dev.workers.dev/mcp18 outils · 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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
| Paramètre | Type | Description |
|---|---|---|
| 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.
| Paramètre | Type | Description |
|---|---|---|
| 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.
Aucun schéma d’entrée n’a été publié pour cet outil.
get_timelineGet the engineering decision timeline.Get the engineering decision timeline.
Aucun schéma d’entrée n’a été publié pour cet outil.
get_articlesGet recent Dev.to articles with reading time, tags and links.Get recent Dev.to articles with reading time, tags and links.
Aucun schéma d’entrée n’a été publié pour cet outil.
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'.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
| Paramètre | Type | Description |
|---|---|---|
| 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.
| Paramètre | Type | Description |
|---|---|---|
| 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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
Aucun schéma d’entrée n’a été publié pour cet outil.
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.
| Paramètre | Type | Description |
|---|---|---|
| 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…
| Paramètre | Type | Description |
|---|---|---|
| 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…
| Paramètre | Type | Description |
|---|---|---|
| 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…
| Paramètre | Type | Description |
|---|---|---|
| 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 '…
| Paramètre | Type | Description |
|---|---|---|
| package* | string | npm package name, e.g. "msp-portfolio" (lowercase). |
18 outils sur 18 ont publié une description.
Les noms et descriptions d’outils sont écrits par l’éditeur et affichés tels quels, comme du texte inerte. Ce sont les chaînes qu’un client MCP transmet à un modèle, alors Forge y recherche des motifs d’injection de prompt — tout constat apparaît avec l’analyse de sécurité ci-dessus. « Privilégié » est une correspondance de mot-clé sur le nom de l’outil, pas un audit de ce qu’il fait : un nom anodin peut tout de même tout faire.
MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence.
Les noms cliquables ouvrent l’index Forge de toutes les entrées observées exposant cet outil. Parcourir tous les outils indexés.
Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.