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.
npx agentmods add mcp/boettiger-lab/data-workflows/duckdb-geogit clone --depth 1 https://github.com/boettiger-lab/data-workflowsWrote 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/boettiger-lab/data-workflows/duckdb-geo)<a href="https://agentmods.dev/mcp/boettiger-lab/data-workflows/duckdb-geo"><img src="https://agentmods.dev/badge/mcp/boettiger-lab/data-workflows/duckdb-geo.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
duckdb-geo 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 5d 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.
This is a copy
100% identical to duckdb-geo — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"duckdb-geo": {
"type": "http",
"url": "https://duckdb-mcp.nrp-nautilus.io/mcp"
}
}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.
- 5d ago First seen · 6 lines scan A 86907a0f7f7f
duckdb-geo is an MCP server published in the GitHub repository boettiger-lab/data-workflows (5 stars, last pushed today), licensed BSD-3-Clause. 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. It is 100% identical to duckdb-geo, differing in 0 lines, and is treated as a copy.
Other mcp servers, from other repositories
quilt-mcp
Secure MCP server for accessing Quilt data with IAM or JWT authentication. Runs locally from the quilt-mcp Python package.
elastic-mcp
Model Context Protocol server for Elasticsearch (search, index inspection, cluster info; read-only by default with optional write tools). Runs locally from the elastic-mcp npm package.
neo4j-reuse
MCP server "neo4j-reuse" as configured in usalu/semio. Launched with bun script.ts dev mcp neo4j reuse.
mcp-database-server
Add your description here. Runs locally from the mcp-database-server Python package.
sql-server-mcp
Local, single-user MCP server for read-only SQL Server / MS Fabric queries - one process per tenant. Runs locally from the sql-server-mcp Python package.
mcp-opensearch
Read-only MCP server for OpenSearch and OpenSearch Dashboards. Runs locally from the mcp-opensearch Python package.