Skip to content

MCP servers › io.github.sfy257000 › local-codebase-indexer

MCP server · registry snapshot 2026-11-13 · last checked 2026-11-13

local-codebase-indexer MCP server

Registry name io.github.sfy257000/local-codebase-indexer

by sfy257000 · GitHub account (the registry's namespace rule)repository: same ownerSource ↗PyPI ↗

Trace SQL Server tables to C# callers and Razor pages locally; MCP server and CLI. — the publisher's description

7 of 8 record checks metversion 0.9.1PythonMITstandard input/output

Summary

io.github.sfy257000/local-codebase-indexer is a local MCP server listed in the official MCP registry at version 0.9.1, under the namespace of the GitHub account sfy257000. Its linked repository, github.com/sfy257000/local-codebase-indexer, belongs to the same GitHub account.

Record checks

7 of 8 record checks met · 1 does not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • met: No known critical or high advisory in the package or its dependencies
  • #2,744 of 20,610 packages by monthly downloads, tied with 5 others
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
PyPI · listed version current
License
MIT
Dependencies
no known high or critical advisories
Repository
public
Last tested
not tested

Tool list

Not read: It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
0.9.1, published 2026-11-13 (registry, as of the 2026-11-13 snapshot)
First listed version
2026-11-09 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, 2026-11-09 to 2026-11-13; 3 in the 90 days before the 2026-11-13 snapshot.
Most recent 3 versions
  • 0.9.1 · 2026-11-13
  • 0.9.0 · 2026-11-10
  • 0.8.0 · 2026-11-09
(versions still listed in the registry only)
Registry data
snapshot 2026-11-13
Package and repository
checked 2026-11-13

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 0.9.0 (published 2026-11-10) → 0.9.1 (published 2026-11-13), between the registry lists of 2026-11-12 and 2026-11-13.

The publisher’s GitHub release note for v0.9.1 (“0.9.1 — SQL provenance fixes and reproducible tool comparisons”), published 2026-11-13.

Read the release note (the publisher’s text, shown as plain text)
This patch release corrects SQL access attribution and adds reproducible comparisons explaining when Local Codebase Indexer helps with SQL Server / C# maintenance.

### Correctness fixes

- Limit `sp_executesql` analysis to its SQL argument and statement, including quoted procedure names. Unrelated literals, parameter values, and similarly named columns no longer create false accesses.
- Scope CTE names and UPDATE/DELETE aliases to their consuming statement, including omitted semicolons and UNION / INSERT SELECT patterns.
- Recognize GO only as a batch separator line, preserving comma-joined sources after predicates such as `a.go = b.id`.
- Keep SQL object definitions and suggestions restricted to SQL source files; application functions retain normal symbol navigation.
- Respect C# / VB6 parameter and local shadowing, invalidate overwritten SQL bindings, and avoid treating query-parameter strings as executed SQL. Preserve earlier valid execution evidence.

### Reproducible tool comparisons

English, Traditional Chinese, and Simplified Chinese READMEs now include measured results, trade-offs, and links to all raw query records. A new optional runner compares the unchanged retrieval questions with actual ripgrep candidate search plus standard BM25 ranking.

| Retrieval suite | rg + BM25 file Recall@5 | Indexer | Difference |
|---|---:|---:|---:|
| MES-style synthetic, 42 questions | 81.0% | 91.7% | +10.7 percentage points |
| Same questions with distractors | 81.0% | 90.5% | +9.5 percentage points |
| Python standard library, 12 questions | 100.0% | 79.2% | -20.8 percentage points |

The indexer retains its default 5 result chunks; the baseline returns 5 files. Both are scored at file level. These are 54 unique project-authored questions and 96 executions including the repeated noisy suite, not independent production-accuracy measurements.

- In the separate bundled synthetic navigation task, required evidence-file coverage increases from 3/5 to 5/5 (60% to 100%) versus one literal table-name search. Controller reachability remains `probable`, not runtime proof.
- On noisy/stdlib retrieval suites, rendered output uses 94.9% / 96.9% fewer Unicode characters than full reads of the same selected files. Tiny synthetic files produce 2.3% more characters. These are not measured Claude-token savings or reductions against Grep snippets.
- Richer navigation costs more time: recorded warm CLI medians are 244.5 ms versus 8.3 ms for a literal rg call, with 266.1 ms for the initial indexer call including indexing. Timings are machine-specific.
- Serena and Claude Context features are documented with pinned upstream sources; no end-to-end Claude, Serena, or Claude Context superiority claim is made.

See the [protocol](https://github.com/sfy257000/local-codebase-indexer/blob/v0.9.1/docs/tool-comparison.md), [recorded summary](https://github.com/sfy257000/local-codebase-indexer/blob/v0.9.1/benchmarks/tool-comparison.json), and [all 96 query records](https://github.com/sfy257000/local-codebase-indexer/blob/v0.9.1/benchmarks/tool-comparison-queries.jsonl). Recorded measurements retain their pre-release package-version label and source fingerprint.

### Upgrade

```bash
python -m pip install --upgrade local-codebase-indexer==0.9.1
```

Index format increases from 9 to 10. The first index update automatically rebuilds older parsed data; existing projects do not need to delete their index manually.

### Validation

187 tests pass, including 33 SQL/binding regressions and 7 benchmark-protocol tests added since 0.9.0. CI covers Linux and Windows on Python 3.10, 3.12, and 3.13, plus lint/type checks, installed-package validation, project evaluation, and comparison smoke runs. Retrieval questions, gold answers, and thresholds were not changed.

Changes: #4 and #5. [Full changelog](https://github.com/sfy257000/local-codebase-indexer/compare/v0.9.0...v0.9.1).

The release on GitHub

Source: the official MCP Registry list on 2026-11-12 and on 2026-11-13; release notes from the GitHub Releases API, checked 2026-11-13.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: the required option --root has no value in the entry, and it is not stated whether it takes one.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.9.1
Latest stable
0.9.1
Status
current
Withdrawn
no

Source: pypi.org · 2026-11-13. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-11-13 (OSV.dev; each bar counts advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha256-c0f50e77703728836…
License
MIT

Source: the package registry · 2026-11-13.

Usage

Downloads
1,308 in the last month

Source: pypistats.org · 2026-11-13.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-13.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-13. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-13. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-13. Source: read 2026-11-13.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-13. Source: read 2026-11-13.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Version 0.9.1 on PyPIExists and can be installedmatchesPyPI · 2026-11-13
Repository github.com/sfy257000/local-codebase-indexerOpens publiclymatchesapi.github.com · 2026-11-13

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.sfy257000
GitHub owner
a personal account (sfy257000)
Repository
github.com/sfy257000/local-codebase-indexer
Stars
0
Repository age
91–180 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-13; security policy read from GitHub · 2026-11-09.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

7 of 8 record checks met · 1 does not apply

  • #2,744 of 20,610 packages by monthly downloads, tied with 5 others
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-13 (security policy 2026-11-09). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.sfy257000/local-codebase-indexer

Answered from the data above

Who publishes io.github.sfy257000/local-codebase-indexer?

The registry ties the namespace io.github.sfy257000 to the GitHub account sfy257000; only its owner can publish under it. Its linked repository, github.com/sfy257000/local-codebase-indexer, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.sfy257000/local-codebase-indexer safe to install?

We do not rate servers as safe or unsafe. 7 of its 8 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.sfy257000/local-codebase-indexer been security tested?

No. It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it.

Does io.github.sfy257000/local-codebase-indexer publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Is the listed version current?

Yes. The registry lists 0.9.1, the latest stable release on PyPI.

Where is the source code of io.github.sfy257000/local-codebase-indexer?

In github.com/sfy257000/local-codebase-indexer, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

It requires a setting the publisher marks as required (for example a URL part or a configuration value) that has no default, so we did not start it. — the server's own choice

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-13; not classified yet
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
api.github.com · 2026-11-13
Hosting type
registry · 2026-11-13
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-13
Required credentials
none declared
registry · 2026-11-13 · no declaration is not a guarantee
Package registry
registry · 2026-11-13
Freshness
0–30 days
registry updatedAt · 2026-11-13
Lifecycle status
registry · 2026-11-13
License class
package registry · 2026-11-13
Integrity hash
declared (sha256)
package registry · 2026-11-13
Signature / provenance
does not apply
PyPI publishes no registry signature or attestation equivalent to npm dist.signatures
Dependency advisories
none known
OSV.dev · 2026-11-13
Popularity
1,308 downloads a month
package registry · 2026-11-13
Publisher signals
owner: a personal account · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-11-13
Maintenance
api.github.com · 2026-11-13
Environment
your machine
where it runs, from the hosting type · 2026-11-13

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.sfy257000/local-codebase-indexer: MCP server record.” Data checked 2026-11-13. https://protocolprobe.com/mcp/servers/io.github.sfy257000/local-codebase-indexer

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 7 of 8 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.sfy257000/local-codebase-indexer)](https://protocolprobe.com/mcp/servers/io.github.sfy257000/local-codebase-indexer)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology