chatcrystal

MCPattested
v0.6.1io.github.ZengLiangYiApache-2.0Updated 22d agonpmGitHub

Local-first AI PKM memory for coding conversations.

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.
898Downloads/wk
58GitHub stars
5Forks
22d agoLast update
Reads these credentials
  • CHATCRYSTAL_API_TOKENAPI keyoptional

    Optional token for a protected ChatCrystal Cloud or remote instance.

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
Authorio.github.ZengLiangYi
LicenseApache-2.0
Version0.6.1
Sourcenpm+mcp-registry
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 · a2a7297
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface7 tools · 1 privileged
Security scan✓ Cleanv0.5.5 · 4mo agoHow well does this scan work?
EvalsNone
IndexedJun 12, 2026

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

Tools

7 tools · 1 privileged
Statically extracted from the published packagev0.5.5 · 4mo 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_knowledgeNo description published

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

get_noteNo description published

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

list_notesNo description published

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

get_relationsNo description published

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

recall_for_taskNo description published

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

validate_task_memoryNo description published

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

write_task_memoryprivilegedNo description published

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

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

Local-first AI PKM memory for coding conversations.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.