io.github.Sisuthros/claude-amplifier

MCPcommunity
v1.5.3io.github.SisuthrosUnknownUpdated 4mo agonpmGitHub

Persistent memory + decision tracking for Claude across sessions. Local SQLite, no cloud.

[]( Persistent memory for Claude that doesn't lie to itself. Write-verification, stale-memory detection, Pattern Oracle, verification-gated lessons — so unverified guesses can't quietly become "memories" Claude treats as facts, and so fake "id: 1fd61c52af06f2bd" success messages can't paper over silent failures. A week ago, Claude told me an agent runtime config was broken because the model name…

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.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorio.github.Sisuthros
LicenseUnknown
Version1.5.3
Sourcemcp-registry
npmclaude-amplifier
GitHubSisuthros/claude-amplifier
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—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)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface13 tools · none privileged
Security scan✓ Cleanv1.5.3 · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

13 tools · none privileged
Statically extracted from the published packagev1.5.3 · 3mo 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.

amplify_learnNo description published

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

amplify_decisionsNo description published

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

amplify_context_loadNo description published

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

amplify_link_decisionsNo description published

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

amplify_global_patternsNo description published

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

amplify_preflightNo description published

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

amplify_record_claimNo description published

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

amplify_verify_claimNo description published

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

amplify_promote_patternNo description published

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

amplify_evidence_chainNo description published

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

amplify_promote_from_memory_mdNo description published

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

amplify_suggest_pattern_keyNo description published

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

amplify_audit_freshnessNo description published

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

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

[]( Persistent memory for Claude that doesn't lie to itself. Write-verification, stale-memory detection, Pattern Oracle, verification-gated lessons — so unverified guesses can't quietly become "memories" Claude treats as facts, and so fake "id: 1fd61c52af06f2bd" success messages can't paper over silent failures. A week ago, Claude told me an agent runtime config was broken because the model name had another provider's prefix substring in it. The fix worked. I let Claude write that down as a…

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

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

No dependency coverage

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