Code-Fundi MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

code-fundi-repo-map

Read-only

Map a dependency across source, compared repositories, and public index to locate its usage. Returns structured JSON for blast radius analysis.

Instructions

Build a cross-repository dependency map showing where a dependency appears across the source repo, optional compared repos, and (optionally) the public index. Returns structured JSON. Consumes credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "repo_key": "<repo_key>"
    },
    "name": "code-fundi-repo-map"
  }
}

Input Schema

Name	Required	Description
`demo`	No	Run in demo mode (pre-signup, public data, IP-based credits)
`type`	No	Dependency type filter
`limit`	No	Max dependencies (default 25)
`repo_key`	Yes	Repository UUID or clone URL
`dependency`	No	Dependency name to map
`compare_repos`	No	Repository UUIDs to compare against (max 10)
`files_per_repo`	No	Max files per repo (default 25)
`include_public_index`	No	Include matches from the public index (default false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.4Jul 31, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds meaningful behavioral detail: it consumes credits and returns structured JSON. There is no contradiction between the description and annotations, and the added credit consumption is important operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two succinct sentences. The first sentence states the core function and options; the second covers return format and credit cost. No wasted words, and key information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core build operation, optional inputs, return type, and credit consumption. While there is no output schema, the 'Returns structured JSON' statement is minimal but acceptable for a read-only mapping tool with fully described parameters in the input schema. It is not exhaustive about output shape, but it is complete enough for invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with every parameter having a description. The tool description only echoes the optional compare repos and public index features, adding no new parameter-level semantics or syntax details beyond the schema. Baseline 3 is appropriate because the schema carries the parameter documentation load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb phrase 'Build a cross-repository dependency map' and a clear resource (dependency map across repositories). It distinguishes this tool from siblings by emphasizing cross-repo mapping and optional public index inclusion, which no sibling name suggests.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the tool's scope (source repo, optional compared repos, optional public index) and notes credit consumption, giving clear contextual usage. It does not explicitly name alternatives or state when not to use this tool, but the context is sufficiently clear among the sibling list.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.