Repository guide · architecture · v2
modelcontextprotocol / python-sdk · Architecture
A Python repository of 1726 analyzed files, mostly under i18n, examples, tests and docs_src, with library code under src. The listed static paths start at a conformance client and mostly stop at external or unresolved standard-library calls. Most relations stay unresolved. The highest-degree modules the analyzer found are test harnesses.
- Original repository
- modelcontextprotocol/python-sdk
- License
- MIT · open-source license
- Analyzed revision · last verified
- 77001c96f9507be0f4d009b83210a384a5e08bda ·
modelcontextprotocol/python-sdk architecture: how it is structured
Terms used on this page
- Entrypoint record
- A file the analyzer marks as a place where execution can start. When it carries a __main__ guard excerpt, the file contains an if __name__ == "__main__": block and the excerpt shows what that block calls; without an excerpt, the file was flagged by its name only.
- Bounded static execution path
- A call chain reconstructed from the source code without running it, stopped after a fixed number of steps. It shows how far the code can be followed on paper, not what happens at run time.
- Unresolved boundary
- Where a static path stops because the next call goes into an external library or cannot be resolved without running the code. It marks the edge of this analysis, not a defect in the repository.
- Static relations
- Calls and imports found in the source. "External or unresolved" relations point outside the analyzed files.
- Module role
- The analyzer's label for a file, inferred from how many calls go in and out (for example core, entry/orchestration, leaf). It describes a position in the call graph, not the authors' design.
- Test-like files
- Files whose names or locations look like tests. This analysis counts them; it does not run them.
- Observed · inferred · author-claimed · unresolved
- How each statement is supported: read directly from the analyzed files; derived by the analyzer from them; stated by the repository's authors (metadata, README); or not established by this analysis.
- Verified
- Two uses on these pages. In an analyzer record ("verified provenance", "a verified entrypoint") it means the record was read directly from the analyzed files, which these guides call observed; for an entrypoint, the __main__ guard text is present. Since the analyzer fix of 2026-10-04, a file that only has an entrypoint-like name such as cli.py or main.py is recorded as inferred; guides analyzed before that still call such a file verified, and it is still only a guess about how the file is used. It does not mean the code was run or tested. "Last verified" is the date the guide last passed the lab's checks against the analysis record of the stated revision; it is not a review of the repository itself.
Shape at a glance
The analyzer marks four top-level directories as likely subsystems: docs, docs_src, src and tests. Of 1726 analyzed files, most sit outside src. Four directories are each larger than src (140): i18n (664), examples (298), tests (285) and docs_src (218). Smaller ones are docs (58), .github (27) and scripts (12). Platform metadata lists Python as the primary language, with topics around MCP clients and servers. The description presents the project as a Python SDK for Model Context Protocol servers and clients.
srchas__main__guards insrc/mcp/cli/__init__.py,src/mcp/client/__main__.pyandsrc/mcp/server/__main__.py.src/mcp-typescarries its ownpyproject.toml.- Filename heuristics add
src/mcp/cli/cli.py,src/mcp/server/lowlevel/server.pyandsrc/mcp/server/mcpserver/server.py. This hints at separate low-level and higher-level server modules. examples/storiesholds client and server script sets. For topics such astools,promptsandoauth, each set hasclient.py,server.pyandserver_lowlevel.py.
Entrypoints and control flow
The reconstruction reports 178 entrypoints, 5460 resolved call relations and 658 bounded paths. The analyzer names .github/actions/conformance/client.py as the main starting place. One of its teaching claims names src/mcp/cli/cli.py instead, and which one is primary is not established.
The conformance client's __main__ guard calls main(). All ten paths in the packet start there, with no truncation and no cycles:
- three end at module-level calls (
logging.basicConfig,logging.getLogger,os.environ.get); - seven pass through
main, and six of these end at external calls such assys.exit,printandlogger.debug; - one,
main→client_modein the same file, ends as a leaf.
No listed path reaches a module under src.
The cited entrypoints hand off quickly:
- the cited
docs_srctutorial (docs_src/apps/tutorial001_client.py) callsanyio.run(main); - the cited story client (
examples/stories/apps/client.py) callsrun_client(main); - the cited story servers call
run_server_from_argsorrun_app_from_args.
Core modules and their inferred roles
The analyzer infers these roles from static cross-module call counts and entrypoint membership, not from what the code does. All twenty modules in the role list sit under tests/, and no src module appears.
- Service/core candidates:
tests/interaction/_connect.py(177 in, 3 out) andtests/interaction/auth/_harness.py(145 in, 1 out). - Leaf/data-boundary candidates:
tests/shared/test_dispatcher.py(117 in, 0 out) andtests/interaction/auth/_provider.py(50 in). - Orchestration candidates: test modules with only outgoing calls, such as
tests/shared/test_jsonrpc_dispatcher.py(79) andtests/interaction/auth/test_lifecycle.py(51).
Read this list as a map of the test harness, mostly tests/interaction. It does not rank the library modules in src.
Where static paths stop
Most edges stop at a boundary. Of 47493 static relations, 41452 are external or unresolved and 6041 are local; by type there are 38302 calls and 9191 imports. 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 path ends at the local leaf client_mode.
Example and tutorial entrypoints hand off to runtime launchers. The cited docs_src tutorials call anyio.run, and server tutorials call mcp.run(...), for example with transport="streamable-http" and port=3001. Whether static resolution follows these calls back into src is not established.
The analyzer states that it does not resolve reflection, dynamic imports, runtime dependency injection, monkey-patching, framework runtime wiring or dynamic dispatch.
Dependencies between parts
- Sixteen manifests under
examples/listmcpas a runtime dependency, mostly without a version. - Example servers such as
everything-serveraddanyio,click,httpx2,starletteanduvicorn. - The root
pyproject.tomllistsmcpandmcp-example-storiesas dev dependencies, andrich,typerandpython-dotenvas optional. - None of the root manifest's 31 records has runtime scope, and the packet does not establish why.
src/mcp-types/pyproject.tomllistspydantictwice with different lower bounds, plustyping-extensions. Constraints are recorded as written.
With 6041 local relations against 41452 external or unresolved ones, the links between src, examples, docs_src and tests are only partly visible in the static graph.
What static analysis cannot show
- Runtime wiring: the analyzer does not resolve reflection, dynamic imports, generated code or framework runtime wiring. How transports, handlers and servers connect at run time is therefore outside these paths.
- Configuration: options passed at startup, such as
stateless_http=Trueandjson_response=Truetomcp.run, are visible as text, but their effect is not established. - Running it: install, run and build inference is partial, and no installation command is verified.
- Tests as behaviour: there are 287 test-like files, but the analyzer reads them as call graphs and does not execute them.
- Coverage bounds: files over 400 kB, minified bundles and vendored directories are inventoried but not parsed. Relation extraction is also capped per file and per repository.
Reading order for the architecture
pyproject.toml.- The
srcentrypoints:src/mcp/cli/__init__.py,src/mcp/client/__main__.pyandsrc/mcp/server/__main__.py. src/mcp/server/lowlevel/server.pyandsrc/mcp/server/mcpserver/server.py.- One story set, such as
examples/stories/tools/client.pywith its servers. tests/interaction/_connect.py, the most-called module in the role list.
What this analysis could not establish
The writing model's own notes on the analysis record. Identifiers such as lim_3, exec_* or claim_… name records of that analysis; the claims table cites the same records.
- One of the analyzer's teaching claims states that no bounded static execution path is available, which conflicts with the 658 bounded paths reported by the reconstruction and the ten paths listed.
- Only ten of the 658 bounded paths are listed, all from the conformance client; flows from src entrypoints are not shown.
- The packet's static core-flow summary shows HANDLERS.get and asyncio.run reached from the conformance client's main, which may indicate table-based handler dispatch, but no listed execution-path record covers these edges.
- The primary entrypoint is ambiguous: the analyzer summary names .github/actions/conformance/client.py, while a teaching claim names src/mcp/cli/cli.py.
- No runtime-scope dependency record exists for the root pyproject.toml, so the core library's runtime dependencies are not established.
- The resolved relation sample shows only intra-file calls inside docs_src tutorials; cross-directory edges (for example examples or tests into src) are not sampled.
Claims and evidence — 39 claims, 39 supported by an independent verifier
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 |
Sources, rights and disclosure · attribution-license-templates/v0.1
Rights notice. 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.
Platform notice. 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.
How this page is produced. 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-assisted analysis. Reviewed by EVEMISS Technology through human–AI collaborative review. · Report a rights concern · Back to the overview