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.
npx agentmods add instructions/shape-network/mcp-server/claude-mdgit clone --depth 1 https://github.com/shape-network/mcp-serverWhat 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.00855 | $0.00855 |
| Opus 5 | $0.00428 | $0.00428 |
| Sonnet 5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
mcp-server 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 2d 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 — 109 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.
Development Commands
Core Development
yarn dev- Start development server (runs at http://localhost:3002/mcp)yarn build- Build the project using xmcpyarn start- Start production server from dist/
Code Quality
yarn lint- Run ESLint on src/ directoryyarn lint:fix- Auto-fix ESLint issuesyarn lint:check- Run lint with max warnings = 0 (strict mode)yarn format- Format code with Prettieryarn format:check- Check if code is properly formatted
Architecture Overview
This is MCP server based on xmcp (https://xmcp.dev/docs) that provides AI assistants with access to Shape blockchain data. The architecture follows a modular tool-based design:
Core Components
Configuration & Clients (src/)
config.ts- Environment-based configuration (chain ID, API keys, RPC URLs)clients.ts- Viem RPC clients for Shape mainnet/testnet and Ethereum mainnet, plus Alchemy SDK and Redisaddresses.ts- Contract addresses for gasback and stack contracts on both networkstypes.ts- TypeScript types for all tool outputs and error responses
Tool Architecture (src/tools/)
The server uses a category-based tool organization:
gasback/- Creator earnings analysis and reward simulationnetwork/- Chain status monitoringnft/- Collection analytics and ownership datastack/- Achievement tracking system
Infrastructure
utils/cache.ts- Redis caching layer with fallback for when Redis is unavailableabi/- Contract ABIs for gasback and stack contractsmiddleware.ts- Express middleware (currently minimal)
Tool Pattern
Each tool follows this structure:
export const schema = {
/* Zod validation schema */
};
export const metadata = {
name: string,
description: string,
annotations: {
/* Tool metadata including cache TTL, categories, etc */
},
};
export default async function toolName(params) {
/* Implementation */
}
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.
- 2d ago First seen · 109 lines · 855 tokens per session scan A c596a4f6a573
mcp-server CLAUDE.md is an instructions file published in the GitHub repository shape-network/mcp-server (7 stars, last pushed 1y ago), licensed MIT. It adds 855 tokens to every session, about $0.0043 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 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
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.