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/scope-bid/scope-mcpWrote 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/scope-bid/scope-mcp/scope-aec-mcp-scope-mcp)<a href="https://agentmods.dev/mcp/scope-bid/scope-mcp/scope-aec-mcp-scope-mcp"><img src="https://agentmods.dev/badge/mcp/scope-bid/scope-mcp/scope-aec-mcp-scope-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
scope-mcp 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
{
"scope-mcp": {
"command": "npx",
"args": [
"-y",
"@jackgillen15-dev/scope-mcp"
],
"env": {
"SCOPE_API_BASE": "https://scope-bid.vercel.app",
"SCOPE_API_TOKEN": "",
"SCOPE_ORG_SLUG": ""
}
}
}What else server.json configures
This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.
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 · 14 lines scan A 2d498828125a
scope-mcp is an MCP server published in the GitHub repository scope-bid/scope-mcp (1 stars, last pushed 1mo 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
open-agreements
Fill standard legal agreement templates (NDAs, SAFEs, NVCA docs, employment) as DOCX files. Runs locally from the @open-agreements/contract-templates-mcp npm package.
clio-mcp
Connect Claude to Clio: 26 tools for matters, contacts, documents, tasks, billing, audit logs. Runs locally from the @oktopeak/clio-mcp npm package. Needs 8 environment variables to run.
fedlex
MCP server "fedlex" as configured in malkreide/fedlex-mcp. Runs fedlex_mcp.server with python.
fedlex-mcp
MCP Server for Swiss federal law via the Fedlex SPARQL endpoint. Runs locally from the fedlex-mcp Python package.
mycase-mcp
Connect Claude to MyCase: cases, contacts, documents, tasks, calendar, calls, time, billing, staff. Runs locally from the @oktopeak/mycase-mcp npm package. Needs 5 environment variables to run.
eu-ai-act-mcp
EU AI Act compliance MCP server with bounded system assessment, structured classification, article grounding, GPAI, Art. 6(3), Annex III/IV, deadlines, obligations, penalties, and FAQ. By Lexbeam Software. Runs locally from the @lexbeam-software/eu-ai-act-mcp npm package.