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/vish288/mcp-codaWrote 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/vish288/mcp-coda/mcp-coda)<a href="https://agentmods.dev/mcp/vish288/mcp-coda/mcp-coda"><img src="https://agentmods.dev/badge/mcp/vish288/mcp-coda/mcp-coda/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/vish288/mcp-coda/mcp-coda"><img src="https://agentmods.dev/badge/mcp/vish288/mcp-coda/mcp-coda.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-coda 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 10d 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
{
"mcp-coda": {
"command": "uvx",
"args": [
"mcp-coda"
],
"env": {
"CODA_API_TOKEN": "",
"CODA_READ_ONLY": ""
}
}
}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.
- 10d ago First seen · 12 lines scan A 3eb64ca74367
mcp-coda is an MCP server published in the GitHub repository vish288/mcp-coda (2 stars, last pushed 18d 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
skyvern
AI-powered browser automation — navigate, click, fill forms, and extract data from any website. Remote server at api.skyvern.com.
pdf-mcp
Surgical PDF access for AI agents: keyword, semantic & hybrid search; structured extraction of text, tables, images & TOC; OCR; and CJK/vertical-script support — with SQLite caching. Runs locally from the pdf-mcp Python package. Needs 2 environment variables to run.
schemabrain
The trust and intelligence layer between AI agents and your database. Runs locally from the schemabrain Python package. Needs 1 environment variable to run.
oraclemcp
MCP server "oraclemcp" as configured in MuhDur/oraclemcp. Runs in Docker (ghcr.io/muhdur/oraclemcp:0.9.0).
mcp-clickhouse
ClickHouse query & management for AI agents — SQL-classified read/write/destructive gating. Runs locally from the @dockndevai/mcp-clickhouse npm package. Needs 4 environment variables to run.
mcp-neo4j-knowledge-graph
Neo4j-based knowledge graph MCP server with temporal versioning and semantic search. Runs locally from the @henrychong-ai/mcp-neo4j-knowledge-graph npm package.