mcp
pypi package · declared by 136 of 2,343 sampled repositories · graph computed 2026-08-24
Counted from the runtime dependencies public repositories declare — not the resolved tree. A transitive dependency is a consequence; a declared one is a choice. Development dependencies are excluded because they repeat across every project in a language regardless of what is being built.
Declared with
ranked by association, not by count| Declared with | Repositories | vs chance |
|---|---|---|
| opentelemetry-api | 9 of 2,343 | 0.40 |
| pathspec | 9 of 2,343 | 0.40 |
| watchdog | 11 of 2,343 | 0.40 |
| prompt-toolkit | 10 of 2,343 | 0.37 |
| python-docx | 9 of 2,343 | 0.34 |
| uvicorn | 41 of 2,343 | 0.32 |
| websockets | 15 of 2,343 | 0.32 |
| httpx | 40 of 2,343 | 0.32 |
| fastmcp | 11 of 2,343 | 0.31 |
| rich | 34 of 2,343 | 0.31 |
| python-dotenv | 40 of 2,343 | 0.31 |
| anthropic | 14 of 2,343 | 0.30 |
| jsonschema | 9 of 2,343 | 0.30 |
| google-genai | 9 of 2,343 | 0.30 |
| starlette | 10 of 2,343 | 0.30 |
| typer | 20 of 2,343 | 0.29 |
| jinja2 | 18 of 2,343 | 0.29 |
| boto3 | 8 of 2,343 | 0.29 |
| pyyaml | 38 of 2,343 | 0.28 |
| pydantic | 49 of 2,343 | 0.27 |
Every pair above is counted from the same evidence: repo manifest.
Used instead
candidates · shares a neighbourhood and refuses to co-occurNo alternative measured. A pair qualifies only if it shares a neighbourhood and then fails to appear together against an expectation that it would — and almost everything that shares a neighbourhood does appear together. That is the test working, not a gap in the data: similarity alone would list this tool’s closest neighbours as alternatives, and most of them are things it is used with.