updated 2026-08-12 05:02 UTC

Codex MCP Go

w31r4/codex-mcp-go

codex-mcp-go is a Go-based MCP (Model Context Protocol) server that serves as a bridge for Codex CLI, enabling various A

MCP Servers Go Grade D Listed MIT
30.5/100
Rank #760 of 1283
Compare Codex MCP Go

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-02-03 · 190d ago
Recent change
Rank +1

Is Codex MCP Go safe? Codex MCP Go scores 30.5/100 (Grade D), ranked #760 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; no OSSF Scorecard result yet; 1% of recent commits are signed; last pushed 2026-02-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#353 Google Health Fitbit MCP — 30.8 (D) → #354 iMessage MCP — 30.5 (D) → #356 Word MCP Live — 30.3 (D) → #357 Openevidence MCP — 30.2 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 41 spots (#720 → #761)
2026-08-08
Newly Listed
First tracked at rank #721
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 190 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Codex MCP Go View MCP Servers Report missing data
13.6
Activity sub-score · out of 100
#355
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 D 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 →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 190 days ago — may be stale

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
52
Forks
4
Last Push
2026-02-03
190 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
▲1
was #761

Analysis

HVTrust Dimensions vs MCP Servers

30.5 / 100 · 67.0% confidence

Codex MCP Go MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.6 / 25
2.6 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
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.4 below avg 12.4
AdoptionLog-scaled stars · package downloads
4.1 / 20
1.7 below avg 5.8

Activity Inputs

13.6 / 100
StarsRepository reach
10.3 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
—
Not available
Signed Commits
1%
of last 100 commits verified

Is Codex MCP Go safe?

Public trust evidence for Codex MCP Go 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 Codex MCP Go publish package provenance?
Yes. Codex MCP Go's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Codex MCP Go have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Codex MCP Go. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Codex MCP Go actively maintained?
Stale. The repository has not been pushed to in 190 days. Consider whether the project is still being maintained.
What license does Codex MCP Go use?
Codex MCP Go ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Codex MCP Go's commits signed?
1% of the last 100 commits to Codex MCP Go 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
Codex MCP Go appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies 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
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 Codex MCP Go?

For maintainers

HVTrust scores Codex MCP Go 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
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 41 spots (#720 → #761)
2026-08-08
Newly Listed
First tracked at rank #721
GitHub → npm: @zenfun510/codex-mcp-go

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 30.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/codex-mcp-go.svg)](https://hvtracker.net/agents/codex-mcp-go)
HTML:
<a href="https://hvtracker.net/agents/codex-mcp-go"><img src="https://hvtracker.net/badge/codex-mcp-go.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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