mcp-server CLAUDE.md

Repository instructions for developing an MCP server that gives AI assistants access to Shape blockchain data. MCP is a standard way for assistants to call external tools and services.

In plain words
What is it for?
For starting, building, and running the server; checking or fixing lint and formatting; and understanding its blockchain clients, contracts, and configuration.
Why use it?
It puts the project's development commands, architecture, configuration, and code-quality rules in one place for coding agents.

Instructions file

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 instructions/shape-network/mcp-server/claude-md
Clone the repo
git clone --depth 1 https://github.com/shape-network/mcp-server
Per session 855 This file is loaded in full into every session.
When invoked 855 The same file — it is already loaded in full.
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 $0.00855 $0.00855
Opus 5 $0.00428 $0.00428
Sonnet 5 $0.00171 $0.00171
Haiku 4.5 $0.00085 $0.00085

Measured 2d ago against content hash c596a4f6a573, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

CLAUDE.md · 109 lines

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 xmcp
  • yarn start - Start production server from dist/

Code Quality

  • yarn lint - Run ESLint on src/ directory
  • yarn lint:fix - Auto-fix ESLint issues
  • yarn lint:check - Run lint with max warnings = 0 (strict mode)
  • yarn format - Format code with Prettier
  • yarn 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 Redis
  • addresses.ts - Contract addresses for gasback and stack contracts on both networks
  • types.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 simulation
  • network/ - Chain status monitoring
  • nft/ - Collection analytics and ownership data
  • stack/ - Achievement tracking system

Infrastructure

  • utils/cache.ts - Redis caching layer with fallback for when Redis is unavailable
  • abi/ - Contract ABIs for gasback and stack contracts
  • middleware.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 */
}

Read the full file on GitHub · 109 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. 2d ago First seen · 109 lines · 855 tokens per session scan A c596a4f6a573

Subscribe to this mod's changes

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.

Related

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.

openai/codex · 5,182 tokens

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

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens

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.

langchain-ai/langchain · 4,345 tokens