updated 2026-10-16 16:07 UTC

Codex MCP Tool

Repository
MCP Servers TypeScript Listed MIT

Is Codex MCP Tool safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.7 / 10
Provenance None
Signed commits 3%
Last push 16d ago
Advisories None known
Compare Codex MCP Tool

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Codex MCP Tool scores 49.8/100 (Grade D), ranked #1020 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.7/10; 3% of recent commits are signed; no published advisory affects its latest release (@trishchuk/codex-mcp-tool); last pushed 2026-09-30. Every point is earned from checkable signals — never paid placement. How scoring works →

How Codex MCP Tool could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Codex MCP Tool and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/x51xxx/codex-mcp-tool, MIT, last pushed 2026-09-30. 3% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 2.7/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 5
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @trishchuk/codex-mcp-tool 2.6.0. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-08-27 OSSF Scorecard: 2.6/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Codex MCP Tool’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Codex MCP Tool compares in MCP Servers

  1. #576 Meta Ads MCP 49.9 +0.1
  2. #577 Markifact: AI Performance Marketing 49.8 ±0
  3. #578 Codex MCP Tool 49.8 this agent
  4. #579 MCP Document Reader 49.8 ±0
  5. #580 Trade It 49.4 −0.4

Bars show each HVTrust score; the tick marks Codex MCP Tool’s 49.8.

Where the 49.8 comes from

HVTrust dimensions vs the MCP Servers average

49.8 / 100 · 100.0% confidence

Codex MCP Tool MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.5 / 25
7.0 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
10.8 / 17
1.5 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.3 / 20
1.0 above avg 12.3
AdoptionLog-scaled stars · package downloads
6.4 / 20
1.0 below avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-16
Grade Changed
Trust grade C → D
2026-10-16
Rank Moved
Rank dropped 18 spots (#1002 → #1020)
2026-10-12
Rank Moved
Rank dropped 14 spots (#976 → #990)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.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 Codex MCP Tool View MCP Servers Report missing data
42.9
Activity sub-score · out of 100
#578
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 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 →

Signals refreshed 2026-10-16 16:07 UTC · Repo last pushed 16 days ago

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
24
Forks
7
Last Push
2026-09-30
16 days ago
Commits (4 wk)
3
Downloads (7d)
183
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
▼18
was #1002

Analysis

Activity Inputs

42.9 / 100
StarsRepository reach
8.4 / 30
FreshnessLast push recency
22.8 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
4.2 / 20

Common questions about Codex MCP Tool

Public trust evidence for Codex MCP Tool 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 Tool publish package provenance?
No published build provenance is currently detected for Codex MCP Tool. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Codex MCP Tool have an OpenSSF Scorecard?
Codex MCP Tool has an OpenSSF Scorecard score of 2.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 Codex MCP Tool actively maintained?
Maintained. Last push was 16 days ago.
What license does Codex MCP Tool use?
Codex MCP Tool ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Codex MCP Tool's commits signed?
3% of the last 100 commits to Codex MCP Tool 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 Tool 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
How this surface has changed

Detected changes to Codex MCP Tool's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-10-02
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Codex MCP Tool?

For maintainers

HVTrust scores Codex MCP Tool 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
Rank 29Grade 10HVTrust 6Score 3Listed 2Scorecard 1Delisted 1MCP 1Surface 1
2026-10-16
Grade Changed
Trust grade C → D
2026-10-16
Rank Moved
Rank dropped 18 spots (#1002 → #1020)
2026-10-12
Rank Moved
Rank dropped 14 spots (#976 → #990)
2026-10-10
Rank Moved
Rank dropped 22 spots (#947 → #969)
2026-10-09
Grade Changed
Trust grade D → C
2026-10-09
Rank Moved
Rank rose 17 spots (#964 → #947)
2026-10-06
Grade Changed
Trust grade C → D
2026-10-04
Grade Changed
Trust grade D → C
2026-10-04
Rank Moved
Rank rose 16 spots (#969 → #953)
2026-10-02
Provider Added
Runtime surface grew — new detected provider dependency: OpenAI
2026-10-02
Grade Changed
Trust grade C → D
2026-10-02
Rank Moved
Rank dropped 30 spots (#936 → #966)
2026-10-01
Rank Moved
Rank dropped 49 spots (#887 → #936)
2026-09-30
Grade Changed
Trust grade D → C
2026-09-30
Rank Moved
Rank rose 76 spots (#963 → #887)
2026-09-30
HVTrust Changed
HVTrust up 3.1pts (49.0 → 52.1)
2026-09-30
Activity Score Changed
Activity score up 8pts (38 → 46)
2026-09-27
Rank Moved
Rank rose 11 spots (#973 → #962)
2026-09-25
Rank Moved
Rank dropped 12 spots (#958 → #970)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 182 spots (#1137 → #955)
2026-09-23
HVTrust Changed
HVTrust up 28.0pts (21.1 → 49.1)
2026-09-22
Newly Listed
First tracked at rank #1137
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Grade Changed
Trust grade C → D
2026-09-16
Grade Changed
Trust grade D → C
2026-09-16
Rank Moved
Rank rose 18 spots (#940 → #922)
2026-09-15
Rank Moved
Rank dropped 10 spots (#930 → #940)
2026-09-10
Grade Changed
Trust grade C → D
2026-09-09
Rank Moved
Rank dropped 18 spots (#897 → #915)
2026-09-07
Rank Moved
Rank dropped 52 spots (#839 → #891)
2026-09-06
Grade Changed
Trust grade D → C
2026-09-06
Rank Moved
Rank rose 86 spots (#925 → #839)
2026-09-06
HVTrust Changed
HVTrust up 3.7pts (46.8 → 50.5)
2026-09-06
Activity Score Changed
Activity score up 9pts (32 → 41)
2026-09-05
Rank Moved
Rank rose 281 spots (#1206 → #925)
2026-09-05
HVTrust Changed
HVTrust up 15.6pts (31.2 → 46.8)
2026-09-04
Rank Moved
Rank dropped 19 spots (#1187 → #1206)
2026-09-03
Rank Moved
Rank dropped 397 spots (#790 → #1187)
2026-09-03
HVTrust Changed
HVTrust down 15.7pts (47.0 → 31.3)
2026-09-02
Rank Moved
Rank dropped 39 spots (#751 → #790)
2026-09-01
Rank Moved
Rank dropped 33 spots (#718 → #751)
2026-08-31
Rank Moved
Rank dropped 39 spots (#679 → #718)
2026-08-30
Rank Moved
Rank dropped 19 spots (#660 → #679)
2026-08-29
Rank Moved
Rank dropped 45 spots (#615 → #660)
2026-08-28
Rank Moved
Rank dropped 55 spots (#560 → #615)
2026-08-28
Activity Score Changed
Activity score down 6pts (39 → 33)
2026-08-27
Scorecard Added
OSSF Scorecard: 2.6/10
2026-08-27
Rank Moved
Rank rose 314 spots (#874 → #560)
2026-08-27
HVTrust Changed
HVTrust up 18.0pts (31.3 → 49.3)
2026-08-26
Rank Moved
Rank dropped 110 spots (#764 → #874)
2026-08-16
Rank Moved
Rank dropped 18 spots (#741 → #759)
2026-08-10
Rank Moved
Rank dropped 39 spots (#695 → #734)
2026-08-08
Newly Listed
First tracked at rank #695
GitHub → npm: @trishchuk/codex-mcp-tool

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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