@nacre.work/mcp

MCPattested
v0.26.7NacreApache-2.0Updated 1d agonpmGitHub

Nacre MCP server: Streamable HTTP and STDIO

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.
105Downloads/wk
1GitHub stars
1d agoLast update
Needs 1 credential before it runs
  • NACRE_SERVICE_KEYAPI keyrequired

    Service-account key for STDIO mode. The server also needs the deployment's full environment (database and backend configuration) - see docs/mcp.md; the key alone is not enough to start it.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorNacre
LicenseApache-2.0
Version0.26.7
Sourcenpm+mcp-registry
npm@nacre.work/mcp
GitHubnacre-work/nacre
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 · 7202696
Dependencies✓ 21 resolved+ · none vulnerable
Tool surface6 tools · 1 privileged
Security scan✓ Cleanv0.26.7 · todayHow well does this scan work?
EvalsNone
IndexedSep 26, 2026

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

Tools

6 tools · 1 privileged
Statically extracted from the published packagev0.26.7 · 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.

searchNatural-language query

Natural-language query

No input schema was published for this tool.

list_layersThe layers you can read, with descriptions and document counts.

The layers you can read, with descriptions and document counts.

No input schema was published for this tool.

get_documentFetch one document by id, or by external_id within a layer: its title, layer, status and

Fetch one document by id, or by external_id within a layer: its title, layer, status and

No input schema was published for this tool.

ingest_statusNo description published

This tool published no description. Forge does not invent one.

ingest_documentNo description published

This tool published no description. Forge does not invent one.

delete_documentprivilegedDelete a document: it leaves search results immediately and its vectors are reclaimed

Delete a document: it leaves search results immediately and its vectors are reclaimed

No input schema was published for this tool.

4 of 6 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

Nacre MCP server: Streamable HTTP and STDIO

Keywords
nacremcpmodel-context-protocolagentsragpermissionsself-hosted
Alternatives
Comparing tool surfaces…

Tools exposed

6 tools · 1 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-26 — observed resolution, not a publisher declaration.

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

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

Declared but not resolved

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

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

Topics

Related in rag & embeddings