# ExplorationMaps (remote · www.explorationmaps.com)

Mining claim search and professional mineral exploration maps from public registries.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `www.explorationmaps.com`: 73/100 (this document), [markdown](https://verifymcp.io/servers/coltongriffith-explorationmaps/mcp-server.md), [page](https://verifymcp.io/servers/coltongriffith-explorationmaps/mcp-server)

## Channel facts

- Endpoint: `https://www.explorationmaps.com/mcp/server`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 797 tokens (~265/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 61% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the ExplorationMaps MCP server?

ExplorationMaps is a hosted endpoint at https://www.explorationmaps.com/mcp/server, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http coltongriffith-explorationmaps 'https://www.explorationmaps.com/mcp/server'
```

### Cursor

```json
{
  "mcpServers": {
    "coltongriffith-explorationmaps": {
      "url": "https://www.explorationmaps.com/mcp/server"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "coltongriffith-explorationmaps": {
      "type": "http",
      "url": "https://www.explorationmaps.com/mcp/server"
    }
  }
}
```

### Codex

```toml
[mcp_servers.coltongriffith-explorationmaps]
url = "https://www.explorationmaps.com/mcp/server"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "coltongriffith-explorationmaps": {
      "type": "remote",
      "url": "https://www.explorationmaps.com/mcp/server",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add coltongriffith-explorationmaps --url 'https://www.explorationmaps.com/mcp/server' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  coltongriffith-explorationmaps:
    url: "https://www.explorationmaps.com/mcp/server"
```

### Netclaw

```json
{
  "McpServers": {
    "coltongriffith-explorationmaps": {
      "Transport": "http",
      "Url": "https://www.explorationmaps.com/mcp/server"
    }
  }
}
```

### Vellum

```bash
assistant mcp add coltongriffith-explorationmaps -t streamable-http -u 'https://www.explorationmaps.com/mcp/server'
```

### Other

```json
{
  "mcpServers": {
    "coltongriffith-explorationmaps": {
      "type": "http",
      "url": "https://www.explorationmaps.com/mcp/server"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 72, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “preview_exploration_map” rewrote its description, which is the text the model reads
- [security] Tool “search_mineral_claims” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 154 → 265
- [functional regression] Tool coverage: 79% → 61%
- [functional regression] Schema quality: 154 → 239
- [functional regression] Tool coverage: 79% → 57%
- [functional] Server version: 1.1.0 → 1.1.1
- [functional] Server version: 1.0.0 → 1.1.0
- [cosmetic] “preview_exploration_map” added an optional parameter “annotations”
- [cosmetic] “preview_exploration_map” added an optional parameter “basemap”
- [cosmetic] “preview_exploration_map” added an optional parameter “basemap_opacity”
- [cosmetic] “preview_exploration_map” added an optional parameter “branding”
- [cosmetic] “preview_exploration_map” added an optional parameter “claim_numbers”
- [cosmetic] “preview_exploration_map” added an optional parameter “claims_callout”
- [cosmetic] “preview_exploration_map” added an optional parameter “facts_panel”
- [cosmetic] “preview_exploration_map” added an optional parameter “inset”
- [cosmetic] “preview_exploration_map” added an optional parameter “neighbours”
- [cosmetic] “preview_exploration_map” reworded the description of “facts_panel”
- [cosmetic] “preview_exploration_map” reworded the description of “include”

### 2026-09-22 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-21 (score 73)

First indexed and scored.

## MCP tools (3)

### `preview_exploration_map` (~373 tokens)

Create a mineral exploration map preview

Create 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.

Input parameters:

- `annotations` (array)
- `basemap` (string): Main map basemap. Defaults by map type; geology uses the published bedrock overlay.
- `basemap_opacity` (number)
- `branding` (object)
- `claim_numbers` (array): Exact claim identifiers to map. Overrides search selection; all requested claims must be found.
- `claims_callout` (object)
- `company` (object)
- `facts_panel` (object): Verified, published project facts, drawn in the project callout. claims must equal the number of mapped claims.
- `include`: Reference overlays. "all" enables those that suit the basemap: labels and rail always, roads/settlements only on white or light_grey, geology except on satellite. Pass a list to choose exactly.
- `inset` (object)
- `jurisdiction` (string): Mineral-registry jurisdiction.
- `location` (object)
- `map_type` (string): The mining-specific map format to create.
- `neighbours` (object)
- `search` (object)
- `style` (string): ExplorationMaps visual theme.
- `subtitle` (string): Optional subtitle shown in the map frame.
- `title` (string): Optional finished-map title.

Output parameters:

- `alt_text` (string)
- `branding_applied` (object)
- `caption` (string)
- `claims_found` (integer)
- `claims_found_neighbours` (integer)
- `claims_found_primary` (integer)
- `expires_in_days` (integer)
- `layers_applied` (array)
- `layers_empty` (array)
- `map_type` (string)
- `share_url` (string)
- `source` (string)
- `status` (string)
- `title` (string)
- `warnings` (array)

### `search_mineral_claims` (~183 tokens)

Search mineral claims and tenure

Search 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.

Input parameters:

- `bbox` (array): Optional [minLng,minLat,maxLng,maxLat] spatial query.
- `jurisdiction` (string, required): Mineral-registry jurisdiction.
- `limit` (integer): Maximum claim summaries returned to the model.
- `query` (string): Company/holder name, claim number, or claim name.
- `search_type` (string): Search by holder/company, claim number, or claim name.

Output parameters:

- `claims` (array)
- `count` (integer)
- `jurisdiction` (string)
- `returned` (integer)
- `source` (string)
- `warnings` (array)

### `get_mapping_capabilities` (~52 tokens)

Get ExplorationMaps mapping capabilities

Return 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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/coltongriffith-explorationmaps/mcp-server#diagnostics

## Score history

- 2026-09-25: 73
- 2026-09-24: 72
- 2026-09-23: 72
- 2026-09-22: 73
- 2026-09-21: 73

## Common questions

### What is the ExplorationMaps MCP server?

ExplorationMaps is an MCP server listed in the public MCP registry as io.github.coltongriffith/explorationmaps. Mining claim search and professional mineral exploration maps from public registries. This page covers its hosted endpoint (https://www.explorationmaps.com/mcp/server).

### Is the ExplorationMaps MCP server safe to use?

ExplorationMaps scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ExplorationMaps MCP server expose?

ExplorationMaps exposes 3 tools: preview_exploration_map, search_mineral_claims, get_mapping_capabilities. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.

### Does the ExplorationMaps MCP server require authentication?

No. We connected to ExplorationMaps without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ExplorationMaps MCP server still maintained?

ExplorationMaps is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.explorationmaps.com/mcp/server
- Repository: https://github.com/coltongriffith/mapviewer2
- Website: https://www.explorationmaps.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/coltongriffith-explorationmaps/mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/coltongriffith-explorationmaps/mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/coltongriffith-explorationmaps/mcp-server