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/Custodia-Admin/pagebolt-mcpWrote 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/custodia-admin/pagebolt-mcp/pagebolt)<a href="https://agentmods.dev/mcp/custodia-admin/pagebolt-mcp/pagebolt"><img src="https://agentmods.dev/badge/mcp/custodia-admin/pagebolt-mcp/pagebolt/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/custodia-admin/pagebolt-mcp/pagebolt"><img src="https://agentmods.dev/badge/mcp/custodia-admin/pagebolt-mcp/pagebolt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pagebolt 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 1mo 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
{
"pagebolt": {
"command": "npx",
"args": [
"-y",
"pagebolt-mcp"
],
"env": {
"PAGEBOLT_API_KEY": ""
}
}
}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.
- 1mo ago First seen · 12 lines scan A 905921864922
pagebolt is an MCP server published in the GitHub repository Custodia-Admin/pagebolt-mcp (4 stars, last pushed 15d 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-08-31.
Other mcp servers, from other repositories
safari-mcp
Native Safari browser automation for AI agents — 80 tools, zero Chrome overhead. Runs locally from the safari-mcp npm package.
x-use
Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no API keys required. Runs locally from the x-use-mcp Python package. Needs 3 environment variables to run.
drisp-browser-dev
MCP server "drisp-browser-dev" as configured in drisplabs/browser-mcp. Runs dist/src/index.js with node.
browser-controller
Control your browser. Runs locally from the browser-controller npm package.
chrome-bridge
Your real, logged-in Chrome as an MCP server: 60 token-efficient web-dev tools. ChromeOS included. Runs locally from the chrome-bridge-mcp npm package.
mcp-server
Run Scrapeer visual web-scraping flows from AI agents. Runs locally from the @scrapeer/mcp-server npm package. Needs 1 environment variable to run.