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/TJC-LP/coda-mcp-serverWrote 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/tjc-lp/coda-mcp-server/coda)<a href="https://agentmods.dev/mcp/tjc-lp/coda-mcp-server/coda"><img src="https://agentmods.dev/badge/mcp/tjc-lp/coda-mcp-server/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/tjc-lp/coda-mcp-server/coda"><img src="https://agentmods.dev/badge/mcp/tjc-lp/coda-mcp-server/coda.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
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 9d 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
{
"coda": {
"command": "uv",
"args": [
"run",
"coda-mcp-server"
],
"env": {
"CODA_API_KEY": "${CODA_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.
- 9d ago First seen · 12 lines scan A 1fa6d9177149
coda is an MCP server published in the GitHub repository TJC-LP/coda-mcp-server (6 stars, last pushed 10mo 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
spreadsheet-db-mcp
SQLite-authoritative entity database with an async Google Sheets projection for AI agents. Runs locally from the spreadsheet-db-mcp npm package. Needs 3 environment variables to run.
localdata-mcp
MCP server for databases, spreadsheets, structured files, and directed graphs. Runs locally from the localdata-mcp Python package.
mcp-coda
MCP server for Coda API — docs, pages, tables, rows, formulas, permissions, and more. Runs locally from the mcp-coda Python package. Needs 2 environment variables to run.
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.
docs2db-mcp
MCP server "docs2db-mcp" as configured in rhel-lightspeed/docs2db-mcp-server. Runs locally from the docs2db-mcp Python package.
unifiles-mcp
MCP server for unifiles - unified file operations library. Provides Excel, PDF, Word, and SQLite file operations through Model Context Protocol. Runs locally from the unifiles-mcp Python package.