citepath

Name: citepath
Author: io.github.arif-js

MCPattested

v0.1.4io.github.arif-jsMITUpdated 2d agonpm GitHub

Self-hosted search over your documentation, with citations, for AI assistants and apps

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.

172Downloads/wk

2d agoLast update

Package

Authorio.github.arif-js

LicenseMIT

Version0.1.4

Sourcenpm+mcp-registry

npmcitepath

GitHubarif-js/citepath

SBOMCycloneDX 1.6 ↓

Trust Status

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 · 15aeadd

Dependencies✓ 60 resolved+ · none vulnerable

Tool surface3 tools · none privileged

Security scan✓ Cleanv0.1.4 · todayHow well does this scan work?

EvalsNone

IndexedOct 17, 2026

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

Tools

3 tools · none privileged

Statically extracted from the published packagev0.1.4 · 23h 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.

search_passagesStart here: full-text search over the documentation indexed on this machine. Returns ranked

Start here: full-text search over the documentation indexed on this machine. Returns ranked

No input schema was published for this tool.

get_passageReads one passage in full by its ID, after search_passages has found it. Use it when a search result was

Reads one passage in full by its ID, after search_passages has found it. Use it when a search result was

No input schema was published for this tool.

list_sourcesLists the configured documentation sources: id, name, type, document and passage counts, and the

Lists the configured documentation sources: id, name, type, document and passage counts, and the

No input schema was published for this tool.

3 of 3 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

Self-hosted search over your documentation, with citations, for AI assistants and apps

Keywords

mcpmodel-context-protocoldocumentationsearchretrievalragcitationssqlitefts5claudecursorself-hostedcli

Alternatives

Comparing tool surfaces…

Dependency tree

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

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

zod4.6.7
ignore7.0.13
undici7.30.1
cheerio1.2.011 dependencies
- parse57.3.0+1 not drawn
- undici7.30.1shown above
- domutils3.2.2+1 not drawn2 dependencies
  - domhandler5.0.3+1 not drawn
  - dom-serializer2.0.0+1 not drawn2 dependencies
    entities4.5.0
    domhandler5.0.3shown above+1 not drawn
- domhandler5.0.3shown above+1 not drawn
- htmlparser210.1.0+2 not drawn2 dependencies
  - domutils3.2.2shown above+1 not drawn
  - domhandler5.0.3shown above+1 not drawn
- cheerio-select2.1.0+4 not drawn2 dependencies
  - domutils3.2.2shown above+1 not drawn
  - domhandler5.0.3shown above+1 not drawn
- dom-serializer2.0.0shown above+1 not drawn
- whatwg-mimetype4.0.0
- encoding-sniffer0.2.1+2 not drawn
- parse5-parser-stream7.1.21 dependency
  - parse57.3.0shown above+1 not drawn
- parse5-htmlparser2-tree-adapter7.1.02 dependencies
  - parse57.3.0shown above+1 not drawn
  - domhandler5.0.3shown above+1 not drawn
picomatch4.0.7
markdown-it14.3.36 dependencies
- mdurl2.1.0
- argparse2.0.1
- entities4.5.0shown above
- uc.micro2.1.0
- linkify-it5.0.21 dependency
  - uc.micro2.1.0shown above
- punycode.js2.3.1
robots-parser3.0.1
@modelcontextprotocol/sdk1.32.1+16 not drawn1 dependency
- zod4.6.7shown above

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

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

package cap reached: 54

fresh ^2.0.0 — required by express@5.3.0package cap reached
cookie ^0.7.1 — required by express@5.3.0package cap reached
router ^2.2.0 — required by express@5.3.0package cap reached
accepts ^2.0.0 — required by express@5.3.0package cap reached
type-is ^2.1.0 — required by express@5.3.0package cap reached
parseurl ^1.3.3 — required by express@5.3.0package cap reached
statuses ^2.0.1 — required by express@5.3.0package cap reached
encodeurl ^2.0.0 — required by express@5.3.0package cap reached
mime-types ^3.0.0 — required by express@5.3.0package cap reached
proxy-addr ^2.0.8 — required by express@5.3.0package cap reached
body-parser ^2.3.0 — required by express@5.3.0package cap reached
escape-html ^1.0.3 — required by express@5.3.0package cap reached

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

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

citepath

Tools

Tools exposed

Dependency tree

Declared but not resolved

Topics

Related in search & retrieval