Borrowing it
Nothing to install: this file belongs to Proprius-Labs/pocketscout-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.
curl -O https://raw.githubusercontent.com/Proprius-Labs/pocketscout-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/Proprius-Labs/pocketscout-mcpWrote 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/proprius-labs/pocketscout-mcp/claude-md)<a href="https://agentmods.dev/instructions/proprius-labs/pocketscout-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/proprius-labs/pocketscout-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.
<a href="https://agentmods.dev/instructions/proprius-labs/pocketscout-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/proprius-labs/pocketscout-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01775 | $0.01775 |
| Opus 5 | $0.00888 | $0.00888 |
| Sonnet 5 | $0.00355 | $0.00355 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
pocketscout-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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PocketScout MCP
What This Is
PocketScout is a fast triage tool for drug-target binding sites — it gives an AI assistant the tools to pull together everything known about a protein's pockets (structure, chemistry, conservation, literature) into a single briefing in minutes. The flagship use case is reconnaissance before computational binder design: filling the gap between "I have a target" and "I'm running RFdiffusion."
Built with FastMCP 3.0, Python 3.11+, httpx, Pydantic v2.
Who This Is For
Drug discovery scientists (computational and bench) who need a fast binding-site briefing — whether evaluating an unfamiliar target, onboarding a new team member, screening candidates in a scouting or BD role, or preparing a target for de novo binder design. Also serves as a demonstration of domain-informed MCP server design for Anthropic's life sciences ecosystem.
Design Philosophy
-
Tool descriptions are prompt engineering. Claude reads the docstrings and Field descriptions to decide when/how to use each tool. Every description should encode scientific reasoning, not just data labels. This is where domain expertise matters most.
-
Composition over coverage. 8 tools that compose into a real workflow > 30 isolated database wrappers. The tools are ordered to reflect how expert medicinal chemists actually evaluate targets.
-
Pre-compute interpretations. Each tool returns raw data AND an
interpretationfield with scientific context. This helps Claude reason without dumping raw JSON into its context. -
Fail gracefully with useful messages. Biological databases are flaky. Missing data is informative (no ChEMBL data = untargeted = opportunity). Errors should tell the scientist what the absence means, not just "404."
-
Filter noise. Crystallization artifacts (glycerol, PEG, sulfate) pollute binding site analysis. The artifact filter list is scientifically important.
Architecture
pocketscout-mcp/
├── CLAUDE.md ← You are here
├── pyproject.toml
├── README.md ← Design rationale (important for portfolio)
├── src/pocketscout_mcp/
│ ├── server.py ← MCP server: 8 tools + 2 prompts
│ ├── models.py ← Pydantic models (field descriptions = MCP schema)
│ └── clients/ ← Async API wrappers
│ ├── base.py ← Shared HTTP client with retries
│ ├── uniprot.py ← Protein annotation, function, family
│ ├── pdb.py ← Structures, ligands, binding sites
│ ├── alphafold.py ← Structure confidence (pLDDT)
│ ├── chembl.py ← Bioactivity, competitive landscape
│ └── pubmed.py ← Literature search
├── tests/
│ └── test_clients.py
└── examples/
└── egfr_assessment.md ← Example walkthrough
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 · 118 lines · 1,775 tokens per session scan A 15b3b4073716
pocketscout-mcp CLAUDE.md is an instructions file published in the GitHub repository Proprius-Labs/pocketscout-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 1,775 tokens to every session, about $0.0089 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
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.
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).
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.