Is io.github.Sisuthros/claude-amplifier safe to use?

io.github.Sisuthros/claude-amplifier has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.Sisuthros/claude-amplifier?

io.github.Sisuthros/claude-amplifier supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.Sisuthros/claude-amplifier do?

io.github.Sisuthros/claude-amplifier provides 6 tools: amplify_decisions, FAQ, Roadmap, Configuration, Contributing and 1 more. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.Sisuthros/claude-amplifier?

io.github.Sisuthros/claude-amplifier is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is io.github.Sisuthros/claude-amplifier actively maintained?

io.github.Sisuthros/claude-amplifier is actively maintained — last commit was 6 days ago. It has 1 GitHub stars.

io.github.Sisuthros/claude-amplifier

claude-amplifier

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

1 6 tools GitHub npm

No known CVEs

No license

Actively maintained

Last commit 6d ago

Works with most clients

Transport: stdio, sse, http

6 tools · ~197 tok

Grade A · 0.1% of 200K ctx

Edit this pageView history

AI / ML Data

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "claude-amplifier": {
      "args": [
        "mcp"
      ],
      "type": "stdio",
      "command": "claude-amplifier"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-sisuthros-claude-amplifier)](https://mcppedia.org/s/io-github-sisuthros-claude-amplifier)

Read me

What io.github.Sisuthros/claude-amplifier does

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.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'claude-amplifier' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

89/100across 5 weighted dimensions

How we score →

0255075100

−11

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked claude-amplifier against OSV.dev.

Inventory

Tools (6)

Click any tool to inspect its schema.

~197 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.Sisuthros/claude-amplifier safe to use?: io.github.Sisuthros/claude-amplifier has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.Sisuthros/claude-amplifier?: io.github.Sisuthros/claude-amplifier supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.Sisuthros/claude-amplifier do?: io.github.Sisuthros/claude-amplifier provides 6 tools: amplify_decisions, FAQ, Roadmap, Configuration, Contributing and 1 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.Sisuthros/claude-amplifier?: io.github.Sisuthros/claude-amplifier is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.Sisuthros/claude-amplifier actively maintained?: io.github.Sisuthros/claude-amplifier is actively maintained — last commit was 6 days ago. It has 1 GitHub stars.

Similar servers

Others in ai-ml / data

View all →

PostgreSQL MCP Server98

Query and manage PostgreSQL databases directly from AI assistants

87.9k 1

Sequential Thinking MCP Server98

Dynamic problem-solving through sequential thought chains

87.9k 1

Memory MCP Server98

Persistent memory using a knowledge graph

87.9k 5

Supabase MCP Server97

Manage Supabase projects — databases, auth, storage, and edge functions

2.8k 4

MCP Security Weekly

Get CVE alerts and security updates for io.github.Sisuthros/claude-amplifier and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

AI / ML Data

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "claude-amplifier": {
      "args": [
        "mcp"
      ],
      "type": "stdio",
      "command": "claude-amplifier"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-sisuthros-claude-amplifier)](https://mcppedia.org/s/io-github-sisuthros-claude-amplifier)

Read me

What io.github.Sisuthros/claude-amplifier does

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.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'claude-amplifier' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

Claude Amplifier

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 real five-minute story (v1.4.0 origin)

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

A week later — different session, different model, similar config — Claude "remembered" the fix and applied it again. Except the real problem this time was a TPM cap. Claude never tested its theory; it just trusted last week's confidently-recorded fix. I lost two hours.

That's the bug. It's filed as anthropics/claude-code#27430. It happens to everyone who lets Claude keep notes across sessions. An inference becomes a memory. The memory becomes a "fact." The fact never gets verified.

A second five-minute story (v1.5.0 origin)

A different session, weeks later. Claude reported back: "Decision recorded (id: 1fd61c52af06f2bd). Lesson recorded (id: 04371350ec263822)." Five decisions, eight lessons, all with crisp hex IDs. Felt great.

Next morning, I asked Claude to recall any of them. None existed. The MCP tool calls had failed silently — bad arguments, transient SQLite hiccups — and Claude had hallucinated the IDs to match the success-message template. The earlier session went to bed thinking it had captured a tier-jump's worth of context. Reality: the database was untouched.

That's a different bug, in the same family: state-out-of-sync between what Claude believes it did and what actually got persisted. Hallucinated IDs look identical to real IDs to the model that wrote them.

Claude Amplifier v1.5.0 fixes this structurally too. Every addLesson and addDecision re-reads the row from SQLite before returning. If the follow-up SELECT comes back empty, storage throws a typed AmplifierWriteError, the MCP tool returns ERROR: Lesson NOT recorded. Do not claim this was saved., and an audit line lands in ~/.claude-amplifier/write-errors.jsonl. The "I saved it!" lie is no longer possible.

amplify_context_load now also warns when ~/.claude/memory/<YYYY-MM-DD>.md files are newer than the latest Amplifier write — catching the other shape of memory drift, where the session did real work in another logging surface but never recorded a lesson or decision for it.

Both bugs share a shape: Claude lies confidently about its own state. Verification-gated memory (v1.4.0) catches it on the content side. Write-verification + stale-memory detection (v1.5.0) catches it on the storage side. Pattern Oracle (v1.4.0) keeps using the now-trustworthy memory to warn before the next mistake.

Claude Amplifier (v1.5.1) treats every lesson as living at one of three statuses:

claim (0.5 confidence)   →   evidence (0.7)   →   confirmed (1.0)

A guess starts as a claim and weighs 5× less than a confirmed lesson when the Pattern Oracle scores risk. To promote, you attach evidence: git_commit, test_run, user_confirmation, external_doc, manual_review. Two distinct

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

89/100across 5 weighted dimensions

How we score →

0255075100

−11

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked claude-amplifier against OSV.dev.

Inventory

Tools (6)

Click any tool to inspect its schema.

~197 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.Sisuthros/claude-amplifier safe to use?: io.github.Sisuthros/claude-amplifier has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.Sisuthros/claude-amplifier?: io.github.Sisuthros/claude-amplifier supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.Sisuthros/claude-amplifier do?: io.github.Sisuthros/claude-amplifier provides 6 tools: amplify_decisions, FAQ, Roadmap, Configuration, Contributing and 1 more. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.Sisuthros/claude-amplifier?: io.github.Sisuthros/claude-amplifier is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.Sisuthros/claude-amplifier actively maintained?: io.github.Sisuthros/claude-amplifier is actively maintained — last commit was 6 days ago. It has 1 GitHub stars.