ExplorationMaps MCP server
Commit Nov 9, 2026Lets an AI client search provincial mineral claim registries, import geological data, and generate professional exploration maps.
Also known as coltongriffith/mapviewer2, mapviewer2
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.1.1
- Last commit
- Nov 9, 2026
- License
- —
What is ExplorationMaps MCP?
ExplorationMaps lets an AI client search provincial mineral claim registries, import geological data, and generate professional exploration maps.
Summary generated from the project's README
About ExplorationMaps MCP server
Geologists and mineral exploration professionals can build professional, investor-ready maps by searching provincial claim registries and importing geological data. This tool allows users to visualize drill traces, geology, and tenure information through a browser-based interface. It supports various data formats including CSV, GeoJSON, zipped shapefiles, KML, KMZ, and georeferenced images.
Users can manage mineral portfolios using the Tenure Monitor to track B.C. mineral tenures and receive email reminders for upcoming deadlines. The system integrates with multiple data sources, including ArcGIS services for Ontario, Saskatchewan, Manitoba, Newfoundland and Labrador, and Yukon, as well as a synced mirror for Quebec. For US-based exploration, it provides access to federal BLM MLRS claims for eleven western states.
Setup requires a Supabase project for authentication and cloud storage, with specific environment variables like VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY. While local projects are stored in the browser via localStorage, a Pro subscription via Stripe is required for full cloud migration and advanced features. Maps can be shared via unique random tokens and exported as PNG, SVG, or PDF files.
What you can do with it
- 1Monitor mineral tenure deadlinesTrack days remaining against B.C. mineral claims to ensure they remain in good standing.
- 2Import drill and geology dataUpload drill traces and geological information using CSV or shapefiles to visualize them on a map.
- 3Create investor-ready map exportsGenerate high-quality visual assets for presentations in various professional formats.
Written from the project's README. Every use case is checked against a quote from it.
How to install ExplorationMaps MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ExplorationMaps MCP in Claude Code
$ claude mcp add --transport http mapviewer2 https://www.explorationmaps.com/mcp/serverInstall ExplorationMaps MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mapviewer2": {
"url": "https://www.explorationmaps.com/mcp/server"
}
}
}Install ExplorationMaps MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mapviewer2": {
"type": "http",
"url": "https://www.explorationmaps.com/mcp/server"
}
}
}Install ExplorationMaps MCP in VS Code CLI
$ code --add-mcp '{"name":"mapviewer2","type":"http","url":"https://www.explorationmaps.com/mcp/server"}'Install ExplorationMaps MCP in Codex
$ codex mcp add mapviewer2 --url https://www.explorationmaps.com/mcp/serverInstall ExplorationMaps MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mapviewer2] url = "https://www.explorationmaps.com/mcp/server"
Install ExplorationMaps MCP in Gemini CLI
$ gemini mcp add -s user --transport http mapviewer2 https://www.explorationmaps.com/mcp/serverInstall ExplorationMaps MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mapviewer2": {
"url": "https://www.explorationmaps.com/mcp/server",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablecoltongriffith/mapviewer2 is public and reachablegithub.com/coltongriffith/mapviewer2 ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-09github.com/coltongriffith/mapviewer2 ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 179 msPass
README
View on GitHubExploration 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
- 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/(seescripts/generate-blog.jsandscripts/pseo/)
Requirements
- Node 20+ (Vite 5 requirement; dev/CI verified on Node 20/22)
- npm (a
package-lock.jsonis committed — usenpm cifor 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:5173
The 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
| Command | What it does |
|---|---|
npm run dev |
Vite dev server |
npm run build |
Generates the blog, builds to dist/, copies the admin shell |
npm test |
Vitest run (CI mode) |
npm run test:watch |
Vitest watch mode |
npm run pseo:fixture |
pSEO company-pages pipeline against fixture data |
Environment variables
Documented in .env.example. Summary:
Public (VITE_ — compiled into the client bundle, never secret):
VITE_SUPABASE_URL,VITE_SUPABASE_ANON_KEY— Supabase project + anon key (production-required; without them auth/cloud features disable themselves)VITE_ADMIN_EMAIL— controls admin dashboard visibility only; real authorization is server-side (admin_userstable +is_admin())
Server-only secrets (set in Vercel, never referenced by client code):
SUPABASE_SERVICE_ROLE_KEY— used by/api/trackfor analytics ingestion. Production-required once migration20260710000004is applied.ADMIN_API_SECRET— optional; unlocks the claims-API diagnostic modes in production via thex-admin-secretheader.SUPABASE_URL/SUPABASE_ANON_KEY— optional server-side aliases; theVITE_-prefixed values are used as fallbacks byapi/claims.js(Quebec) andapi/track.js.STRIPE_SECRET_KEY,STRIPE_WEBHOOK_SECRET,STRIPE_PRICE_MONTHLY_ID,STRIPE_PRICE_YEARLY_ID— Pro-subscription billing (seedocs/billing.md). Until set, billing endpoints return 503 and all plan checks fail open — safe to deploy the code before configuring Stripe.
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.
- Data: a mirror of DataBC's
MTA_ACQUIRED_TENURE_SVWlayer, loaded byscripts/tenure-sync/from GitHub Actions (nightly full + twice-daily targeted). A partial or failed government response aborts without writing, so a bad day at the province cannot damage stored portfolios. - Reminders:
scripts/tenure-alerts/, daily. De-duplication is a unique database constraint rather than application logic. - Deadlines are computed in
America/Vancouverthroughout (src/utils/tenureDates.js), never in the browser's timezone. - Developer docs:
docs/tenure-monitor.md. User help:docs/tenure-monitor-help.md.
Serverless APIs (api/)
api/claims.js— multi-province claims search proxy (BC WFS, ArcGIS provinces ON/SK/MB/NL/YT, Quebec via a self-hosted Supabase table). Full pagination with honestmeta: { totalKnown, returned, truncated, pagesFetched, provider }; rate-limited; CORS-restricted; sanitized errors.api/bc-claims.js— BC-only WFS proxy (nearby-claims bbox + legacy search).api/tenure-search.js— Tenure Monitor search over the Exploration Maps mirror of the B.C. mineral tenure registry (tenure number, pasted list, owner name, client number, map extent, geometry). Anonymous-safe, rate-limited, and every response states when the mirror was last synchronized. Reads with the ANON key under the public-read policy, never the service role.api/track.js— all analytics ingestion (page views, live-presence pings, product/search events, landing clicks, leads). Enforces an event-name allowlist, payload size/depth limits, and session-id shape; derives geo from edge headers (never the body); resolves user identity from a verified Supabase access token; writes with the service role; rate-limits per IP. WithoutSUPABASE_SERVICE_ROLE_KEYit accepts-and-drops so analytics can never break the app. Identified automated browsers are dropped before any write. Admin reports also exclude admin accounts and browsers marked internal; opening the admin dashboard marks that browser, while?em_internal=1and?em_internal=0provide an explicit set/clear control.api/stripe-checkout.js/api/stripe-portal.js/api/stripe-webhook.js— Pro-subscription billing (Stripe Checkout + customer portal + the signature-verified webhook that syncspublic.user_plans). Grandfathered accounts (pre-launch) are never downgraded. Seedocs/billing.md.api/_lib/— shared helpers (pagination, request guards, esri→GeoJSON); the underscore path means Vercel does not expose them as endpoints.
Shared maps
Share links are /map/<id> where <id> is a client-generated
crypto.randomUUID() (a 122-bit random token). Reads go through the
get_shared_map(share_id) RPC — table-level SELECT is revoked, so
shared_maps cannot be enumerated from the public client. Old links keep
working: the id remains the lookup key.
Authentication & admin
Supabase auth (magic-link default, password fallback). Admin access is a row
in public.admin_users checked by is_admin() inside SECURITY DEFINER
reporting functions; all definer functions have a pinned search_path and
explicit execute grants. To add an admin:
insert into public.admin_users (user_id, note)
select id, 'added by <you>' from auth.users where email = '<email>';
Local project storage
src/utils/projectStorage.js: projects + the working draft live in
localStorage, deflate-compressed (gz1: prefix), with a schema version and
deterministic migrations. Corrupted records are preserved under a
.recovery key (never auto-deleted) and surfaced with manual export/discard
helpers. Writes return structured results — the UI never claims success on a
failed write. On sign-in, local projects migrate to the cloud with
per-project status + retry (src/utils/cloudMigration.js).
Import formats
CSV (RFC 4180 via Papa Parse; auto-detected lat/long columns, plus azimuth,
dip and length for drill traces), GeoJSON (validated), zipped shapefiles,
loose .shp/.dbf/.prj/.shx sets (the .prj is honored — projected files are
reprojected to WGS84 via proj4), KML, KMZ (bounded: entry count, uncompressed
size, path traversal), and georeferenced images (.png/.jpg/.gif/.webp with
a world file or typed-in edges, lat/long or UTM; resampled to 2048 px and
stored in the project). Published tile ({z}/{x}/{y}) and WMS services can
be added as layers under Reference Overlays.
Claim registries
Canada: BC (WFS), Ontario/Saskatchewan/Manitoba/Newfoundland &
Labrador/Yukon (official ArcGIS services), Quebec (weekly-synced Supabase
mirror). United States: federal BLM MLRS claims for 11 western states,
behind VITE_ENABLE_US_CLAIMS — federal claims only, no state-managed
tenure (Alaska state claims not included); boundaries are generalized BLM
representations, not legal surveys. See docs/us-claims.md for the data
source, field mapping, and the post-deploy verification checklist.
Database migrations
Timestamped, additive migrations live in supabase/migrations/. The legacy
supabase-*.sql files in the repo root are the historical hand-run setup
scripts — they document existing production state; new changes go in
supabase/migrations/ only.
Apply order matters — two migrations are deploy-coupled:
| Step | Action | When |
|---|---|---|
| 1 | 20260710000001_shared_map_lookup_rpc.sql |
Any time (additive) |
| 2 | 20260710000003_live_pings_read_lockdown.sql |
Any time (the deployed app never reads live_pings) |
| 3 | 20260710000005_admin_authorization.sql |
Any time (additive; seeds the current admin) |
| 4 | Deploy the frontend (uses get_shared_map + /api/track) and set SUPABASE_SERVICE_ROLE_KEY in Vercel |
— |
| 5 | 20260710000002_shared_maps_lockdown.sql |
Only after step 4 |
| 6 | 20260710000004_analytics_ingest_lockdown.sql |
Only after step 4 |
Each migration header includes rollback instructions. After applying, verify
RLS as an anonymous client, a normal authenticated user, and the admin —
verification queries are embedded in ...000005.
20260901000001_shared_rate_limit.sql is additive and can be applied any
time, but until it is, the cross-instance rate limiter in api/_lib/guard.js
has nothing to call and fails open (only the per-instance limiter applies).
The send-welcome edge function must also be redeployed
(supabase functions deploy send-welcome) to pick up its lead-row check.
Deployment & rollback
Pushes to main deploy via Vercel (npm run build → dist/, plus api/
functions). Rollback = redeploy the previous Vercel deployment (instant);
if a deploy-coupled migration was applied after the deploy being rolled
back, also run the rollback SQL from that migration's header.
Testing
Vitest + React Testing Library (tests/, config in vitest.config.js).
Coverage focuses on regression protection: save/autosave race conditions,
claims request ordering/cancellation, provider pagination, shapefile
projection + CSV/GeoJSON parsing, storage failure/corruption handling,
local→cloud migration retries, API hardening, ArcGIS geometry conversion,
and shared-map access.
ExplorationMaps MCP questions
How do I add ExplorationMaps MCP to Claude Code?
Run claude mcp add --transport http mapviewer2 https://www.explorationmaps.com/mcp/server in your terminal. Add --scope user to make it available in every project.
How do I add ExplorationMaps MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Does the Tenure Monitor interact with government systems?
No, the Tenure Monitor is read-only and does not perform transactions on a user's behalf with the MTO.
Which claim registries are supported?
It supports Canadian registries (BC, Ontario, Saskatchewan, Manitoba, Newfoundland & Labrador, Yukon, and Quebec) and US federal BLM MLRS claims.