updated 2026-08-12 05:02 UTC

Delimit — API Governance for AI Coding Assistants

delimit-ai/delimit-mcp-server

The merge gate for AI-written code, with signed, replayable attestation. Works across Claude Code, Codex, Cursor, and Ge

MCP Servers Python Grade D Listed MIT
44.5/100
Rank #537 of 1283
Compare Delimit — API Governance for AI Coding Assistants

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

Is Delimit — API Governance for AI Coding Assistants safe? Delimit — API Governance for AI Coding Assistants scores 44.5/100 (Grade D), ranked #537 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; 84% of recent commits are signed; last pushed 2026-08-11. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#191 Better Notion MCP — 44.6 (D) → #192 PaSympa Discord MCP — 44.6 (D) → #194 Genexus18MCP — 44.4 (D) → #195 Wavyrai reMarkable MCP Server — 44.3 (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 17 spots (#531 → #548)
2026-08-08
Newly Listed
First tracked at rank #529
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Compare with another agent Get email alerts for Delimit — API Governance for AI Coding Assistants View MCP Servers Report missing data
55.4
Activity sub-score · out of 100
#193
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 yesterday

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
21
Forks
5
Last Push
2026-08-11
yesterday
Commits (4 wk)
31
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #537

Analysis

HVTrust Dimensions vs MCP Servers

44.5 / 100 · 67.0% confidence

Delimit — API Governance for AI Coding Assistants MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.7 / 25
6.7 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
17.9 / 20
5.5 above avg 12.4
AdoptionLog-scaled stars · package downloads
3.2 / 20
2.6 below avg 5.8

Activity Inputs

55.4 / 100
StarsRepository reach
8.1 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
18.8 / 25
CommunityFork signal
3.6 / 20

Supply Chain Trust

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

Is Delimit — API Governance for AI Coding Assistants safe?

Public trust evidence for Delimit — API Governance for AI Coding Assistants 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 Delimit — API Governance for AI Coding Assistants publish package provenance?
Yes. Delimit — API Governance for AI Coding Assistants's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Delimit — API Governance for AI Coding Assistants have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Delimit — API Governance for AI Coding Assistants. 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 Delimit — API Governance for AI Coding Assistants actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Delimit — API Governance for AI Coding Assistants use?
Delimit — API Governance for AI Coding Assistants ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Delimit — API Governance for AI Coding Assistants's commits signed?
84% of the last 100 commits to Delimit — API Governance for AI Coding Assistants 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
Delimit — API Governance for AI Coding Assistants 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 Delimit — API Governance for AI Coding Assistants?

For maintainers

HVTrust scores Delimit — API Governance for AI Coding Assistants 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 17 spots (#531 → #548)
2026-08-08
Newly Listed
First tracked at rank #529
GitHub → npm: delimit-cli

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 44.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/delimit-api-governance-for-ai-coding-assistants.svg)](https://hvtracker.net/agents/delimit-api-governance-for-ai-coding-assistants)
HTML:
<a href="https://hvtracker.net/agents/delimit-api-governance-for-ai-coding-assistants"><img src="https://hvtracker.net/badge/delimit-api-governance-for-ai-coding-assistants.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