Is Codebase Memory MCP safe to use?

Codebase Memory MCP has an HVTrust score of 91.6/100 (Grade A), ranked #8 of 1308 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Codebase Memory MCP?

Codebase Memory MCP scores 91.6/100 on HVTracker's evidence-weighted HVTrust scale. It has 39.5k GitHub stars and is categorized under MCP Servers.

Codebase Memory MCP

DeusData/codebase-memory-mcp

High-performance code intelligence MCP server. Indexes codebases into a persistent knowledge graph — average repo in mil

MCP Servers C Grade A Listed MIT

91.6/100

Rank #8 of 1308

Compare Codebase Memory MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-19 · 0d ago

Recent change

No recent signal change

Is Codebase Memory MCP safe? Codebase Memory MCP scores 91.6/100 (Grade A), ranked #8 of 1308 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 7.9/10; 30% of recent commits are signed; last pushed 2026-08-19. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#2 Playwright MCP — 89.5 (A) → #3 Apify MCP Server — 87.4 (A) → #4 Stripe Agent Toolkit — 85.4 (A) → #5 XcodeBuildMCP — 84.9 (A) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Maintainer Checklist

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with Playwright MCP Get email alerts for Codebase Memory MCP View MCP Servers Report missing data

93.9

Activity sub-score · out of 100

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade A reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-08-19

Activity & Reach

Stars

39.5k

Forks

3.2k

Last Push

2026-08-19

today

Commits (4 wk)

705

Downloads (7d)

4,528

npm

HN mentions (30d)

—

Open Issues

366

Rank Change

was #8

Analysis

HVTrust Dimensions vs MCP Servers

91.6 / 100 · 100.0% confidence

Codebase Memory MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.9 / 25

13.9 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above avg 13.3

Transparency50% declared license · 50% OSSF Scorecard

15.2 / 17

6.4 above avg 8.8

Maintenance60% last-push freshness · 40% commit activity

20.0 / 20

7.6 above avg 12.4

AdoptionLog-scaled stars · package downloads

15.9 / 20

10.1 above avg 5.8

Activity Inputs

93.9 / 100

StarsRepository reach

27.6 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

25 / 25

CommunityFork signal

16.3 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

7.9 / 10

OpenSSF Scorecard · scanned Aug 19, 2026

Signed Commits

30%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 8

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 9

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 10

Vulnerabilities 10

Is Codebase Memory MCP safe?

Public supply-chain signals for Codebase Memory MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Codebase Memory MCP carries less obvious unverified-evidence risk than projects with thin signals.

Does Codebase Memory MCP publish package provenance?

Yes. Codebase Memory MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Codebase Memory MCP have an OpenSSF Scorecard?

Codebase Memory MCP has an OpenSSF Scorecard score of 7.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Codebase Memory MCP actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Codebase Memory MCP use?

Codebase Memory MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Codebase Memory MCP's commits signed?

30% of the last 100 commits to Codebase Memory MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

Compare Codebase Memory MCP head-to-head

Codebase Memory MCP vs Playwright MCP → Codebase Memory MCP vs Apify MCP Server → Codebase Memory MCP vs Stripe Agent Toolkit →

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

medium confidence

Implemented

Codebase Memory MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Codebase Memory MCP?

For maintainers

HVTrust scores Codebase Memory MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-07-14

Newly Listed

First tracked at rank #8

GitHub → PyPI: codebase-memory-mcp npm: codebase-memory-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/codebase-memory-mcp.svg)](https://hvtracker.net/agents/codebase-memory-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/codebase-memory-mcp"><img src="https://hvtracker.net/badge/codebase-memory-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON