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/jmanhype/speckitWrote 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/jmanhype/speckit/specmatic)<a href="https://agentmods.dev/mcp/jmanhype/speckit/specmatic"><img src="https://agentmods.dev/badge/mcp/jmanhype/speckit/specmatic/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/jmanhype/speckit/specmatic"><img src="https://agentmods.dev/badge/mcp/jmanhype/speckit/specmatic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
specmatic 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
{
"specmatic": {
"command": "npx",
"args": [
"-y",
"@specmatic/mcp"
],
"env": {
"SPECMATIC_CENTRAL_REPO_URL": "${SPECMATIC_CENTRAL_REPO_URL}"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. 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.
- 1mo ago First seen · 12 lines scan A d60c1234cf1e
specmatic is an MCP server published in the GitHub repository jmanhype/speckit (26 stars, last pushed 6mo 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-09-01.
Other mcp servers, from other repositories
playwright-test
A high-level API to automate web browsers. Runs locally from the playwright npm package.
webhook-tester
Test webhook endpoints — send requests, measure latency, validate responses. x402 micropayment. Remote server at webhook-tester.api.klymax402.com.
openapi-contract-guard-mcp
MCP server "openapi-contract-guard-mcp" as configured in xiaohuxi/openapi-contract-guard-mcp. Runs locally from the openapi-contract-guard-mcp 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.
vscode-automation-mcp
MCP server "vscode-automation-mcp" as configured in microsoft/vscode. Launched with npm --prefix test/mcp run start-stdio.