Repository 指南 · 架構 · v2
modelcontextprotocol / python-sdk · 架構
這是一個 Python repository,共分析 1726 個檔案,大多位於 i18n、examples、tests 和 docs_src 下,函式庫程式碼則位於 src 下。列出的靜態路徑從一個 conformance client 開始,大多停在外部或未解析的標準函式庫呼叫。大部分關係仍未解析。分析器找到的 degree 最高的模組都是測試 harness。
- 原始 repository
- modelcontextprotocol/python-sdk
- 授權
- MIT · 開源授權
- 分析的版本 · 最後驗證
- 77001c96f9507be0f4d009b83210a384a5e08bda ·
本頁中文由負責的 AI 編輯依英文正式版本 v2 翻譯;程式碼名稱、路徑、行號與數字都經確定性檢查,與英文版一致。陳述與依據表保留英文原文,因為那是獨立驗證者核對過的紀錄。看英文原文
modelcontextprotocol/python-sdk 架構:它是怎麼組織的
本頁用語說明
- Entrypoint record(進入點記錄)
- 分析器標記為「程式可能從這裡開始執行」的檔案。附有 __main__ guard 摘錄時,表示檔案裡有 if __name__ == "__main__": 區塊,摘錄顯示它呼叫了什麼;沒有摘錄時,只是依檔名判斷。
- Bounded static execution path(有界靜態執行路徑)
- 不執行程式、直接從原始碼重建出的呼叫鏈,走到固定步數就停。它說明在紙面上能追到多遠,不代表實際執行時會發生什麼。
- Unresolved boundary(未解析邊界)
- 靜態路徑停下的地方:下一個呼叫進入外部函式庫,或不執行就無法確定。這是本次分析的邊界,不是 repository 的缺陷。
- Static relations(靜態關係)
- 在原始碼中找到的呼叫與 import。「external or unresolved」表示指向分析範圍以外。
- Module role(模組角色)
- 分析器依呼叫進出次數推論的檔案標籤(例如 core、entry/orchestration、leaf)。它描述的是在呼叫圖中的位置,不是作者的設計意圖。
- Test-like files(類測試檔案)
- 名稱或位置看起來像測試的檔案。本次分析只計數,不執行。
- Observed · inferred · author-claimed · unresolved
- 每句話的依據:直接讀自分析的檔案;由分析器從檔案推論;repository 作者自述(metadata、README);或本次分析無法確定。
- Verified(已驗證)
- 本頁有兩種用法。在分析器的記錄裡(「verified provenance」「verified entrypoint」),它表示這筆記錄是直接從分析的檔案讀到的,也就是本指南所說的 observed;以進入點來說,就是檔案裡確實有 __main__ guard 的文字。分析器在 2026-10-04 修正後,只有 cli.py、main.py 這類像進入點的檔名、沒有 guard 的檔案,會記為 inferred(推測);在那之前分析的指南仍把這類檔案標成 verified,它依然只是對檔案用途的推測。它不代表程式被執行或測試過。「最後驗證」是這份指南最後一次通過本實驗室檢查的日期,檢查對象是所標示版本的分析記錄,不是對 repository 本身的審查。
整體形貌一覽
分析器將四個頂層目錄標記為可能的子系統:docs、docs_src、src 和 tests。在 1726 個分析過的檔案中,大多數位於 src 之外。有四個目錄各自都比 src(140)大:i18n(664)、examples(298)、tests(285)和 docs_src(218)。較小的有 docs(58)、.github(27)和 scripts(12)。平台 metadata 將 Python 列為主要語言,topics 圍繞 MCP client 與 server。描述將這個專案呈現為 Model Context Protocol server 與 client 的 Python SDK。
src在src/mcp/cli/__init__.py、src/mcp/client/__main__.py和src/mcp/server/__main__.py中有__main__守衛。src/mcp-types有自己的pyproject.toml。- 檔名啟發式規則另外加入
src/mcp/cli/cli.py、src/mcp/server/lowlevel/server.py和src/mcp/server/mcpserver/server.py。這暗示有分開的低階與高階 server 模組。 examples/stories存放成組的 client 與 server 腳本。對於tools、prompts和oauth等主題,每一組都有client.py、server.py和server_lowlevel.py。
進入點與控制流程
重建結果回報 178 個進入點、5460 個已解析的呼叫關係和 658 條有界路徑。分析器將 .github/actions/conformance/client.py 指為主要的起點。它的其中一項教學陳述則改指 src/mcp/cli/cli.py,而哪一個才是主要的尚未確定。
conformance client 的 __main__ 守衛呼叫 main()。分析資料中的十條路徑全都從這裡開始,沒有截斷,也沒有循環:
- 三條結束於模組層級的呼叫(
logging.basicConfig、logging.getLogger、os.environ.get); - 七條經過
main,其中六條結束於sys.exit、print和logger.debug等外部呼叫; - 一條,即同一檔案中的
main→client_mode,以 leaf 結束。
列出的路徑沒有一條到達 src 下的模組。
被引用的進入點很快就把控制權交出去:
- 被引用的
docs_src教學(docs_src/apps/tutorial001_client.py)呼叫anyio.run(main); - 被引用的 story client(
examples/stories/apps/client.py)呼叫run_client(main); - 被引用的 story server 呼叫
run_server_from_args或run_app_from_args。
核心模組與推論出的角色
分析器是從靜態的跨模組呼叫次數和進入點歸屬推論出這些角色,不是從程式碼實際做的事。角色清單中的二十個模組全都位於 tests/ 下,沒有任何 src 模組出現。
- service/core 候選:
tests/interaction/_connect.py(177 個呼入、3 個呼出)和tests/interaction/auth/_harness.py(145 個呼入、1 個呼出)。 - leaf/data-boundary 候選:
tests/shared/test_dispatcher.py(117 個呼入、0 個呼出)和tests/interaction/auth/_provider.py(50 個呼入)。 - orchestration 候選:只有呼出的測試模組,例如
tests/shared/test_jsonrpc_dispatcher.py(79)和tests/interaction/auth/test_lifecycle.py(51)。
請把這份清單看成測試 harness 的地圖,主要是 tests/interaction。它並沒有為 src 中的函式庫模組排序。
靜態路徑停在哪裡
大多數邊都停在某個邊界。在 47493 個靜態關係中,41452 個是外部或未解析的,6041 個是本地的;依類型區分,有 38302 個呼叫和 9191 個 import。在列出的十條 conformance client 路徑中,有九條停在外部或未解析的呼叫,例如 logging.basicConfig、os.environ.get、sys.exit 和 logger.debug。有一條路徑結束於本地 leaf client_mode。
範例與教學的進入點會把控制權交給執行期啟動器。被引用的 docs_src 教學呼叫 anyio.run,server 教學則呼叫 mcp.run(...),例如帶有 transport="streamable-http" 和 port=3001。靜態解析是否會沿著這些呼叫回到 src,尚未確定。
分析器表示,它不會解析 reflection、動態 import、執行期依賴注入、monkey-patching、框架執行期接線或動態分派。
各部分之間的依賴
examples/下有十六個 manifest 將mcp列為執行期依賴,大多沒有指定版本。everything-server等範例 server 另外加入anyio、click、httpx2、starlette和uvicorn。- 根目錄的
pyproject.toml將mcp和mcp-example-stories列為 dev 依賴,並將rich、typer和python-dotenv列為選用。 - 根 manifest 的 31 筆記錄都沒有執行期 scope,分析資料也沒有確定原因。
src/mcp-types/pyproject.toml列出兩次pydantic,下限各不相同,另外還有typing-extensions。約束條件依原文記錄。
在 6041 個本地關係對上 41452 個外部或未解析關係的情況下,src、examples、docs_src 和 tests 之間的連結在靜態圖中只有部分可見。
靜態分析無法呈現的部分
- 執行期接線:分析器不會解析 reflection、動態 import、產生的程式碼或框架執行期接線。因此,transport、handler 和 server 在執行期如何連接,不在這些路徑的範圍內。
- 設定:啟動時傳入的選項,例如傳給
mcp.run的stateless_http=True和json_response=True,以文字形式可見,但其效果尚未確定。 - 實際執行:安裝、執行和建置的推論只完成一部分,沒有任何安裝指令經過驗證。
- 把測試當成行為:有 287 個類似測試的檔案,但分析器將它們讀成呼叫圖,不會執行它們。
- 涵蓋範圍限制:超過 400 kB 的檔案、minified bundle 和 vendored 目錄會被列入清單,但不會被解析。關係擷取也有每個檔案和每個 repository 的上限。
架構的閱讀順序
pyproject.toml。src的進入點:src/mcp/cli/__init__.py、src/mcp/client/__main__.py和src/mcp/server/__main__.py。src/mcp/server/lowlevel/server.py和src/mcp/server/mcpserver/server.py。- 一組 story,例如
examples/stories/tools/client.py及其 server。 tests/interaction/_connect.py,角色清單中被呼叫最多的模組。
這次分析無法確定的事
這些是撰寫模型對分析記錄自己的說明。lim_3、exec_* 或 claim_… 這類識別碼指的是那次分析裡的記錄;陳述與依據表引用的也是同一批記錄。
- 分析器的其中一項教學陳述表示沒有可用的有界靜態執行路徑,這與重建結果回報的 658 條有界路徑以及列出的十條路徑相衝突。
- 658 條有界路徑中只列出十條,全部來自 conformance client;沒有呈現從 src 進入點出發的流程。
- 分析資料的靜態核心流程摘要顯示,從 conformance client 的 main 可到達 HANDLERS.get 和 asyncio.run,這可能表示有基於表格的 handler 分派,但沒有任何列出的執行路徑記錄涵蓋這些邊。
- 主要進入點不明確:分析器摘要指名 .github/actions/conformance/client.py,而一項教學陳述指名 src/mcp/cli/cli.py。
- 根目錄的 pyproject.toml 沒有執行期 scope 的依賴記錄,因此核心函式庫的執行期依賴尚未確定。
- 已解析關係的樣本只顯示 docs_src 教學內的同檔案呼叫;跨目錄的邊(例如 examples 或 tests 指向 src)沒有被取樣。
陳述與依據 — 39 條陳述,39 條經獨立驗證者確認(英文原文)
Every substantive statement above is a claim bound to grounding IDs of the analyzed revision. Global grounding IDs are namespaced by the analysis run.
| Claim | Epistemic status | Verifier | Grounding (global IDs) |
|---|---|---|---|
| c1 The analyzer marks four top-level directories as likely subsystems: docs, docs_src, src and tests. | observed | supported | analysis_f7d9a9f9559ef565:subsys_1, analysis_f7d9a9f9559ef565:subsys_2, analysis_f7d9a9f9559ef565:subsys_3, analysis_f7d9a9f9559ef565:subsys_4 |
| c2 The repository summary counts 1726 analyzed files: i18n 664, examples 298, tests 285, docs_src 218, src 140, docs 58, .github 27, scripts 12, schema 4, .claude 2. | inferred | supported | analysis_f7d9a9f9559ef565:summary_repository |
| c3 Platform metadata gives Python as the primary language and lists the topics mcp, mcp-client, mcp-server and python. | observed | supported | analysis_f7d9a9f9559ef565:meta_primary_language, analysis_f7d9a9f9559ef565:meta_topics |
| c4 The repository description presents the project as a Python SDK for Model Context Protocol servers and clients. | author_claimed | supported | analysis_f7d9a9f9559ef565:meta_description |
| c5 Under src, __main__ guards exist in src/mcp/cli/__init__.py, src/mcp/client/__main__.py and src/mcp/server/__main__.py, and src/mcp-types has its own pyproject.toml with dependency records. | observed | supported | analysis_f7d9a9f9559ef565:py_entry_d9208a18098d, analysis_f7d9a9f9559ef565:py_entry_b9466646417f, analysis_f7d9a9f9559ef565:py_entry_f9a552a95482, analysis_f7d9a9f9559ef565:dep_130, analysis_f7d9a9f9559ef565:dep_132 |
| c6 A filename heuristic flags src/mcp/cli/cli.py, src/mcp/server/lowlevel/server.py and src/mcp/server/mcpserver/server.py as likely entrypoints, hinting at separate low-level and higher-level server modules. | inferred | supported | analysis_f7d9a9f9559ef565:entry_166, analysis_f7d9a9f9559ef565:entry_169, analysis_f7d9a9f9559ef565:entry_170 |
| c7 examples/stories has, for tools, prompts and oauth, a client.py, server.py and server_lowlevel.py, each with a __main__ guard. | observed | supported | analysis_f7d9a9f9559ef565:py_entry_87ea932b9cb8, analysis_f7d9a9f9559ef565:py_entry_8c07160f6185, analysis_f7d9a9f9559ef565:py_entry_21e2f5ce39f7, analysis_f7d9a9f9559ef565:py_entry_379debb54dac, analysis_f7d9a9f9559ef565:py_entry_ea329cc730dc, analysis_f7d9a9f9559ef565:py_entry_3f727f29e5ac, analysis_f7d9a9f9559ef565:py_entry_12da9740e94c, analysis_f7d9a9f9559ef565:py_entry_34af4b21106d, analysis_f7d9a9f9559ef565:py_entry_fc187148636e |
| c8 The reconstruction reports 178 entrypoints, 5460 resolved static call relations and 658 bounded execution paths across 1726 files. | inferred | supported | analysis_f7d9a9f9559ef565:architecture_reconstruction |
| c9 The analyzer summary names .github/actions/conformance/client.py as the main starting place, while a teaching claim names src/mcp/cli/cli.py; which is primary is not established. | inferred | supported | analysis_f7d9a9f9559ef565:summary_repository, analysis_f7d9a9f9559ef565:claim_8229d87e32b7, analysis_f7d9a9f9559ef565:entry_166 |
| c10 The conformance client's __main__ guard calls main(). | observed | supported | analysis_f7d9a9f9559ef565:py_entry_7ed4238a8b5b |
| c11 All ten execution paths listed in the packet start at the conformance client's __main__; none is truncated and none reports a cycle. | inferred | supported | analysis_f7d9a9f9559ef565:exec_5e86e34bd295, analysis_f7d9a9f9559ef565:exec_e6323d56ad9b, analysis_f7d9a9f9559ef565:exec_7bf8b1b02bf8, analysis_f7d9a9f9559ef565:exec_fad222196619, analysis_f7d9a9f9559ef565:exec_f72d6b612163, analysis_f7d9a9f9559ef565:exec_e615ffc0aac8, analysis_f7d9a9f9559ef565:exec_f7df7c294eff, analysis_f7d9a9f9559ef565:exec_dec7adb23cfe, analysis_f7d9a9f9559ef565:exec_67ce6661b17d, analysis_f7d9a9f9559ef565:exec_bc0fd26da427 |
| c12 Of the ten listed paths, three end at module-level logging.basicConfig, logging.getLogger and os.environ.get; seven pass through main, six of them ending at external calls (len, print, sys.exit, os.environ.get, logger.debug twice). | inferred | supported | analysis_f7d9a9f9559ef565:exec_5e86e34bd295, analysis_f7d9a9f9559ef565:exec_e6323d56ad9b, analysis_f7d9a9f9559ef565:exec_7bf8b1b02bf8, analysis_f7d9a9f9559ef565:exec_fad222196619, analysis_f7d9a9f9559ef565:exec_f72d6b612163, analysis_f7d9a9f9559ef565:exec_e615ffc0aac8, analysis_f7d9a9f9559ef565:exec_f7df7c294eff, analysis_f7d9a9f9559ef565:exec_dec7adb23cfe, analysis_f7d9a9f9559ef565:exec_67ce6661b17d, analysis_f7d9a9f9559ef565:exec_bc0fd26da427 |
| c13 Only one listed path, main to client_mode in the same file, ends as a leaf rather than at an unresolved boundary; no listed path reaches a module under src. | inferred | supported | analysis_f7d9a9f9559ef565:exec_5e86e34bd295, analysis_f7d9a9f9559ef565:exec_e6323d56ad9b, analysis_f7d9a9f9559ef565:exec_7bf8b1b02bf8, analysis_f7d9a9f9559ef565:exec_fad222196619, analysis_f7d9a9f9559ef565:exec_f72d6b612163, analysis_f7d9a9f9559ef565:exec_e615ffc0aac8, analysis_f7d9a9f9559ef565:exec_f7df7c294eff, analysis_f7d9a9f9559ef565:exec_dec7adb23cfe, analysis_f7d9a9f9559ef565:exec_67ce6661b17d, analysis_f7d9a9f9559ef565:exec_bc0fd26da427 |
| c14 In the cited entrypoints, a docs_src tutorial guard calls anyio.run(main), a story client calls run_client(main), and story servers call run_server_from_args or run_app_from_args. | observed | supported | analysis_f7d9a9f9559ef565:py_entry_5d442081d210, analysis_f7d9a9f9559ef565:py_entry_5a0eebfe2abe, analysis_f7d9a9f9559ef565:py_entry_b93c5a9e94d4, analysis_f7d9a9f9559ef565:py_entry_30a6eb23818f |
| c15 All twenty modules in the packet's role list sit under tests/; no module under src appears among them. | inferred | supported | analysis_f7d9a9f9559ef565:role_263, analysis_f7d9a9f9559ef565:role_267, analysis_f7d9a9f9559ef565:role_309, analysis_f7d9a9f9559ef565:role_310, analysis_f7d9a9f9559ef565:role_275, analysis_f7d9a9f9559ef565:role_268, analysis_f7d9a9f9559ef565:role_272, analysis_f7d9a9f9559ef565:role_289, analysis_f7d9a9f9559ef565:role_266, analysis_f7d9a9f9559ef565:role_281, analysis_f7d9a9f9559ef565:role_291, analysis_f7d9a9f9559ef565:role_270, analysis_f7d9a9f9559ef565:role_274, analysis_f7d9a9f9559ef565:role_301, analysis_f7d9a9f9559ef565:role_290, analysis_f7d9a9f9559ef565:role_292, analysis_f7d9a9f9559ef565:role_314, analysis_f7d9a9f9559ef565:role_273, analysis_f7d9a9f9559ef565:role_282, analysis_f7d9a9f9559ef565:role_283 |
| c16 tests/interaction/_connect.py (177 incoming, 3 outgoing) and tests/interaction/auth/_harness.py (145 incoming, 1 outgoing) are labelled service/core candidates. | inferred | supported | analysis_f7d9a9f9559ef565:role_263, analysis_f7d9a9f9559ef565:role_267 |
| c17 tests/shared/test_dispatcher.py (117 incoming, 0 outgoing) and tests/interaction/auth/_provider.py (50 incoming) are labelled leaf/data-boundary candidates. | inferred | supported | analysis_f7d9a9f9559ef565:role_309, analysis_f7d9a9f9559ef565:role_268 |
| c18 Test modules with only outgoing calls, such as tests/shared/test_jsonrpc_dispatcher.py (79) and tests/interaction/auth/test_lifecycle.py (51), are labelled orchestration candidates. | inferred | supported | analysis_f7d9a9f9559ef565:role_310, analysis_f7d9a9f9559ef565:role_275 |
| c19 Every listed role is derived from static resolved cross-module call degree and entrypoint membership, not from reading what the code does. | inferred | supported | analysis_f7d9a9f9559ef565:role_263, analysis_f7d9a9f9559ef565:role_267, analysis_f7d9a9f9559ef565:role_309, analysis_f7d9a9f9559ef565:role_310, analysis_f7d9a9f9559ef565:role_275, analysis_f7d9a9f9559ef565:role_268, analysis_f7d9a9f9559ef565:role_272, analysis_f7d9a9f9559ef565:role_289, analysis_f7d9a9f9559ef565:role_266, analysis_f7d9a9f9559ef565:role_281, analysis_f7d9a9f9559ef565:role_291, analysis_f7d9a9f9559ef565:role_270, analysis_f7d9a9f9559ef565:role_274, analysis_f7d9a9f9559ef565:role_301, analysis_f7d9a9f9559ef565:role_290, analysis_f7d9a9f9559ef565:role_292, analysis_f7d9a9f9559ef565:role_314, analysis_f7d9a9f9559ef565:role_273, analysis_f7d9a9f9559ef565:role_282, analysis_f7d9a9f9559ef565:role_283 |
| c20 The role list reads as a map of mostly test-harness modules, largely under tests/interaction; since no src module appears in it, it does not rank library modules in src. | inferred | supported | analysis_f7d9a9f9559ef565:role_263, analysis_f7d9a9f9559ef565:role_267, analysis_f7d9a9f9559ef565:role_309, analysis_f7d9a9f9559ef565:role_310, analysis_f7d9a9f9559ef565:role_275, analysis_f7d9a9f9559ef565:role_268, analysis_f7d9a9f9559ef565:role_272, analysis_f7d9a9f9559ef565:role_289, analysis_f7d9a9f9559ef565:role_266, analysis_f7d9a9f9559ef565:role_281, analysis_f7d9a9f9559ef565:role_291, analysis_f7d9a9f9559ef565:role_270, analysis_f7d9a9f9559ef565:role_274, analysis_f7d9a9f9559ef565:role_301, analysis_f7d9a9f9559ef565:role_290, analysis_f7d9a9f9559ef565:role_292, analysis_f7d9a9f9559ef565:role_314, analysis_f7d9a9f9559ef565:role_273, analysis_f7d9a9f9559ef565:role_282, analysis_f7d9a9f9559ef565:role_283 |
| c21 Of 47493 static relations, 41452 are external or unresolved and 6041 are local; by type there are 38302 calls and 9191 imports. | observed | supported | analysis_f7d9a9f9559ef565:relation_counts |
| c22 Of the ten listed conformance-client paths, nine stop at external or unresolved calls such as logging.basicConfig, os.environ.get, sys.exit and logger.debug; one ends at the local leaf client_mode. | inferred | supported | analysis_f7d9a9f9559ef565:exec_5e86e34bd295, analysis_f7d9a9f9559ef565:exec_e6323d56ad9b, analysis_f7d9a9f9559ef565:exec_7bf8b1b02bf8, analysis_f7d9a9f9559ef565:exec_fad222196619, analysis_f7d9a9f9559ef565:exec_f72d6b612163, analysis_f7d9a9f9559ef565:exec_e615ffc0aac8, analysis_f7d9a9f9559ef565:exec_f7df7c294eff, analysis_f7d9a9f9559ef565:exec_dec7adb23cfe, analysis_f7d9a9f9559ef565:exec_67ce6661b17d, analysis_f7d9a9f9559ef565:exec_bc0fd26da427 |
| c23 The cited docs_src tutorial guards call anyio.run, and a server tutorial calls mcp.run with transport="streamable-http" and port=3001. | observed | supported | analysis_f7d9a9f9559ef565:py_entry_5d442081d210, analysis_f7d9a9f9559ef565:py_entry_fb08908da90c, analysis_f7d9a9f9559ef565:py_entry_2f2371a70335, analysis_f7d9a9f9559ef565:py_entry_b3dddc9af128 |
| c24 Whether static resolution follows mcp.run or anyio.run back into src is not established by the packet. | unresolved | supported | analysis_f7d9a9f9559ef565:py_entry_b3dddc9af128, analysis_f7d9a9f9559ef565:lim_1 |
| c25 The analyzer documents that reflection, runtime dependency injection, dynamic imports, monkey-patching, framework runtime wiring and dynamic dispatch are not resolved. | observed | supported | analysis_f7d9a9f9559ef565:lim_1 |
| c26 Of the dependency records, the sixteen cited show manifests under examples/ declaring mcp as a runtime dependency, all but one without a version constraint. | observed | supported | analysis_f7d9a9f9559ef565:dep_2, analysis_f7d9a9f9559ef565:dep_8, analysis_f7d9a9f9559ef565:dep_11, analysis_f7d9a9f9559ef565:dep_17, analysis_f7d9a9f9559ef565:dep_21, analysis_f7d9a9f9559ef565:dep_25, analysis_f7d9a9f9559ef565:dep_34, analysis_f7d9a9f9559ef565:dep_45, analysis_f7d9a9f9559ef565:dep_52, analysis_f7d9a9f9559ef565:dep_59, analysis_f7d9a9f9559ef565:dep_66, analysis_f7d9a9f9559ef565:dep_75, analysis_f7d9a9f9559ef565:dep_84, analysis_f7d9a9f9559ef565:dep_91, analysis_f7d9a9f9559ef565:dep_97, analysis_f7d9a9f9559ef565:dep_98 |
| c27 The root pyproject.toml records mcp and mcp-example-stories as dev dependencies, and rich, typer and python-dotenv as optional dependencies. | observed | supported | analysis_f7d9a9f9559ef565:dep_99, analysis_f7d9a9f9559ef565:dep_100, analysis_f7d9a9f9559ef565:dep_101, analysis_f7d9a9f9559ef565:dep_102, analysis_f7d9a9f9559ef565:dep_103 |
| c28 None of the 31 dependency records sourced from the root pyproject.toml has runtime scope; each is optional or dev. | observed | supported | analysis_f7d9a9f9559ef565:dep_99, analysis_f7d9a9f9559ef565:dep_100, analysis_f7d9a9f9559ef565:dep_101, analysis_f7d9a9f9559ef565:dep_102, analysis_f7d9a9f9559ef565:dep_103, analysis_f7d9a9f9559ef565:dep_104, analysis_f7d9a9f9559ef565:dep_105, analysis_f7d9a9f9559ef565:dep_106, analysis_f7d9a9f9559ef565:dep_107, analysis_f7d9a9f9559ef565:dep_108, analysis_f7d9a9f9559ef565:dep_109, analysis_f7d9a9f9559ef565:dep_110, analysis_f7d9a9f9559ef565:dep_111, analysis_f7d9a9f9559ef565:dep_112, analysis_f7d9a9f9559ef565:dep_113, analysis_f7d9a9f9559ef565:dep_114, analysis_f7d9a9f9559ef565:dep_115, analysis_f7d9a9f9559ef565:dep_116, analysis_f7d9a9f9559ef565:dep_117, analysis_f7d9a9f9559ef565:dep_118, analysis_f7d9a9f9559ef565:dep_119, analysis_f7d9a9f9559ef565:dep_120, analysis_f7d9a9f9559ef565:dep_121, analysis_f7d9a9f9559ef565:dep_122, analysis_f7d9a9f9559ef565:dep_123, analysis_f7d9a9f9559ef565:dep_124, analysis_f7d9a9f9559ef565:dep_125, analysis_f7d9a9f9559ef565:dep_126, analysis_f7d9a9f9559ef565:dep_127, analysis_f7d9a9f9559ef565:dep_128, analysis_f7d9a9f9559ef565:dep_129 |
| c29 Why the root manifest shows no runtime dependency records is not established; the analyzer states it parses PEP 621 dependencies, so a parsing gap or another declaration location are both possible. | unresolved | supported | analysis_f7d9a9f9559ef565:lim_3a |
| c30 src/mcp-types/pyproject.toml lists pydantic twice with lower bounds >=2.14.0 and >=2.12.0, plus typing-extensions; version constraints are recorded as written. | observed | supported | analysis_f7d9a9f9559ef565:dep_130, analysis_f7d9a9f9559ef565:dep_131, analysis_f7d9a9f9559ef565:dep_132, analysis_f7d9a9f9559ef565:lim_3a |
| c31 The everything-server example manifest declares anyio, click, httpx2, starlette and uvicorn alongside mcp as runtime dependencies. | observed | supported | analysis_f7d9a9f9559ef565:dep_22, analysis_f7d9a9f9559ef565:dep_23, analysis_f7d9a9f9559ef565:dep_24, analysis_f7d9a9f9559ef565:dep_25, analysis_f7d9a9f9559ef565:dep_26, analysis_f7d9a9f9559ef565:dep_27 |
| c32 With 6041 local relations against 41452 external or unresolved ones, links between the repository's parts are only partly visible in the static graph. | inferred | supported | analysis_f7d9a9f9559ef565:relation_counts |
| c33 Because reflection, dynamic imports, generated code and framework runtime wiring are not resolved, how transports, handlers and servers connect at run time lies outside the static paths. | inferred | supported | analysis_f7d9a9f9559ef565:lim_1 |
| c34 Install, run and build inference is partial, and installation commands are not verified. | observed | supported | analysis_f7d9a9f9559ef565:lim_2 |
| c35 Startup options such as stateless_http=True and json_response=True passed to mcp.run are visible as text, but their effect is not established. | unresolved | supported | analysis_f7d9a9f9559ef565:py_entry_52515d0b932c, analysis_f7d9a9f9559ef565:lim_1 |
| c36 The repository summary counts 287 test-like files, but static analysis reads them as call graphs rather than executing them. | inferred | supported | analysis_f7d9a9f9559ef565:summary_repository, analysis_f7d9a9f9559ef565:lim_1 |
| c37 Files over 400 kB, minified bundles and vendored directories are inventoried but not parsed, and relation extraction is capped per file and per repository. | observed | supported | analysis_f7d9a9f9559ef565:lim_6 |
| c38 A reading order consistent with the packet: pyproject.toml, the src __main__ entrypoints, the lowlevel and mcpserver server modules, then one examples/stories set. | inferred | supported | analysis_f7d9a9f9559ef565:important_2, analysis_f7d9a9f9559ef565:py_entry_d9208a18098d, analysis_f7d9a9f9559ef565:py_entry_b9466646417f, analysis_f7d9a9f9559ef565:py_entry_f9a552a95482, analysis_f7d9a9f9559ef565:entry_169, analysis_f7d9a9f9559ef565:entry_170, analysis_f7d9a9f9559ef565:py_entry_87ea932b9cb8 |
| c39 tests/interaction/_connect.py has the highest incoming call count in the role list, which makes it a useful entry into the test harness. | inferred | supported | analysis_f7d9a9f9559ef565:role_263 |
來源、權利與說明 · attribution-license-templates/v0.1
權利聲明。原始 repository 託管於 GitHub。其原始碼、文件、名稱、媒體與相關素材的權利,仍屬各自的作者、貢獻者與其他權利人所有,並受該 repository 的授權條款約束。
Original repository hosted on GitHub. Repository source code, documentation, names, media, and related project materials remain subject to the rights of their respective authors, contributors, and other rights holders and to applicable repository license terms.
平台聲明。GitHub 是所連結 repository 的來源託管平台。GitHub 與相關標誌為 GitHub, Inc. 的商標。除非另有明確說明,EVEMISS Technology 與 GitHub 之間沒有隸屬或背書關係。
GitHub is the source hosting platform for the linked repository. GitHub and related marks are trademarks of GitHub, Inc. EVEMISS Technology is not affiliated with or endorsed by GitHub unless explicitly stated otherwise.
這一頁怎麼來的。本頁由對應版本的 repository 分析與 AI 輔助的編輯工具產生。技術陳述綁定所分析的版本;原始 repository 更新後,可能重新驗證。
This page was produced using revision-aware repository analysis and AI-assisted editorial tooling. Technical claims are tied to the analyzed repository revision and may be revalidated when the source repository changes.
本頁包含 AI 輔助分析,並經 EVEMISS Technology 人工與 AI 協力審閱。 · 回報權利疑慮 · 回到概覽