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/hackerdogs-ai/hd-mcpservers-dockerWrote 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/rules/hackerdogs-ai/hd-mcpservers-docker/mcp-server-test-compliance)<a href="https://agentmods.dev/rules/hackerdogs-ai/hd-mcpservers-docker/mcp-server-test-compliance"><img src="https://agentmods.dev/badge/rules/hackerdogs-ai/hd-mcpservers-docker/mcp-server-test-compliance/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/rules/hackerdogs-ai/hd-mcpservers-docker/mcp-server-test-compliance"><img src="https://agentmods.dev/badge/rules/hackerdogs-ai/hd-mcpservers-docker/mcp-server-test-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00989 |
| Opus 5 | $0.00000 | $0.00495 |
| Sonnet 5 | $0.00000 | $0.00198 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
mcp-server-test-compliance 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Test Compliance
Every MCP server's test.sh must include these five test areas. Treat this as required compliance for all *-mcp servers in this repo.
1. Test the install
- Build or verify the Docker image (e.g.
docker build -t <image> .ordocker image inspect <image>). - Fail if the image cannot be built or is missing.
2. Test loading of tools using stdio
- Run the server with
MCP_TRANSPORT=stdio. - Send JSON-RPC:
initialize, thennotifications/initialized, thentools/list. - Assert the response contains a tools list (e.g. grep for
"tools"orresult.tools). - Capture full output before asserting (e.g.
OUT=$( ... ); echo "$OUT" | grep -q '"tools"') to avoid pipe buffering issues.
3. Test calling one or more tools using stdio
- Send
initialize,notifications/initialized, thentools/callwith a simple tool (e.g. a status tool, or a call that needs no API key). - Keep stdin open after the last message (e.g.
( printf '...'; sleep 4 ) | docker run ...) so the server can write the response. - Assert the response contains expected result (e.g.
"result","content", or a known string from the tool output). - Prefer tools that do not require API keys or network when possible.
4. Test loading of tools using HTTP streamable
- Start the server with
MCP_TRANSPORT=streamable-httpandMCP_PORT=<port>. - POST to
http://localhost:<port>/mcpwithContent-Type: application/jsonandAccept: application/json, text/event-stream. - Send
initialize; capturemcp-session-idfrom response headers if present. - Send
tools/list(andnotifications/initializedif required) with the same session. - Assert the response includes a tools list (e.g. contains
"tools").
5. Test calling one or more tools using HTTP streamable
- Using the same HTTP session (and
mcp-session-idif used), POSTtools/callwith a simple tool and minimal arguments. - Assert the response contains
"result"or"content"or a known success indicator. - Prefer tools that do not require API keys when possible.
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.
- 9d ago First seen · 72 lines · 0 tokens per session scan A 27d32f1002f8
mcp-server-test-compliance is a cursor rule published in the GitHub repository hackerdogs-ai/hd-mcpservers-docker (5 stars, last pushed 21d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 989 tokens. 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 cursor rules, from other repositories
agent-config-test-confirmation
Require explicit user approval before running or creating tests that mutate active agent configs.
fail-closed-verification
Fail-closed verification protocol — direct validation required; no speculation; mutable data/config protected.
pytest-run-tests-integration
All pytest tests for ongoing use must be runnable via runtests.py.
tdd-skill
TDD follows Kent Beck's short feedback loop. With an AI agent, the Green step is more deliberate: do not ask for intentionally dirty code and plan a cleanup pass. Ask for the smallest production-quality implementation that satisfies the test, then reserve deeper design changes for a separate refining refactor.
testing-patterns
Comprehensive testing patterns for React Testing Library and Go testing in POS System.
unit-test-manners
When implementing unit tests, adhere to the following principles to ensure robust, maintainable, and fast tests.