# repomap (npm · @sylphx/repomap)

A map of your codebase for AI agents: code graph, search, call paths and change impact. No API key.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- npm · `@sylphx/repomap`: 69/100 (this document), [markdown](https://verifymcp.io/servers/sylphxai-repomap/sylphx-repomap.md), [page](https://verifymcp.io/servers/sylphxai-repomap/sylphx-repomap)

## Channel facts

- Registry: `npm`
- Package: `@sylphx/repomap`
- Version: `1.3.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Supply Chain Security**: 63/100
  - No malware found by supply-chain analysis.
  - Known CVEs could not be checked: the version this server declares is not published in its registry.
  - No install/post-install scripts declared.
  - Dependency health could not be checked: the version this server declares is not published in its registry.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to SylphxAI/repomap).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1101 tokens (~183/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the repomap MCP server?

repomap runs locally as an npm package, launched with npx -y @sylphx/repomap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add sylphxai-repomap -- npx -y @sylphx/repomap
```

### Cursor

```json
{
  "mcpServers": {
    "sylphxai-repomap": {
      "command": "npx",
      "args": [
        "-y",
        "@sylphx/repomap"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sylphxai-repomap": {
      "command": "npx",
      "args": [
        "-y",
        "@sylphx/repomap"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sylphxai-repomap -- npx -y @sylphx/repomap
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sylphxai-repomap": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@sylphx/repomap"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sylphxai-repomap --command npx --arg -y --arg @sylphx/repomap
```

### Hermes

```yaml
mcp_servers:
  sylphxai-repomap:
    command: "npx"
    args: ["-y", "@sylphx/repomap"]
```

### Netclaw

```json
{
  "McpServers": {
    "sylphxai-repomap": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@sylphx/repomap"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add sylphxai-repomap -t stdio -c npx -a -y @sylphx/repomap
```

### Other

```json
{
  "mcpServers": {
    "sylphxai-repomap": {
      "command": "npx",
      "args": [
        "-y",
        "@sylphx/repomap"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-26 (score 69, −11)

- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: 1.00 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 1.2.2 → 1.3.2
- [functional] Package version: 1.2.2 → 1.3.0

### 2026-09-25 (score 80)

First indexed and scored.

## MCP tools (6)

### `map` (~142 tokens)

Map the codebase

Start here. A map of the repository: modules (communities of files that depend on each other), the most central files (PageRank), the most used symbols, and entry points. Pass `focus` (a directory) to zoom in and get an outline of its files and symbols with line numbers.

Input parameters:

- `focus` (string): Directory to zoom into, e.g. src/server.
- `format` (string): text (default, compact, file:line cited) or json.
- `limit` (integer): Items per section (default 12).
- `root` (string): Repository root. Defaults to the client's workspace root or the server's working directory.

### `search` (~173 tokens)

Search code

Hybrid code search over AST chunks (whole functions, methods, classes): symbol names, BM25 keywords and a local code embedding model, so identifiers and plain questions both work, e.g. "parseConfig", "refresh token expiry" or "where are failed requests retried". Returns ranked file:line ranges with the matching lines.

Input parameters:

- `format` (string): text (default, compact, file:line cited) or json.
- `include_tests` (boolean): Default true (tests rank lower).
- `kind` (string)
- `limit` (integer): Max results (default 10).
- `path` (string): Only files whose path starts with or contains this.
- `query` (string, required)
- `root` (string): Repository root. Defaults to the client's workspace root or the server's working directory.

### `context` (~149 tokens)

360° view of a symbol or file

Everything about one symbol or file: its code, who calls it (with call-site lines), what it calls, subtypes, members, imports, importers and the tests that touch it. Target forms: `path/to/file.ts`, `file.ts:42`, `Class.method`, `Class::method`, or a bare name.

Input parameters:

- `code_lines` (integer): Lines of source to include for a symbol (default 60, 0 for none).
- `format` (string): text (default, compact, file:line cited) or json.
- `root` (string): Repository root. Defaults to the client's workspace root or the server's working directory.
- `target` (string, required)

### `trace` (~138 tokens)

Trace call paths

With `from` and `to`: the shortest call path between two symbols or files, each hop cited file:line (falls back to the file dependency path). With only `from`: the call tree below it (direction callees) or above it (direction callers).

Input parameters:

- `depth` (integer): Tree depth (default 3).
- `direction` (string)
- `format` (string): text (default, compact, file:line cited) or json.
- `from` (string, required)
- `root` (string): Repository root. Defaults to the client's workspace root or the server's working directory.
- `to` (string)

### `impact` (~158 tokens)

Change impact (blast radius)

What breaks if this changes. Give `target` (symbol or file, or a list) or `changed: true` to analyse the current git diff. Returns a risk level, direct and indirect callers with call sites, importing files, modules touched, and the tests to run.

Input parameters:

- `base` (string): Git ref for `changed` (default HEAD).
- `changed` (boolean): Use the working-tree git diff (against `base`).
- `depth` (integer): Caller depth (default 3).
- `format` (string): text (default, compact, file:line cited) or json.
- `root` (string): Repository root. Defaults to the client's workspace root or the server's working directory.
- `target`

### `db` (~223 tokens)

Database map

Map the database: tables, columns, primary and foreign keys, indexes, and the code that queries each table (file:line). By default it reads schema sources in the repo: SQL migrations, Prisma, Drizzle, SQLAlchemy and Diesel. To inspect a live Postgres, MySQL or SQLite database, pass `url_env` (the NAME of an environment variable holding the connection string). The connection is strictly read-only and the string is never stored or shown. Pass `table` for one table's full detail.

Input parameters:

- `format` (string): text (default, compact, file:line cited) or json.
- `root` (string): Repository root. Defaults to the client's workspace root or the server's working directory.
- `table` (string): Focus on one table: columns, indexes, who references it, and where the code queries it.
- `url` (string): Connection string (prefer url_env so secrets stay out of transcripts).
- `url_env` (string): Name of an env var with the connection string, e.g. DATABASE_URL.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/sylphxai-repomap/sylphx-repomap#diagnostics

## Score history

- 2026-09-26: 69
- 2026-09-25: 80

## Common questions

### What is the repomap MCP server?

repomap is an MCP server listed in the public MCP registry as io.github.SylphxAI/repomap. A map of your codebase for AI agents: code graph, search, call paths and change impact. No API key. This page covers its npm package (@sylphx/repomap).

### Is the repomap MCP server safe to use?

repomap scores 69 out of 100 on VerifyMCP. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the repomap MCP server expose?

repomap exposes 6 tools: map, search, context, trace, impact, db. Their descriptions and schemas cost roughly 983 tokens of context every time the server is loaded.

### Is the repomap MCP server still maintained?

repomap is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the repomap MCP server under?

repomap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@sylphx/repomap
- Socket report: https://socket.dev/npm/package/@sylphx/repomap
- Repository: https://github.com/SylphxAI/repomap
- Website: https://sylphxai.github.io/repomap/
- Changelog RSS feed: https://verifymcp.io/servers/sylphxai-repomap/sylphx-repomap.xml
- Changelog JSON feed: https://verifymcp.io/servers/sylphxai-repomap/sylphx-repomap.json
- HTML version of this page: https://verifymcp.io/servers/sylphxai-repomap/sylphx-repomap