api-testing

api-testing is a skill for Claude Code from wallieinformal201/pentest-mcp-server. It costs 46 tokens per session (4,226 once invoked), scanned A, original, Apache-2.0.

A testing guide for MCP tool and resource handlers using Vitest, a JavaScript and TypeScript testing framework. It shows how to create mock request contexts and check results, errors, and formatting.

In plain words
What is it for?
Use it to write unit tests for handlers, services, utilities, storage-dependent code, and input or error handling.
Why use it?
It lets you test handler behavior without running the full server, while keeping tests useful when the implementation changes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the @cyanheads/pentest-mcp-server plugin — 31 skills shipped together

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 skills/wallieinformal201/pentest-mcp-server/api-testing
Any agent
npx skills add wallieinformal201/pentest-mcp-server --skill api-testing
Clone the repo
git clone --depth 1 https://github.com/wallieinformal201/pentest-mcp-server

Made for: Claude Code.

Or install @cyanheads/pentest-mcp-server, the plugin that ships this one along with the rest of its 31 skills.

Wrote 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.

agentmods badge for api-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/wallieinformal201/pentest-mcp-server/api-testing.svg)](https://agentmods.dev/skills/wallieinformal201/pentest-mcp-server/api-testing)
Your own site
<a href="https://agentmods.dev/skills/wallieinformal201/pentest-mcp-server/api-testing"><img src="https://agentmods.dev/badge/skills/wallieinformal201/pentest-mcp-server/api-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,226 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.04226
Opus 5 $0.00023 $0.02113
Sonnet 5 $0.00009 $0.00845
Haiku 4.5 $0.00005 $0.00423

Measured 5d ago against content hash 4687adf18eb6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

api-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 5d 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.

skills/api-testing/SKILL.md · 397 lines

How it starts

The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Tests target handler behavior directly — call handler(input, ctx), assert on the return value or thrown error. The framework's handler factory (try/catch, formatting, telemetry) is not involved. Use createMockContext from @cyanheads/mcp-ts-core/testing to construct the ctx argument.

Additional exports from /testing: createMockLogger() returns a standalone MockContextLogger for unit-testing code that accepts a ContextLogger directly (services, utilities). createInMemoryStorage(options?) provides a real StorageService backed by InMemoryProvider for testing services that take a StorageService dependency.

Philosophy: Test behavior, not implementation. Refactors should not break tests. Match the repo's existing test layout: fresh scaffolds use tests/, while colocated src/**/*.test.ts files are also supported. Integration tests at I/O boundaries over unit tests of internals.


createMockContext options

import { createMockContext } from '@cyanheads/mcp-ts-core/testing';

createMockContext()                                           // minimal — ctx.state operations throw without tenantId
createMockContext({ tenantId: 'test-tenant' })               // enables ctx.state (tenant-scoped in-memory storage)
createMockContext({ errors: myTool.errors })                 // attaches typed ctx.fail keyed by the contract reasons
createMockContext({ sample: vi.fn().mockResolvedValue(...) }) // with MCP sampling
createMockContext({ elicit: vi.fn().mockResolvedValue(...) }) // with elicitation
createMockContext({ progress: true })                        // with task progress (ctx.progress populated)
createMockContext({ requestId: 'my-id' })                    // override request ID (default: 'test-request-id')
createMockContext({ notifyResourceListChanged: () => {} })   // with resource-list change notifier
createMockContext({ notifyResourceUpdated: (_uri) => {} })   // with resource update notifier
createMockContext({ signal: controller.signal })             // custom AbortSignal
createMockContext({ auth: { clientId: 'test', scopes: [], sub: 'test-user' } }) // with auth context
createMockContext({ uri: new URL('myscheme://item/123') })   // for resource handler testing

Read the full file on GitHub · 397 lines

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.

  1. 5d ago First seen · 397 lines · 46 tokens per session scan A 4687adf18eb6

Subscribe to this mod's changes

api-testing is a skill published in the GitHub repository wallieinformal201/pentest-mcp-server (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 46 tokens to every session and 4,226 once invoked, about $0.0002 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.