esri-living-atlas-mcp: Instructions file for Claude Code

CLAUDE.md

esri-living-atlas-mcp CLAUDE.md is an instructions file for Claude Code from codeforanchorage/esri-living-atlas-mcp. It costs 1,658 tokens per session, scanned A, original, MIT.

Project instructions for an MCP server that provides data from Esri's Living Atlas, a catalog of maps and geographic datasets on ArcGIS Online.

In plain words
What is it for?
Use them when developing, configuring, or running the local Living Atlas MCP server and its Python dependencies.
Why use it?
They document which ArcGIS data source and search method the project must use, reducing the risk of returning incomplete or incorrectly scoped results.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is codeforanchorage/esri-living-atlas-mcp's own configuration. It tells Claude Code how to work on esri-living-atlas-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything esri-living-atlas-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to codeforanchorage/esri-living-atlas-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/codeforanchorage/esri-living-atlas-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/codeforanchorage/esri-living-atlas-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.

agentmods badge for esri-living-atlas-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/codeforanchorage/esri-living-atlas-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/codeforanchorage/esri-living-atlas-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/codeforanchorage/esri-living-atlas-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/codeforanchorage/esri-living-atlas-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.

agentmods 80×15 button for esri-living-atlas-mcp CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/codeforanchorage/esri-living-atlas-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/codeforanchorage/esri-living-atlas-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,658 This file is loaded in full into every session.
When invoked 1,658 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01658 $0.01658
Opus 5 $0.00829 $0.00829
Sonnet 5 $0.00332 $0.00332
Haiku 4.5 $0.00166 $0.00166

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

Security

Grade A, and why

esri-living-atlas-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 11d 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 · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 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.

Living Atlas fork. This is the ESRI Living Atlas fork of the OpenContext MCP server framework ("ESRI Living Atlas MCP"). It serves ArcGIS Living Atlas of the World — Esri's curated catalog on ArcGIS Online (www.arcgis.com) — via the built-in living_atlas plugin (see config.yaml). It was adapted from the San Diego regional fork, whose arcgis plugin (ArcGIS Enterprise) remains in the tree, disabled, as the machinery it was forked from.

Data source: ArcGIS Online / Living Atlas group

Facts verified empirically against the live API (full detail + raw captures in docs/CATALOG_NOTES.md and capture/raw_curl.txt — read those before touching discovery or scoping code):

  • The Living Atlas filter is a group membership: group 47dd57c9a59d458c86d3d6b978560088 on www.arcgis.com. All catalog queries use the group content search (/sharing/rest/content/groups/<id>/search) — the only endpoint that honors the Living Atlas categories taxonomy. Do NOT scope by owner:esri* or contentstatus:public_authoritative (both are wrong).
  • categories semantics: one param holding a JSON array = OR; the param repeated = AND. Category paths prefix-match. The taxonomy lives in category-set item 1ad6b64fe4e1428a8f182dd6010fc2c9 (/data), not in the group's categorySchema (which only delegates).
  • Type filters go inside q: q=(wildfire) (type: "Deep Learning Package").
  • Premium markers: typeKeywords containing Requires Subscription (or Requires Credits). Service-level token demands surface as HTTP 401/403 or in-body ArcGIS error codes 498/499 — always map these to the clean subscriber-content message, never a raw error. No tokens, ever; premium access is permanently out of scope.
  • Membership enforcement: query tools accept only Living Atlas item IDs, and get_dataset verifies group membership (q=id:<id> against the group) before resolving any service URL. This is deliberate anti-laundering — don't add service-URL parameters to tools.
  • Live catalog, no snapshot: ~10,800 items, updated continuously. Caching TTLs: search ~10 min, item metadata/schemas/taxonomy ~1 h. Single retry with 0.5s backoff; timeouts and outages must produce honest "upstream unavailable / not an empty result" errors.
  • Feature queries: standard /FeatureServer/<N>/query, paginate with resultOffset. Beware layer-specific pathology: some huge national layers (e.g. USA Structures 0ec8512a…) reject ALL spatial queries server-side after ~55s.
  • Spatial reference: WGS84 in/out everywhere (inSR=4326, outSR=4326).
  • Attribution: pass each item's accessInformation (credits) through in tool responses; providers include federal agencies and NGOs, not just Esri.

Read the full file on GitHub · 89 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. 11d ago First seen · 89 lines · 1,658 tokens per session scan A ab1513f61a29

Subscribe to this mod's changes

esri-living-atlas-mcp CLAUDE.md is an instructions file published in the GitHub repository codeforanchorage/esri-living-atlas-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 1,658 tokens to every session, about $0.0083 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

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

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,126 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,469 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