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/thomasproject-stack/signal-prospector/prospectorgit clone --depth 1 https://github.com/thomasproject-stack/signal-prospectorWrote 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/thomasproject-stack/signal-prospector/prospector)<a href="https://agentmods.dev/mcp/thomasproject-stack/signal-prospector/prospector"><img src="https://agentmods.dev/badge/mcp/thomasproject-stack/signal-prospector/prospector.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
prospector 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
{ "prospector": { "command": "uvx", "args": [ "prospector" ] } }
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 · 8 lines scan A ee6c96f89741
prospector is an MCP server published in the GitHub repository thomasproject-stack/signal-prospector (2 stars, last pushed 1mo 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
browser-use
Make websites accessible for AI agents. Runs locally from the browser-use Python package.
stripe
Stripe's hosted MCP server: lets the agent work with customers, products, prices and payment links. Remote server at mcp.stripe.com.
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 3 environment variables to run.
engram-server
MCP server "engram-server" as configured in jamjet-labs/jamjet. Runs in Docker (ghcr.io/jamjet-labs/engram-server:0.5.0).
agent-web-search-mcp
A multi-provider web search layer for AI agents. Runs locally from the agent-web-search-mcp Python package.
swag-mcp
MCP server "swag-mcp", hosted remotely, as configured in jmagar/swag-mcp.