MSPortfolio — MCP-Native Engineering Portfolio

io.github.ManSio由 GitHub 帳號 ManSio 發布v1.0.4更新於 Oct 24, 2026

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

發布方自己的服務：PortfolioFit

已驗證Streamable HTTP可網頁執行知識與記憶資料與分析

服務詳細資訊

識別碼: io.github.ManSio/msp-portfolio
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 ManSio。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.ManSio%2Fmsp-portfolio.svg)](https://sourceweft.com/mcp/io.github.ManSio%2Fmsp-portfolio?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

讓助理查詢並核對這位工程師的作品集資料，包括專案、原則、實驗與已知問題。

可以做什麼: 提供一組唯讀工具，用來查詢這位工程師的個人作品集：個人簡介、專案與決策紀錄、工程原則、時間軸、文章、提交歷史、反模式、實驗、日誌與已知問題看板。另有 analyze_stack 比對技能需求、simulate_architecture 模擬架構在負載等情境下的表現，以及 verify_claim、verify_repo、verify_article、verify_package 等工具，用外部來源核對相關說法。
適用情境: 當您想以可查證的資料回答關於這位工程師的問題時使用，例如面試準備、專案審查，或核對其專案、文章與套件等說法。
執行需求: 遠端 HTTP 端點，無需安裝套件、環境變數或驗證。部分核對工具會連線至 GitHub、Dev.to 與 npm registry 等外部 API，需要網路存取。

安裝前請注意

多數工具為唯讀，但 verify_repo、verify_article 與 verify_package 會向 GitHub、Dev.to 及 npm registry 發出查詢，可能揭露您所查詢的內容。資料為部署時的快照，可能不是最新。

安裝

在 SourceWeft 中

開啟儀表板中的 MSPortfolio — MCP-Native Engineering Portfolio，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.ManSio%2Fmsp-portfolio/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "msportfolio-native-engineering-portfolio": {
      "type": "http",
      "url": "https://msp-portfolio.mansio-dev.workers.dev/mcp"
    }
  }
}

工具

get_profile

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

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

輸入參數filter

search_projects

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.

輸入參數query必填

get_engineering_principles

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

無需輸入參數。

get_timeline

Get the engineering decision timeline.

無需輸入參數。

get_articles

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

無需輸入參數。

get_commit_history

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

無需輸入參數。

get_antipatterns

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

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

輸入參數required_skills必填

simulate_architecture

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.

輸入參數scenario必填project_id必填

get_experiments

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

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

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.

無需輸入參數。

get_issue_detail

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.

輸入參數id必填

verify_claim

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.

輸入參數claim必填

verify_repo

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

輸入參數repo必填readme

verify_article

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

輸入參數query必填

verify_package

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

輸入參數package必填