@jagilber-org/index-server

MCPattested
v1.42.4io.github.jagilber-orgMITUpdated 2d agonpmGitHub

MCP instruction indexing server with search, CRUD, validation, and cross-repo knowledge promotion.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
25Downloads/wk
2d agoLast update
Package
Authorio.github.jagilber-org
LicenseMIT
Version1.42.4
Sourcenpm+mcp-registry
npm@jagilber-org/index-server
GitHubjagilber-org/index-server
SBOMCycloneDX 1.6 ↓
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 17e38d7
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface8 tools · none privileged
Security scan✓ Cleanv1.42.4 · todayHow well does this scan work?
EvalsNone
IndexedSep 16, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · none privileged
Statically extracted from the published packagev1.42.4 · 8h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

quickstartInstall, configure, and verify Index Server with the MCP-native flow.

Install, configure, and verify Index Server with the MCP-native flow.

No input schema was published for this tool.

client-configConfig file formats and best practices for VS Code, Copilot CLI, and Claude Desktop.

Config file formats and best practices for VS Code, Copilot CLI, and Claude Desktop.

No input schema was published for this tool.

verificationChecklist for verifying the MCP connection and diagnosing common setup issues.

Checklist for verifying the MCP connection and diagnosing common setup issues.

No input schema was published for this tool.

setup_index_serverGuide an MCP-native Index Server install and initial configuration.

Guide an MCP-native Index Server install and initial configuration.

No input schema was published for this tool.

clientOptional target client such as vscode, copilot-cli, or claude.

Optional target client such as vscode, copilot-cli, or claude.

No input schema was published for this tool.

configure_index_serverExplain the right config file shape and key settings for a target client.

Explain the right config file shape and key settings for a target client.

No input schema was published for this tool.

verify_index_serverWalk through verification and troubleshooting for setup or connection issues.

Walk through verification and troubleshooting for setup or connection issues.

No input schema was published for this tool.

symptomOptional short problem statement to tailor the checklist.

Optional short problem statement to tailor the checklist.

No input schema was published for this tool.

8 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP instruction indexing server with search, CRUD, validation, and cross-repo knowledge promotion.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

8 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-17 — observed resolution, not a publisher declaration.

60 packages resolved · 14 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

131 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+119 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.