MCP server providing project analysis tools: statistics, code search, module listing, and dependency analysis.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"project-analysis-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# project-analysis-mcp An [MCP](https://modelcontextprotocol.io) server that helps an LLM understand and analyze a codebase. It exposes four read-only tools: | Tool | Description | |------|-------------| | `project_stats` | File/line statistics grouped by file extension | | `find_code` | Search source files for a text/regex pattern (with context) | | `list_modules` | List Python modules with their docstrings and class/function structure | | `analyze_dependency` | Analyze how a dependency is imported/used across a project | Transport: **stdio** (JSON-RPC). Python ≥ 3.11. ## Install & run ### Option A — from PyPI (recommended) ```bash uvx project-analysis-mcp # or pipx install project-analysis-mcp ``` ### Option B — from this repo (editable) ```bash cd mcp-servers/project_analysis_mcp_pkg uv pip install -e . # then run: project-analysis-mcp ``` ### Option C — run the module directly (no install) ```bash uv run --directory <repo-root> python mcp-servers/project_analysis_mcp.py ``` ## Configure a client Add the server to your client's MCP config (the exact file depends on the client: `mcp.json`, `settings.json`, `claude_desktop_config.json`, etc.). **Using the console script (after install):** ```json { "mcpServers": { "Project Analysis": { "command": "project-analysis-mcp" } } } ``` **Using `uvx` (auto-fetches the package):** ```json { "mcpServers": { "Project Analysis": { "command": "uvx", "args": ["project-analysis-mcp"] } } } ``` **Using the repo directly (no publish):** ```json { "mcpServers": { "Project Analysis": { "command": "uv", "args": [ "run", "--directory", "/abs/path/to/repo", "python", "/abs/path/to/repo/mcp-servers/project_analysis_mcp.py" ], "env": {} } } } ``` ## Notes - All tools are read-only and operate on a `project_path` you pass in. - Binary/large/ignored files are skipped automatically. - Compatible with any MCP client that supports…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.