MSPortfolio — MCP-Native Engineering Portfolio
Server Details
MCP server for Mikhail (ManSio)'s engineering portfolio: projects, principles, lab, evidence.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 18 tools
Each tool targets a distinct resource or verification source, with clear boundaries between listing, searching, detailing, simulating, and verifying. Overlaps like get_articles vs verify_article are well differentiated by read-only portfolio data vs live external grounding.
All tool names use consistent snake_case and follow a predictable verb_noun pattern (get_*, verify_*, search_*, analyze_*, simulate_*). The few multi-word nouns like issue_detail and commit_history remain readable and consistent.
18 tools is slightly above the typical 3-15 range, but each tool covers a distinct portfolio facet or verification target. The set is rich but not redundant, making the count reasonable though a bit heavy.
The read-only portfolio surface is broad: profile, projects, stack analysis, diary, issues, experiments, timeline, search, simulation, and multiple verification tools. Minor gaps exist, such as no dedicated single-project detail tool, but agents can work around this via get_projects or search_projects.
Available Tools
18 toolsanalyze_stackARead-onlyInspect
Compare the owner's stack against a job's required skills. Returns per-skill match with evidence and coverage.
Inputs: required_skills (required).
get_antipatternsARead-onlyInspect
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.
Inputs: no named parameters.
get_articlesARead-onlyInspect
Get recent Dev.to articles with reading time, tags and links.
Inputs: no named parameters.
get_commit_historyARead-onlyInspect
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'.
Inputs: no named parameters.
get_diaryARead-onlyInspect
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.
Inputs: no named parameters.
get_engineering_principlesARead-onlyInspect
Get engineering principles with real examples and A/B-style counterfactuals.
Inputs: no named parameters.
get_experimentsARead-onlyInspect
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.
Inputs: no named parameters.
get_issue_detailARead-onlyInspect
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.
Inputs: id (required).
get_known_issuesARead-onlyInspect
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.
Inputs: no named parameters.
get_profileARead-onlyInspect
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.
Inputs: no named parameters.
get_projectsBRead-onlyInspect
Get portfolio projects with stack, highlights, and decision logs. Optional filter by stack tag.
Inputs: filter.
get_timelineBRead-onlyInspect
Get the engineering decision timeline.
Inputs: no named parameters.
search_projectsARead-onlyInspect
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.
Inputs: query (required).
simulate_architectureARead-onlyInspect
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.
Inputs: scenario (required), project_id (required).
verify_articleARead-onlyInspect
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).
Inputs: query (required).
verify_claimARead-onlyInspect
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.
Inputs: claim (required).
verify_packageARead-onlyInspect
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).
Inputs: package (required).
verify_repoARead-onlyInspect
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).
Inputs: repo (required), readme.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
An MCP server for deep research or task groups
Personal MCP server for humans who create. Proof of authorship, license control.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceA portfolio MCP server demonstrating four tools (web search, database query, file reading, directory listing) with read-only SQL, filesystem sandbox, and both stdio and HTTP transports.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for exploring a software developer's portfolio: lists projects, semantically searches code, explains architecture, summarizes READMEs, and answers questions through a natural-language agent, with a built-in web playground.MIT
- MIT
- FlicenseNot gradedqualityDmaintenanceA simple demonstration MCP server that provides an echo tool and resource for learning how to build MCP servers. Serves as a starting point and template for creating custom MCP server implementations.1-
Glama MCP Gateway
Add one secure layer between your agents and this server.