mcp server
Trestle
Detects leaked secrets (API keys, tokens, private keys) in source code.
Description as published by the maintainer. Source
- version 1.4.1
- active
- security
active — Most recent push to the repository was 2026-06-21. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
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 | 2 | 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-06-21 | 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 | 0 | 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 | |
| Package downloads | 41 downloads | Package downloads from the npm registry in this window. Includes continuous integration runs, mirrors and automated installs, so it overstates the number of human users. | 2026-07-30 to 2026-08-05 | npm | |
| Latest published version | 1.4.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-29 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | Apache-2.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-06-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
-
AgentTrust — Identity & Trust for A2A Agents
— last commit 2026-04-09, shares security
Identity, trust, and A2A orchestration for autonomous AI agents. Official A2A partner.
-
ai.kernora/agent-sec
— last commit 2026-07-31, shares security
Zero-install security baseline for AI coding agents — OWASP/CWE-cited rules over MCP.
-
ai.radmail/radmail-mcp
— last commit 2026-07-04, shares security
Email OS for agents - real-inbox search, triage, commitments, and a verifiable BEC hard-stop.
-
Scry
— archived, last commit 2026-05-25, shares security
Free IPv4 lookups against a distributed attacker-observation corpus.
-
app.scfcontrolsplatform/mcp-server-scf
— last commit 2026-07-27, shares security
MCP server for the SCF Controls Platform — 83 tools for controls, evidence, risk, and TPRM.
-
Arcjet
— last commit 2026-04-09, shares security
An MCP server for Arcjet - the runtime security platform that ships with your AI code.
-
ContrastAPI
— last commit 2026-08-04, shares security
55 tools, 7 Resources, Sigma rules, email SPF/DMARC, MITRE, CVE/KEV, risk_score. No key.
-
com.datakoot/security-intel-mcp
— last commit 2026-08-02, shares security
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
-
com.fidacy/ai-agent-firewall
— last commit 2026-08-04, shares security
Every agent action watched, every money-moving one gated, every verdict independently verifiable.
-
com.fidacy/mcp
— last commit 2026-08-04, shares security
Payment firewall for AI agents: a signed, verifiable verdict on every money-moving action.
These share tags the maintainers applied themselves, such as security. 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: development-tools, secret-scanning, security.
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