What is demandsphere-mcp CLAUDE.md?

Project instructions for an MCP server, a standard way for AI assistants to use external tools, that connects to DemandSphere search and AI-visibility data. They explain the project layout, commands, tests, and coding rules.

Use them when developing, testing, formatting, or running the DemandSphere MCP server in Python.

They give a coding agent the project context it needs to make consistent changes and run the right checks. This avoids guessing how the server is organised or tested.

How DemandSphereDev/demandsphere-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to DemandSphereDev/demandsphere-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/DemandSphereDev/demandsphere-mcp/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/DemandSphereDev/demandsphere-mcp

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/demandspheredev/demandsphere-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/demandspheredev/demandsphere-mcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/demandspheredev/demandsphere-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/demandspheredev/demandsphere-mcp/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/demandspheredev/demandsphere-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/demandspheredev/demandsphere-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 997 This file is loaded in full into every session.

When invoked 997 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00997	$0.00997
Opus 5	$0.00498	$0.00498
Sonnet 5	$0.00199	$0.00199
Haiku 4.5	$0.00100	$0.00100

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

Security

Grade A, and why

demandsphere-mcp 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 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.

CLAUDE.md · 74 lines

How it starts

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

CLAUDE.md

Agent rules and conventions for demandsphere-mcp. Tools using the AGENTS.md convention (Codex, Cursor, Aider, etc.) should also read this file — AGENTS.md is a stub that points here.

Project snapshot

Public MCP (Model Context Protocol) server that brokers the DemandSphere search-intelligence API (v5.0 SERP analytics + v5.1 GenAI visibility) to AI assistants. Python 3.11+, MIT-licensed, distributed via GitHub. PyPI publishing is deferred to Phase 2.

Run & test commands

uv sync --extra dev                     # install dev deps
uv run pytest                           # run tests
uv run ruff check src/ tests/           # lint
uv run ruff format src/ tests/          # format
uv run demandsphere-mcp                 # run server (stdio)

Architecture map

src/demandsphere_mcp/server.py — MCP server entry point, tool/prompt/resource registration
src/demandsphere_mcp/config.py — settings loaded from env vars and ~/.config/demandsphere/config.json
src/demandsphere_mcp/client.py — async HTTP client and token-bucket rate limiter
src/demandsphere_mcp/tools/ — one file per domain:
- sites.py — site discovery (v5.0)
- keywords_v50.py — SERP analytics (v5.0)
- genai_v51.py — GenAI visibility (v5.1)
- brands_v51.py — brand management (v5.1)
- chatgpt_compat.py — ChatGPT Deep Research search/fetch
- prompts.py — MCP Prompts (workflow templates)
- resources.py — MCP Resources (parameter discovery)
- utils.py — error handling, validation, hint builders

Code conventions

Type hints required on all public APIs — we ship py.typed
Ruff target py311, line length 100
Async HTTP via httpx.AsyncClient only — never requests
All schemas via pydantic v2
New tools live in src/demandsphere_mcp/tools/<domain>.py and register in server.py

Testing rules

Every new tool needs tests in tests/test_<name>.py
No real API calls — mock httpx (see tests/test_core.py for patterns)
Async tests use pytest-asyncio configured with asyncio_mode = "auto" — no per-test decorator needed
Unit tests cover validators, response shaping, and error paths
Integration-style tests for multi-tool flows live in test_consolidated.py

Read the full file on GitHub · 74 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.

9d ago First seen · 74 lines · 997 tokens per session scan A ba2d0b2867e2

Subscribe to this mod's changes

demandsphere-mcp CLAUDE.md is an instructions file published in the GitHub repository DemandSphereDev/demandsphere-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 997 tokens to every session, about $0.0050 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.

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.

vercel/next.js · 7,296 tokens

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,153 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

demandsphere-mcp: Instructions file for Claude Code