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/ContentWriterco/Compabase-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/contentwriterco/compabase-mcp/compabase)<a href="https://agentmods.dev/mcp/contentwriterco/compabase-mcp/compabase"><img src="https://agentmods.dev/badge/mcp/contentwriterco/compabase-mcp/compabase/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/contentwriterco/compabase-mcp/compabase"><img src="https://agentmods.dev/badge/mcp/contentwriterco/compabase-mcp/compabase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
compabase 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 7d 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
{
"compabase": {
"type": "http",
"url": "https://compabase.com/api/mcp/claude"
}
}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.
- 7d ago Changed 321a6e3d2531
- 1mo ago First seen · 6 lines scan A add92ef5af82
compabase is an MCP server published in the GitHub repository ContentWriterco/Compabase-MCP (0 stars, last pushed 7d 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
scala
MCP server for S.C.A.L.A. AI OS — run your entire business from Claude. CRM, invoicing, bookings, AI assistant, 19 industry verticals, 250M+ company database. Runs locally from the scala-mcp-server npm package. Needs 1 environment variable to run.
vybe-solana-api
Solana MCP for wallets, trades, markets, PnL, transfers, onchain data, signable swaps and API tools. Remote server at docs.vybenetwork.com.
stripe
Stripe's hosted MCP server: lets the agent work with customers, products, prices and payment links. Remote server at mcp.stripe.com.
crypto
Crypto token and narrative trend volume over time, with growth signals. Free key at trendsmcp.ai. Remote server at crypto.api.trendsmcp.ai.
coinrithm-trading
CoinRithm MCP server (coinrithm-mcp) and self-host agent runner (coinrithm-agent): keyless prediction-market data across 12 venues, plus paper trading of crypto spot, futures, and prediction markets with a user-minted API key. Runs locally from the @coinrithm/mcp-trading npm package. Needs 1 environment variable to…
mcp-trading
Keyless prediction-market data across 12 venues plus paper-trading of crypto spot, futures, and PM. Runs locally from the @coinrithm/mcp-trading npm package. Needs 2 environment variables to run.