A checklist for building, linting, type-checking, inspecting, and smoke-testing an MCP server. A smoke test is a small check that confirms the service starts and basic behavior works.

Use it to validate the server locally, inspect its available tools, test a safe SELECT query, and check a Docker run.

It catches build errors, formatting problems, invalid types, startup failures, and incorrect tool responses before release.

testing — Cursor rule by evtapps

Install

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.

agentmods

npx agentmods add rules/evtapps/ditto-mcp/testing

Clone the repo

git clone --depth 1 https://github.com/evtapps/ditto-mcp

Made for: Cursor.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 131 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00010	$0.00131
Opus 5	$0.00005	$0.00066
Sonnet 5	$0.00002	$0.00026
Haiku 4.5	$0.00001	$0.00013

Measured yesterday against content hash 276f9c23f5f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

testing 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 yesterday.

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.

.cursor/rules/testing.mdc · 11 lines

What it actually says

Testing & Validation

Build: yarn build must succeed.
Lint: yarn lint:check and yarn format:check must pass.
Type-check: yarn type-check must pass.
MCP Inspector: npx -y @modelcontextprotocol/inspector npx ditto-mcp-server to validate tool listing and calls.
Smoke test Docker: run container and verify startup logs.
For tool behavior, test a safe SELECT with dummy args; verify items and error envelope formats.

Changes

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.

yesterday First seen · 11 lines · 10 tokens per session scan A 276f9c23f5f6

Subscribe to this mod's changes

testing is a cursor rule published in the GitHub repository evtapps/ditto-mcp (0 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 131 once invoked, about $0.0001 per session on Opus 5. 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.

DevOps and cloud Testing

testing

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Testing & Validation

What this file has done since we first saw it

Other cursor rules, from other repositories

angular-20

dev-standard

typescript

coolify-ai-docs

python_lib

specs