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/geek-fun/data-studio-agent/data-studio-mcp-data-studiogit clone --depth 1 https://github.com/geek-fun/data-studio-agentWrote 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/geek-fun/data-studio-agent/data-studio-mcp-data-studio)<a href="https://agentmods.dev/mcp/geek-fun/data-studio-agent/data-studio-mcp-data-studio"><img src="https://agentmods.dev/badge/mcp/geek-fun/data-studio-agent/data-studio-mcp-data-studio.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
data-studio 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 4d 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
{
"data-studio": {
"command": "npx",
"args": [
"-y",
"@geek-fun/data-studio-mcp"
],
"env": {}
}
}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.
- 4d ago First seen · 10 lines scan A efab9705c749
data-studio is an MCP server published in the GitHub repository geek-fun/data-studio-agent (3 stars, last pushed today), licensed Apache-2.0. 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
code-context
Local code search for AI coding agents: a CLI and MCP server with hybrid keyword + semantic search and SQL relevance-ranked aggregation over an index that lives in plain files. No accounts, no keys, no server. Runs locally from the @infino-ai/code-context npm package.
mako-ai
Agentmako is a local project intelligence CLI and MCP server for codebases and databases, with repo-aware indexing, schema snapshots, and secure live database connectivity. Runs locally from the agentmako npm package.
local-memory-mcp
Persistent local AI memory. SQLite + FTS5 + vector search, knowledge graph. No cloud, no API keys. Runs locally from the @studiomeyer/local-memory-mcp npm package. Needs 4 environment variables to run.
dbeast
MCP server "dbeast" as configured in snss10/DBeast. Runs ${workspaceFolder}/dbeast/src/server.py with python. Needs 9 environment variables to run.
midplane
Safe-by-default SQL guardrails for AI agents: AST-checked queries, per-table policy, audit log. Runs locally from the midplane npm package. Needs 4 environment variables to run.
postgres
Secure read-only PostgreSQL MCP server in Rust — a maintained alternative to the deprecated @modelcontextprotocol/server-postgres. Blocks writes at the AST, not with regexes. Runs locally from the postgres-mcp-hardened npm package. Needs 2 environment variables to run.