MCP server expose nuanced.dev functionality
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":"iflow-mcp-nuanced-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.
# Nuanced MCP Server A [Model Context Protocol (MCP)](https://modelcontextprotocol.io) server that provides call graph analysis capabilities to LLMs through the [nuanced](https://github.com/nuanced-dev/nuanced) library. ## Overview This MCP server enables LLMs to understand code structure by accessing function call graphs through standardized tools and resources. It allows AI assistants to: - Initialize call graphs for Python repos - Explore function call relationships - Analyze dependencies between functions - Provide more contextually aware code assistance ## API ### Tools - **initialize_graph** - Initialize a code graph for the given repository path - Input: `repo_path` (string) - **switch_repository** - Switch to a different initialized repository - Input: `repo_path` (string) - **list_repositories** - List all initialized repositories - No inputs required - **get_function_call_graph** - Get the call graph for a specific function - Inputs: - `file_path` (string) - `function_name` (string) - `repo_path` (string, optional) - uses active repository if not specified - **analyze_dependencies** - Find all module or file dependencies in the codebase - Inputs (at least one required): - `file_path` (string, optional) - `module_name` (string, optional) - **analyze_change_impact** - Analyze the impact of changing a specific function - Inputs: - `file_path` (string) - `function_name` (string) ### Resources - **graph://summary** - Get a summary of the currently loaded code graph - No parameters required - **graph://repo/{repo_path}/summary** - Get a summary of a specific repository's code graph - Parameters: - `repo_path` (string) - Path to the repository - **graph://function/{file_path}/{function_name}** - Get detailed information about a specific function - Parameters: - `file_path` (string) - Path to the file containing the function - `function_name` (string) - Name of the …
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.