Agentdb MCP Server

agentdb npm v3.0.0-alpha.20

Published by ruvnet — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Self-learning vector memory for AI agents — single-file .rvf cognitive container with HNSW search, episodic Reflexion memory, causal graph + Cypher, 9 RL algorithms, Thompson Sampling bandit, 41 MCP tools, hybrid (BM25 + dense) retrieval, GNN attention. 1

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 99 − adoption risk = 92/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 1.2 = 99. What the published surface and source actually contain:

PointsWhat was foundCategory
−1.2 Package runs install-time scripts MTC-SUP-010 supply-chain

2. Client adoption risk — 99 − 7 = 92. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 16

high Shell/command execution in server code (dist/src/cli/agentdb-cli.js)MTC-SRC-002

In the server's implementation (`dist/src/cli/agentdb-cli.js:1757`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: spawn } = await import('child_process'); const serverProcess = spawn('node', [mcpServerPath], { stdi

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/cli/agentdb-cli.js

high Shell/command execution in server code (dist/src/cli/commands/install-embeddings.js)MTC-SRC-002

In the server's implementation (`dist/src/cli/commands/install-embeddings.js:5`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ort { spawnSync } from 'child_process'; // Color codes for beautiful output const colors = { reset: '\x1b[0m', b

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/cli/commands/install-embeddings.js

high Shell/command execution in server code (dist/src/db-fallback.js)MTC-SRC-002

In the server's implementation (`dist/src/db-fallback.js:377`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: pper; } exec(sql) { return this.db.exec(sql); } save() { // Save

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/db-fallback.js

medium Hardcoded egress to an external endpoint (dist/src/controllers/EmbeddingService.js)MTC-SRC-003

In the server's implementation (`dist/src/controllers/EmbeddingService.js:214`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch('https://api.openai.com/v1/embeddings', { method: 'POST', headers:

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/controllers/EmbeddingService.js

medium Hardcoded egress to an external endpoint (dist/src/services/LLMRouter.js)MTC-SRC-003

In the server's implementation (`dist/src/services/LLMRouter.js:383`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const response = await fetch('https://openrouter.ai/api/v1/chat/completions', { method: 'POST',

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/services/LLMRouter.js

medium Dynamic module load from a non-literal (dist/src/backends/ruvector/RuVectorBackend.js)MTC-SRC-005

In the server's implementation (`dist/src/backends/ruvector/RuVectorBackend.js:303`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: mmapModule = await import(moduleName); } catch { // mmap-io not available,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/backends/ruvector/RuVectorBackend.js

medium Dynamic module load from a non-literal (dist/src/browser/HNSWIndex.js)MTC-SRC-005

In the server's implementation (`dist/src/browser/HNSWIndex.js:338`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: x from JSON */ import(json) { const data = JSON.parse(json); this.config = data.config;

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/browser/HNSWIndex.js

medium Dynamic module load from a non-literal (dist/src/cli/agentdb-cli.js)MTC-SRC-005

In the server's implementation (`dist/src/cli/agentdb-cli.js:1526`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: initScenario } = await import(runnerUrl); const subcommand = args[1]; if (!subcommand || subcom

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/cli/agentdb-cli.js

medium Dynamic module load from a non-literal (dist/src/cli/commands/doctor.js)MTC-SRC-005

In the server's implementation (`dist/src/cli/commands/doctor.js:152`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: try { require(mod.module); console.log(` ✅ ${mod.name} available`); passedChe

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/cli/commands/doctor.js

medium Dynamic module load from a non-literal (dist/src/cli/lib/config-manager.js)MTC-SRC-005

In the server's implementation (`dist/src/cli/lib/config-manager.js:498`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: SON string. */ import(json) { const config = JSON.parse(json); return this.validate(config);

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/cli/lib/config-manager.js

medium Dynamic module load from a non-literal (dist/src/cli/lib/report-store.js)MTC-SRC-005

In the server's implementation (`dist/src/cli/lib/report-store.js:392`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: JSON. */ async import(json) { const results = JSON.parse(json); const ids = []; for (co

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/cli/lib/report-store.js

medium Dynamic module load from a non-literal (dist/src/cli/lib/simulation-registry.js)MTC-SRC-005

In the server's implementation (`dist/src/cli/lib/simulation-registry.js:99`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const module = await import(filePath); const scenario = module.default || module;

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/cli/lib/simulation-registry.js

medium Dynamic module load from a non-literal (dist/src/cli/lib/simulation-runner.js)MTC-SRC-005

In the server's implementation (`dist/src/cli/lib/simulation-runner.js:107`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const module = await import(fullPath); return module.default || module; }

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/cli/lib/simulation-runner.js

medium Dynamic module load from a non-literal (dist/src/controllers/WASMVectorSearch.js)MTC-SRC-005

In the server's implementation (`dist/src/controllers/WASMVectorSearch.js:129`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: onst wasmModule = await import(normalizedPath); const ReasoningBankWasm = wasmModule.ReasoningBankWasm |

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/controllers/WASMVectorSearch.js

medium Dynamic module load from a non-literal (dist/src/optimizations/ToolCache.js)MTC-SRC-005

In the server's implementation (`dist/src/optimizations/ToolCache.js:211`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ersistence) */ import(entries) { const now = Date.now(); let imported = 0; for (const {

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/optimizations/ToolCache.js

low Package runs install-time scripts (postinstall)MTC-SUP-010

"agentdb" executes postinstall script(s) at install time. An install hook runs at install time; most are routine build/setup, but review what it does before trusting it.

Evidence: node scripts/postinstall.cjs || true

Fix: Review the scripts; install with --ignore-scripts where possible and vet what they do.

Location: package agentdb

Tools 35

Each tool and what it can reach — statically extracted from the published source.

  • agentdb_clear_cacheno sensitive capability
  • agentdb_deleteno sensitive capability
  • agentdb_delete_batchno sensitive capability
  • agentdb_initno sensitive capability
  • agentdb_insertno sensitive capability
  • agentdb_insert_batchno sensitive capability
  • agentdb_pattern_searchno sensitive capability
  • agentdb_pattern_statsno sensitive capability
  • agentdb_pattern_storeno sensitive capability
  • agentdb_pattern_store_batchno sensitive capability
Show 25 more tools ↓
  • agentdb_searchno sensitive capability
  • agentdb_statsno sensitive capability
  • causal_add_edgeno sensitive capability
  • causal_queryno sensitive capability
  • causal_traverseno sensitive capability
  • consolidate_nowno sensitive capability
  • db_statsno sensitive capability
  • experience_recordno sensitive capability
  • learner_discoverno sensitive capability
  • learning_end_sessionno sensitive capability
  • learning_explainno sensitive capability
  • learning_feedbackno sensitive capability
  • learning_metricsno sensitive capability
  • learning_predictno sensitive capability
  • learning_start_sessionno sensitive capability
  • learning_trainno sensitive capability
  • learning_transferno sensitive capability
  • recall_with_certificateno sensitive capability
  • reflexion_retrieveno sensitive capability
  • reflexion_storeno sensitive capability
  • reflexion_store_batchno sensitive capability
  • reward_signalno sensitive capability
  • skill_createno sensitive capability
  • skill_create_batchno sensitive capability
  • skill_searchno sensitive capability

What this scan could not see

Versions 2

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v3.0.0-alpha.20 latest A 92/100 16 1.13.0 2026-09-08
v3.0.0-alpha.18 A 92/100 16 1.12.1 2026-07-29

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/agentdb/badge.svg)](https://mcptrustchecker.com/registry/agentdb)
HTML
<a href="https://mcptrustchecker.com/registry/agentdb"><img src="https://mcptrustchecker.com/registry/agentdb/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/agentdb/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan agentdb --online

Use the free API → How scoring works

More in Developer Tools