Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/circle-rd/upki-caWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/circle-rd/upki-ca/upki-ca-docs-local-dev)<a href="https://agentmods.dev/mcp/circle-rd/upki-ca/upki-ca-docs-local-dev"><img src="https://agentmods.dev/badge/mcp/circle-rd/upki-ca/upki-ca-docs-local-dev/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/circle-rd/upki-ca/upki-ca-docs-local-dev"><img src="https://agentmods.dev/badge/mcp/circle-rd/upki-ca/upki-ca-docs-local-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
uPKI CA Docs (local dev) scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 17d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"uPKI CA Docs (local dev)": {
"url": "http://localhost:3000/mcp",
"type": "http"
}
}What else mcp.json configures
This page is one entry in a file that holds 3. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 17d ago First seen · 6 lines scan A 923a10099834
uPKI CA Docs (local dev) is an MCP server published in the GitHub repository circle-rd/upki-ca (2 stars, last pushed 13d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.
Other mcp servers, from other repositories
robotmcp
Modular MCP server with Streamable HTTP, optional OAuth 2.1, Supabase auth, Cloudflare tunnel, and creator-only access control. Runs locally from the robotmcp.server Python package. Needs 4 environment variables to run.
engram-server
MCP server "engram-server" as configured in jamjet-labs/jamjet. Runs in Docker (ghcr.io/jamjet-labs/engram-server:0.5.0).
plain-example
MCP server "plain-example", hosted remotely at plain-example.plaintunnel.com, as configured in dropseed/plain.
multisim-mcp
Unofficial MCP server for NI Multisim Automation API. Runs locally from the multisim-mcp Python package. Needs 1 environment variable to run.
plaud
MCP server "plaud" as configured in Gunnarguy/PlaudBlender. Runs locally from the @plaud-ai/mcp npm package.
civic-agent-kit
Python SDK for building civic AI tools across Africa — M-Pesa, parliament, budgets, drought, MCP and A2A. Runs locally from the civic-agent-kit Python package.