klypix-mcp

MCPattested
v1.87.0io.github.dahshanlabsApache-2.0Updated 3d agonpmGitHub

Active state management for multi-agent coding: a shared, versioned project brain over MCP.

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.
459Downloads/wk
8GitHub stars
5Forks
3d agoLast update
Package
Authorio.github.dahshanlabs
LicenseApache-2.0
Version1.87.0
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 · 6d09c15
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface22 tools · none privileged
Security scan✓ Cleanv1.84.0 · 27d agoHow well does this scan work?
EvalsNone
IndexedAug 27, 2026

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

Tools

22 tools · none privileged
Statically extracted from the published packagev1.84.0 · 27d 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.

list_canvasesList all .klypix / .any canvas files in the vault, with card and connection counts.

List all .klypix / .any canvas files in the vault, with card and connection counts.

No input schema was published for this tool.

read_canvasRead a canvas as structured markdown (every card, the connection graph, [[wikilinks]], #tags) AND attach its image assets so you can SEE them, not just their filenames (capped: the first 8 images under ~5MB each — a bigger canvas returns the rest as filenames only). Pass the canvas TITLE directly (…

Read a canvas as structured markdown (every card, the connection graph, [[wikilinks]], #tags) AND attach its image assets so you can SEE them, not just their filenames (capped: the first 8 images under ~5MB each — a bigger canvas returns the rest as filenames only). Pass the canvas TITLE directly (…

No input schema was published for this tool.

search_canvasesSearch card text, titles, and #tags across every canvas in the vault. Returns the canvases and the matching cards.

Search card text, titles, and #tags across every canvas in the vault. Returns the canvases and the matching cards.

No input schema was published for this tool.

search_all_brainsNo description published

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

brain_askNo description published

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

project_map_contextNo description published

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

project_map_scanNo description published

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

project_map_driftNo description published

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

brain_challengeNo description published

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

brain_insightsStructural read of a brain.klypix: the most-connected "hub" cards (load-bearing decisions), orphaned decisions (no connections — maybe forgotten), stale open questions (aging & unresolved), and area sizes. Use to answer "what matters here / what am I forgetting / what should I review?" — read it at…

Structural read of a brain.klypix: the most-connected "hub" cards (load-bearing decisions), orphaned decisions (no connections — maybe forgotten), stale open questions (aging & unresolved), and area sizes. Use to answer "what matters here / what am I forgetting / what should I review?" — read it at…

No input schema was published for this tool.

brain_lensNo description published

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

brain_connectNo description published

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

brain_reconcileNo description published

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

brain_gardenNo description published

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

create_canvasCreate a new .klypix canvas from cards + connections and save it to the vault. The user opens it in the KLYPIX app (Canvas → Open). Prefer short, titled cards (one idea each) connected by meaningful arrows. For anything a person reads IN ORDER — steps, phases, checklists, sections — put the cards i…

Create a new .klypix canvas from cards + connections and save it to the vault. The user opens it in the KLYPIX app (Canvas → Open). Prefer short, titled cards (one idea each) connected by meaningful arrows. For anything a person reads IN ORDER — steps, phases, checklists, sections — put the cards i…

No input schema was published for this tool.

add_to_canvasAppend cards (and optional connections) to an existing v4 .klypix, preserving all existing items and their positions. New cards are placed to the right of the current content. Connections may reference new cards (by index/title) or existing cards (by title).

Append cards (and optional connections) to an existing v4 .klypix, preserving all existing items and their positions. New cards are placed to the right of the current content. Connections may reference new cards (by index/title) or existing cards (by title).

No input schema was published for this tool.

brain_noteNo description published

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

brain_messageNo description published

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

brain_message_receiptExplicit durable receipt for a coordination note already offered into model-visible context and acknowledged by a later independent action. Call only after the note has actually been incorporated into the receiving agent's work. Requires the exact message id and one-time offer token returned with t…

Explicit durable receipt for a coordination note already offered into model-visible context and acknowledged by a later independent action. Call only after the note has actually been incorporated into the receiving agent's work. Requires the exact message id and one-time offer token returned with t…

No input schema was published for this tool.

brain_syncNo description published

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

brain_doctorNo description published

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

canvas_viewNo description published

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

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

Active state management for multi-agent coding: a shared, versioned project brain over MCP.

Keywords
mcpmodel-context-protocolmulti-agentagent-coordinationproject-memoryproject-continuitycoding-agentcontext-engineeringa2aagent2agentagent-interoperabilitycanvasagentagent-memorylocal-firstklypixai
Alternatives
Comparing tool surfaces…

Dependency tree

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

60 packages resolved · 5 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

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

+49 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.

Topics

Related in memory & knowledge graphs