@seanhogg/builderforce-memory-mcp

MCPattested
v2026.9.33Sean HoggMITUpdated 4d agonpmGitHub

BuilderForce Agent Memory — MCP transport. Exposes @seanhogg/builderforce-memory to any MCP client (Claude Agent SDK in-process, stdio, or HTTP) over a pluggable MemoryBackend, with token-saving fetch-on-demand recall.

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.
735Downloads/wk
2GitHub stars
4d agoLast update
Reads these credentials
  • BUILDERFORCE_API_KEYAPI keyoptional

    Builderforce tenant API key (bfk_*). When set, additionally exposes the token_usage and model_efficiency cost tools.

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
AuthorSean Hogg
LicenseMIT
Version2026.9.33
Sourcenpm+mcp-registry
npm@seanhogg/builderforce-memory-mcp
GitHubSeanHogg/builderforce-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 · ffe2864
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface8 tools · none privileged
Security scan✓ Cleanv2026.9.32 · 4d agoHow well does this scan work?
EvalsNone
IndexedSep 28, 2026

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

Tools

8 tools · none privileged
Statically extracted from the published packagev2026.9.32 · 4d 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.

token_usageCurrent token spend + budget for the workspace (today).

Current token spend + budget for the workspace (today).

No input schema was published for this tool.

model_efficiencyWhich models performed best/cheapest for this workspace's recent work.

Which models performed best/cheapest for this workspace's recent work.

No input schema was published for this tool.

memory_recallSemantically recall the most relevant stored memories for a query.

Semantically recall the most relevant stored memories for a query.

No input schema was published for this tool.

memory_getFetch a single memory by its exact key. Use when you already know the key

Fetch a single memory by its exact key. Use when you already know the key

No input schema was published for this tool.

memory_recall_by_tagList memories carrying a given tag (e.g. 'user', 'project', 'decision').

List memories carrying a given tag (e.g. 'user', 'project', 'decision').

No input schema was published for this tool.

memory_rememberPersist a fact for future sessions. Call when you learn something durable and reusable:

Persist a fact for future sessions. Call when you learn something durable and reusable:

No input schema was published for this tool.

memory_compactShrink memories that have already been absorbed elsewhere (folded into a model,

Shrink memories that have already been absorbed elsewhere (folded into a model,

No input schema was published for this tool.

memory_forgetDelete a memory by key. Use to remove a fact that is now wrong or obsolete.

Delete a memory by key. Use to remove a fact that is now wrong or obsolete.

No input schema was published for this tool.

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

BuilderForce Agent Memory — MCP transport. Exposes @seanhogg/builderforce-memory to any MCP client (Claude Agent SDK in-process, stdio, or HTTP) over a pluggable MemoryBackend, with token-saving fetch-on-demand recall.

Keywords
mcpmodel-context-protocolclaude-agent-sdkagent-memoryssmbuilderforcetypescript
Alternatives
Comparing tool surfaces…

Tools exposed

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

60 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.

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.

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

Topics

Related in memory & knowledge graphs