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/Goodeye-Labs/goodeye-cliWrote 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/goodeye-labs/goodeye-cli/goodeye)<a href="https://agentmods.dev/mcp/goodeye-labs/goodeye-cli/goodeye"><img src="https://agentmods.dev/badge/mcp/goodeye-labs/goodeye-cli/goodeye/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/goodeye-labs/goodeye-cli/goodeye"><img src="https://agentmods.dev/badge/mcp/goodeye-labs/goodeye-cli/goodeye.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
goodeye 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 1mo 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
{ "goodeye": { "url": "https://mcp.goodeye.dev/mcp", "type": "streamable-http" } }
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.
- 1mo ago First seen · 6 lines scan A 928087453aa8
goodeye is an MCP server published in the GitHub repository Goodeye-Labs/goodeye-cli (3 stars, last pushed 13d 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
media-validator
MCP server "media-validator" as configured in HelixDevelopment/code. Launched with bash constitution/skills/media-validator/media-validator.sh. Needs 1 environment variable to run.
waitbus
Workstation-local event bus and blocking wait/emit primitive: let any agent or script wait on or emit CI, pytest, Docker, and filesystem events without polling. GitHub Actions is source #1. Runs locally from the waitbus Python package.
slop-eval
Scores AI-generated UI for genericness ("slop") using an Anthropic LLM-judge rubric, with a --json mode for CI/agent quality gates and a documented programmatic API (scorecomposite, ScoreInput, LLMJudgeSource) for in-process use by agent frameworks. Runs locally from the slop-eval-cli Python package.
swarm-rd-orchestrator
Ray-native context/memory sharing for parallel research agents, with an agent-native CLI and MCP server (Milestone 1 spike). Runs locally from the swarm-rd-orchestrator-cli Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.