mcp server
Cejel
Offline deterministic engineering-trust certificates for repositories, with no telemetry.
Description as published by the maintainer. Source
- version 0.2.2
- active
active — Most recent push to the repository was 2026-08-06.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-06 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 12 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.2.2 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-29 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | AGPL-3.0 | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-29 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
io.github.duriantaco/skylos
— last commit 2026-08-07, shares ai-generated-code, code-quality, devsecops
Dead code, security, secrets detection and code quality for Python, TypeScript, Go.
-
io.github.davidmosiah/mcp-scorecard
— last commit 2026-08-06, shares cli, scorecard
Agent-readiness scorecard for any MCP server: 10 checks, 0-100 score, actionable findings.
-
io.github.artokun/comfyui-mcp
— last commit 2026-08-06, shares offline
MCP server + Claude Code plugin for ComfyUI: run workflows, generate images, manage models & VRAM.
-
Draugr
— last commit 2026-08-06, shares cli, devsecops, sarif
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
-
Bomly
— last commit 2026-08-03, shares devsecops, sarif
Give your coding agent the dependency graph it is about to change: scan, diff, explain, audit
-
io.github.caglarbozkurt/heimdall
— last commit 2026-07-06, shares cli, sarif, security
Scan an MCP server or agent config for injection, exfiltration, and risky capabilities.
-
io.github.Ecocitizenz/ecz-id-mcp-verifier
— last commit 2026-07-01, shares sarif
Local-first, read-only ECZ-ID verifier over MCP (stdio): checks, reports, explains, routes.
-
LiveCheck AI
— last commit 2026-07-30, shares code-quality, code-review
Secure MCP runtime server for scanning and autofixing code issues
-
ControlKeel
— last commit 2026-08-06, shares code-review, devsecops, security
Governed MCP workflows with policy validation, findings tracking, and review gates.
-
io.github.abhinavteja123/codemore
— last commit 2026-07-18, shares code-quality, security, static-analysis
The static analyzer your AI agent reads — fix-ready, machine-readable scan reports over MCP.
These share tags the maintainers applied themselves, such as ai-generated-code, code-quality, devsecops, static-analysis. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: ai-generated-code, cli, code-quality, code-review, devsecops, offline, sarif, scorecard, security, static-analysis, trust, trust-certificate.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab