ExplorationMaps MCP server
online · 100% uptimeio.github.coltongriffith/explorationmaps·v1.1.1Mining claim search and professional mineral exploration maps from public registries.
0 stars
Reviews
Write oneNobody has reviewed ExplorationMaps yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
ExplorationMaps tools (3, 1 write)
write = sends, deletes, buys or postsget_mapping_capabilitiesFreeReturn the map types, mineral-registry jurisdictions, context overlays, search modes, and styles supported by ExplorationMaps. Use this when deciding whether ExplorationMaps can fulfill a mapping request or when a jurisdiction is unclear.
preview_exploration_mapwrite actionFreeCreate a branded mineral exploration map from public registry claims and return a shareable URL. Provide at least one of search, location or claim_numbers. For a specific project, search its claims first and pass exact claim_numbers. Supply published facts and branding when known; never invent ownership, targets, grades or coordinates. Supports separate neighbouring claims, a project callout, locator inset, and map basemap selection. Drill and NI 43-101 layouts require user-supplied data or qualified review; this tool does not generate drill results. Free use allows 10 previews per hour; allowance in the result reports how many remain.
search_mineral_claimsFreeSearch public mineral-claim registries by holder, exact claim number, claim name, or geographic bounding box; provide query, bbox, or both. Claim-name search is available for British Columbia and US BLM jurisdictions. Returns claim number as a string, name, holder, status, expiry, area and centroid when the registry supplies them. Cluster results geographically before selecting a specific project. Results are informational, not a legal title opinion or survey.
Public scan report
scanner v0.1.10 · 2026-10-30 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 717ms20/20
- Tool poisoning3 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
How ExplorationMaps compares
Against every graded Web search MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 81/100
- higher than 67% of 3,470 Web search servers
- Tools
- 3
- the typical Web search server has 5
- Tools that change things
- 33%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote Web search server answers 100%
- Response time
- 294 ms
- faster than 52% of 2,238 Web search servers
What its tools let an agent do: 2 read · 1 change
Release history: 2 versions in the registry since 2026-09-21, latest 2026-09-23, typically one every 2 days.
Install ExplorationMaps in Claude Code, Cursor or VS Code
claude mcp add --transport http explorationmaps https://www.explorationmaps.com/mcp/server
What the publisher says
From the ExplorationMaps repository's README, as published. We do not edit it. Read it on GitHub
Exploration Maps
Browser-based map builder for mineral exploration: search provincial claim registries, import drill/geology data, style investor-ready maps, and export them as PNG/SVG/PDF. Live at explorationmaps.com.
Stack
(see scripts/generate-blog.js and scripts/pseo/)
- Frontend: React 18 + Vite 5 single-page app (src/), Leaflet map engine
- Backend: Supabase (auth, Postgres, RLS) + Vercel serverless functions (api/)
- Static marketing content: generated blog + company pages under public/
Requirements
- Node 20+ (Vite 5 requirement; dev/CI verified on Node 20/22)
- npm (a package-lock.json is committed — use npm ci for reproducible installs)
Development
npm ci # install exactly the locked dependencies
cp .env.example .env # fill in the VITE_ variables (see below)
npm run dev # Vite dev server on http://localhost:5173The serverless functions under api/ run on Vercel. For full-stack local work use vercel dev; with plain npm run dev the claims search and analytics endpoints are absent (the UI degrades gracefully).
Commands
Environment variables
Documented in .env.example. Summary:
Public (VITE — compiled into the client bundle, never secret):**
(production-required; without them auth/cloud features disable themselves)
- VITESUPABASEURL, VITESUPABASEANON_KEY — Supabase project + anon key
authorization is server-side (adminusers table + isadmin())
- VITEADMINEMAIL — controls admin dashboard visibility only; real
Server-only secrets (set in Vercel, never referenced by client code):
Production-required once migration 20260710000004 is applied.
- SUPABASESERVICEROLE_KEY — used by /api/track for analytics ingestion.
production via the x-admin-secret header.
- ADMINAPISECRET — optional; unlocks the claims-API diagnostic modes in
VITE_-prefixed values are used as fallbacks by api/claims.js (Quebec) and api/track.js.
- SUPABASEURL / SUPABASEANON_KEY — optional server-side aliases; the
STRIPEPRICEYEARLY_ID — Pro-subscription billing (see docs/billing.md). Until set, billing endpoints return 503 and all plan checks fail open — safe to deploy the code before configuring Stripe.
- STRIPESECRETKEY, STRIPEWEBHOOKSECRET, STRIPEPRICEMONTHLY_ID,
Architecture notes
Tenure Monitor (/tenure-monitor)
Watches a saved portfolio of B.C. mineral tenures: days remaining against each claim's good-to-date, email reminders, change detection, and one-click hand-off into the map editor. Read-only with respect to government transactions — it never touches MTO on a user's behalf.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
ExplorationMaps: common questions
- Is ExplorationMaps MCP server safe?
- Mostly: it is graded B (81/100). Read the ExplorationMaps safety report
- How do I install ExplorationMaps?
- It runs remotely at www.explorationmaps.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does ExplorationMaps need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is ExplorationMaps maintained?
- The last commit was 6 days ago (2026-10-29). The latest release is v1.1.1.
- Is ExplorationMaps up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of ExplorationMaps?
- Servers from other publishers that do the same job: GitHits MCP server, Google Maps MCP Server and Papersgpt For Zotero MCP server.
- How does ExplorationMaps compare with other Web search MCP servers?
- safety score 81/100 (higher than 67% of 3,470 Web search servers); tools 3 (the typical Web search server has 5); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to ExplorationMaps
Same job from other publishers: the closest match first, then the best rated.
GitHitsSearch public open-source code, documentation, metadata, vulnerabilities, changelogs, and examples.not reviewedEstablishedA- Google Maps MCP Server18 Google Maps tools for AI agents — geocode, search, directions, weather, and more.not reviewedEstablishedB
- Papersgpt For ZoteroProfessional AI research tool for Zotero: chat with PDFs, whole-library search, Literature Radar, AutoPilot. 30+ LLMs or local models; built-in MCP server.not reviewedEstablishedB
- Ref ToolsToken-efficient search for coding agents over public and private documentation.not reviewedEstablishedA
- Apple MapsSearch places, estimate routes, and build Apple Maps links on macOS.not reviewedEstablishedA