Is Codealive MCP safe to use?

Codealive MCP has an HVTrust score of 51.5/100 (Grade C), ranked #722 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Codealive MCP?

Codealive MCP scores 51.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 89 GitHub stars and is categorized under MCP Servers.

Codealive MCP

CodeAlive-AI/codealive-mcp

Context engine for large codebases, exposed through MCP. Gives AI coding agents precise repository context; benchmarked

MCP Servers Python Grade C Listed MIT

51.5/100

Rank #722 of 1320

Compare Codealive MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-08-16 · 19d ago

Recent change

Rank +5

Is Codealive MCP safe? Codealive MCP scores 51.5/100 (Grade C), ranked #722 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.7/10; 29% of recent commits are signed; last pushed 2026-08-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#365 Ckan MCP Server — 51.7 (C) → #366 Longbridge MCP — 51.6 (C) → #368 Meta Ads MCP — 51.5 (C) → #369 DollhouseMCP — 51.5 (C) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-04

Rank Moved

Rank dropped 15 spots (#707 → #722)

2026-09-03

Rank Moved

Rank dropped 51 spots (#656 → #707)

2026-09-02

Rank Moved

Rank dropped 24 spots (#632 → #656)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 5.7/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

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

Compare with another agent Get email alerts for Codealive MCP View MCP Servers Report missing data

46.4

Activity sub-score · out of 100

#367

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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-08-16

19 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼15

was #707

Analysis

HVTrust Dimensions vs MCP Servers

51.5 / 100 · 100.0% confidence

Codealive MCP MCP Servers average (778 agents)

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

8.6 / 25

0.9 below avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.5 above avg 11.8

Maintenance60% last-push freshness · 40% commit activity

13.1 / 20

0.9 above avg 12.2

AdoptionLog-scaled stars · package downloads

4.7 / 20

1.5 below avg 6.2

Activity Inputs

46.4 / 100

StarsRepository reach

11.7 / 30

FreshnessLast push recency

22.4 / 25

ActivityRecent commits

7.5 / 25

CommunityFork signal

4.7 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

5.7 / 10

OpenSSF Scorecard · scanned Sep 2, 2026

Signed Commits

29%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 6

SAST 6

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Is Codealive MCP safe?

Public trust evidence for Codealive MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Codealive MCP publish package provenance?

No published build provenance is currently detected for Codealive MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Codealive MCP have an OpenSSF Scorecard?

Codealive MCP has an OpenSSF Scorecard score of 5.7/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 Codealive MCP actively maintained?

Maintained. Last push was 19 days ago.

What license does Codealive MCP use?

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

Are Codealive MCP's commits signed?

28% of the last 100 commits to Codealive 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.

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

high confidence

Implemented

Codealive MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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

N/A

No package source configured

Detailed evidence is not shown in the public view.

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

Maintain Codealive MCP?

For maintainers

HVTrust scores Codealive 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-09-04

Rank Moved

Rank dropped 15 spots (#707 → #722)

2026-09-03

Rank Moved

Rank dropped 51 spots (#656 → #707)

2026-09-02

Rank Moved

Rank dropped 24 spots (#632 → #656)

2026-09-01

Rank Moved

Rank dropped 25 spots (#607 → #632)

2026-08-31

Rank Moved

Rank dropped 31 spots (#576 → #607)

2026-08-29

Rank Moved

Rank dropped 33 spots (#537 → #570)

2026-08-27

Rank Moved

Rank dropped 14 spots (#515 → #529)

2026-08-26

Scorecard Added

OSSF Scorecard: 5.7/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 519 spots (#1034 → #515)

2026-08-26

HVTrust Changed

HVTrust up 31.5pts (20.8 → 52.3)

2026-08-20

Rank Moved

Rank dropped 11 spots (#1024 → #1035)

2026-08-19

Rank Moved

Rank dropped 10 spots (#1014 → #1024)

2026-08-16

Rank Moved

Rank dropped 19 spots (#997 → #1016)

2026-08-14

Rank Moved

Rank dropped 22 spots (#977 → #999)

2026-08-13

Rank Moved

Rank dropped 11 spots (#966 → #977)

2026-08-10

Rank Moved

Rank dropped 57 spots (#916 → #973)

2026-08-08

Newly Listed

First tracked at rank #898

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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