Borrowing it
Nothing to install: this file belongs to kazuph/mcp-fetch. 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/kazuph/mcp-fetch/main/CLAUDE.mdgit clone --depth 1 https://github.com/kazuph/mcp-fetchWrote 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/instructions/kazuph/mcp-fetch/claude-md)<a href="https://agentmods.dev/instructions/kazuph/mcp-fetch/claude-md"><img src="https://agentmods.dev/badge/instructions/kazuph/mcp-fetch/claude-md.svg" alt="Measured on agentmods" 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.00953 | $0.00953 |
| Opus 5 | $0.00477 | $0.00477 |
| Sonnet 5 | $0.00191 | $0.00191 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
mcp-fetch CLAUDE.md 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 8d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
mcp-fetch is a Model Context Protocol (MCP) server that provides web content fetching capabilities for AI assistants. It converts HTML pages to clean markdown using Mozilla Readability and optionally processes images using Sharp.
Development Commands
# Build TypeScript to JavaScript
npm run build
# Type checking only (recommended before commits)
npm run typecheck
# Run all quality checks (biome linting + typecheck)
npm test
# Format code using Biome
npm run format
# Lint code using Biome
npm run lint
# Build and run the server
npm run dev
# Run the compiled server
npm start
Architecture
Single-File Design
- Core logic: All functionality is in
index.ts(606 lines) - Type definitions: External module types in
types.d.ts - This is intentional - the tool has focused scope and benefits from centralized logic
Key Components
- MCP Server: Uses
@modelcontextprotocol/sdkfor protocol implementation - Content Pipeline: HTML → Readability → Markdown → Pagination
- Image Pipeline: Fetch → JPEG conversion → Vertical merging → File saving → Optional Base64 encoding
- Parameter Validation: Zod schemas with automatic type conversion from string/number unions
Dependencies Architecture
- Content Processing:
@mozilla/readability+jsdom+turndownchain - Image Processing:
sharpfor high-performance image operations - HTTP:
node-fetchfor web requests - Compliance:
robots-parserfor robots.txt checking
Code Patterns
Parameter Handling
Parameters use union types (string | number) with Zod validation for automatic type conversion:
url: z.string(),
maxLength: z.union([z.string(), z.number()]).transform(Number).default(20000),
enableFetchImages: z.union([z.string(), z.boolean()]).transform(toBool).default(false)
Error Handling
Network operations include comprehensive error handling with specific error types for different failure scenarios.
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.
- 8d ago First seen · 138 lines · 953 tokens per session scan A 8be1cb67f31a
mcp-fetch CLAUDE.md is an instructions file published in the GitHub repository kazuph/mcp-fetch (41 stars, last pushed 2mo ago), licensed MIT. It adds 953 tokens to every session, about $0.0048 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-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.