MCP.Market

Throughline MCP server

by devznsh·io.github.devznsh/throughline·v1.0.1

Give Claude complete understanding of your software project.

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Throughline yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Throughline tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 53 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Throughline compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 48,255 servers

Install Throughline in Claude Code, Cursor or VS Code

The registry entry has no remote endpoint or installable package.

What the publisher says

From the Throughline repository's README, as published. We do not edit it. Read it on GitHub

Throughline

Give Claude complete understanding of your software project.

Point it at a repository on your machine. It reads every file, extracts symbols with tree-sitter, resolves imports into a call graph, ingests git history, and exposes the whole thing to Claude as precise retrieval tools.

Then you can ask the questions you actually have — "where is rate limiting handled?", "what breaks if I change this?" — and get real file paths and line numbers instead of plausible-sounding guesses.

Everything runs locally. This extension makes no network requests of any kind.

What it looks like

You: where does indexing decide a file has changed?

3 matches for "where does indexing decide a file has changed"

### src/core/services/index-repository.ts:171-186
method IndexingService.index — src/core/services/index-repository.ts:171-186
why: text match; 15 inbound references; 6 matches in this file

      const hash = contentHash(buffer);
      const previous = known.get(scanned.relPath);
      ...
      if (mode === 'incremental' && previous === hash) {
        unchanged.push(scanned.relPath);
        continue;
      }

That why: line is the point. Results are ranked by how structurally central they are — inbound references, export status, architectural role — not by how many times a word appears. A file that mentions caching loses to the one that implements it.

What you can ask

Eighteen tools in total — see docs/TOOLS.md.

Supported languages

Full symbol extraction — TypeScript · TSX · JavaScript · JSX · Python · Go · Java · Kotlin · C# · Rust · C · C++ · YAML · JSON

Text-searchable only — SQL · Markdown · Dockerfile · Terraform (grammars not yet vendored; files are indexed and searchable, but no symbols are extracted)

Anything else is still catalogued and searchable as text.

Install

From a release — download throughline.mcpb, then in Claude Desktop go to Settings → Extensions → Advanced settings → Install Extension. You'll be asked which directories the connector may read.

From source — see docs/INSTALL.md:

npm install
npm run grammars     # vendor tree-sitter WASM grammars
npm run build
npm run smoke -- .   # watch it index itself

Requires Claude Desktop on macOS or Windows. Node ships with Claude Desktop, so there's nothing else to install.

First run

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Throughline: common questions

Is Throughline MCP server safe?
Mostly: it is graded B (80/100). Read the Throughline safety report
Does Throughline need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Throughline maintained?
The last commit was 94 days ago (2026-08-02). The latest release is v1.0.1.