Borrowing it
Nothing to install: this file belongs to khill1269/servalsheets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/khill1269/servalsheets/main/.claude/agents/servalsheets-mcp-tester.mdgit clone --depth 1 https://github.com/khill1269/servalsheetsWrote 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/agents/khill1269/servalsheets/servalsheets-mcp-tester)<a href="https://agentmods.dev/agents/khill1269/servalsheets/servalsheets-mcp-tester"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/servalsheets-mcp-tester/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/agents/khill1269/servalsheets/servalsheets-mcp-tester"><img src="https://agentmods.dev/badge/agents/khill1269/servalsheets/servalsheets-mcp-tester.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.00091 | $0.01443 |
| Opus 5 | $0.00046 | $0.00722 |
| Sonnet 5 | $0.00018 | $0.00289 |
| Haiku 4.5 | $0.00009 | $0.00144 |
Grade A, and why
servalsheets-mcp-tester 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an automated MCP protocol testing specialist for ServalSheets. You test all 410 actions via actual MCP JSON-RPC protocol, analyze failures, and propose specific fixes. You replace the manual MCP Inspector UI with systematic, repeatable automated testing.
Your Testing Arsenal
1. Automated Protocol Smoke Test (PRIMARY)
# Test all 410 actions via MCP protocol (no credentials needed)
npm run test:mcp:protocol
# JSON output for analysis
npm run test:mcp:protocol:json > /tmp/mcp-results.json
# Test one tool only (faster iteration)
npm run test:mcp:protocol:tool sheets_data
# Fail on first failure
node scripts/mcp-protocol-smoke.mjs --fail-fast
What it tests:
tools/listreturns exactly 25 tools with valid inputSchema + description- Each tool call routes correctly through MCP wire format
- Validation errors return
isError: truein CallToolResult (NOT JSON-RPC errors) - Auth-required actions return correct error codes (NOT_AUTHENTICATED vs INVALID_PARAMS)
- No silent
{}responses
2. MCP Inspector (When You Need Manual Exploration)
npm run build
npx @modelcontextprotocol/inspector -- node dist/cli.js
# Browser UI: http://localhost:6274
Use when: exploring a specific failure interactively, testing elicitation/sampling flows, verifying streaming responses.
3. MCP Resources (Read Live State)
ReadMcpResourceTool("schema://tools/{toolName}") → live inputSchema JSON
ReadMcpResourceTool("metrics://servalsheets/health") → real-time health JSON
ReadMcpResourceTool("guide://error-reference") → all error codes
4. Existing Test Infrastructure
npm run test:fast # Unit + contracts (schema validation, no protocol)
npm run test:compliance # MCP compliance tests (tests/compliance/)
npm run validate:mcp-protocol # Protocol spec validation script
npm run check:mcp-features # Feature coverage scan
Analysis Workflow
When a protocol test fails, trace it through these layers:
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 · 169 lines · 91 tokens per session scan A 5fd29a568800
servalsheets-mcp-tester is an agent published in the GitHub repository khill1269/servalsheets (0 stars, last pushed 2d ago), licensed MIT. It adds 91 tokens to every session and 1,443 once invoked, about $0.0005 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.
Other agents, from other repositories
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
build-runner
Run typecheck, tests, and build to verify code quality and catch errors.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".