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/GeckoVision/gecko-surfWrote 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/geckovision/gecko-surf/surf)<a href="https://agentmods.dev/mcp/geckovision/gecko-surf/surf"><img src="https://agentmods.dev/badge/mcp/geckovision/gecko-surf/surf.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
surf 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
{
"surf": {
"command": "uvx",
"args": [
"gecko-surf"
],
"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.
- 7d ago First seen · 9 lines scan A d3fcbcc64973
surf is an MCP server published in the GitHub repository GeckoVision/gecko-surf (6 stars, last pushed 2d ago), 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
liquid
Self-hosted MCP server for Liquid — connect your agent to any HTTP API on the fly. Runs locally from the liquid-mcp Python package. Needs 5 environment variables to run.
llmwiki-serve
Serve existing Markdown, Obsidian-style, or LLMWiki folders as cited agent-readable context. Runs locally from the llmwiki-serve Python package.
plsql-mcp
MCP server "plsql-mcp" as configured in MuhDur/plsql-intelligence. Runs in Docker (ghcr.io/muhdur/plsql-mcp:0.6.3).
cortex
MCP server "cortex" as configured in tools-for-agents/cortex. Runs locally from the @tools-for-agents/cortex npm package.
commune-mcp
MCP server for Commune – email infrastructure for agents. Set up an inbox and send your first email in 30 seconds. Programmatic inboxes, consistent threads, custom domains, attachments, and structured data. Runs locally from the commune-mcp Python package. Needs 1 environment variable to run.
contentful-management
Create, update, and publish content across spaces and environments. Runs locally from the mcparmory-contentful-management Python package.