fleet-memory-mcp

MCPattested
v0.1.0UnknownMITUpdated 29d agonpmGitHub

RCLL — self-hosted, hierarchical shared memory for a team of AI agents over MCP (rooms, L0-L3 depth, pgvector). Fork of vectorize-io/hindsight.

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.
29d agoLast update
Package
AuthorUnknown
LicenseMIT
Version0.1.0
Sourcenpm+mcp-registry
npmfleet-memory-mcp
GitHubHoletron-lab/fleet-memory
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 · 77ea122
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface5 tools · none privileged
Security scan✓ Cleanv0.1.0 · todayHow well does this scan work?
EvalsNone
IndexedAug 28, 2026

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

Tools

5 tools · none privileged
Statically extracted from the published packagev0.1.0 · 20h 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.

memory_retainSave a fact, observation, or document to long-term memory with automatic room/hall classification.

Save a fact, observation, or document to long-term memory with automatic room/hall classification.

No input schema was published for this tool.

memory_recallSearch long-term memory for relevant facts. Uses semantic search with optional room/hall scoping

Search long-term memory for relevant facts. Uses semantic search with optional room/hall scoping

No input schema was published for this tool.

memory_reflectDeep reasoning over memory — synthesizes facts, finds patterns, answers complex questions with citations.

Deep reasoning over memory — synthesizes facts, finds patterns, answers complex questions with citations.

No input schema was published for this tool.

memory_compressCreate compressed memory summaries (closets) from stored facts. Groups memories by room+hall

Create compressed memory summaries (closets) from stored facts. Groups memories by room+hall

No input schema was published for this tool.

memory_bridgeCreate a cross-bank memory bridge (tunnel) between two related memories in different banks.

Create a cross-bank memory bridge (tunnel) between two related memories in different banks.

No input schema was published for this tool.

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

RCLL — self-hosted, hierarchical shared memory for a team of AI agents over MCP (rooms, L0-L3 depth, pgvector). Fork of vectorize-io/hindsight.

Keywords
mcpmemoryrcllfleet-memoryhindsightai-agentsmulti-agentpgvectorlong-term-memoryself-hostedmodel-context-protocol
Alternatives
Comparing tool surfaces…

Tools exposed

5 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-26 — observed resolution, not a publisher declaration.

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

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

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

+41 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