ExplorationMaps

Name: ExplorationMaps
Author: coltongriffith

Server Details

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

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 100.0% over 19 days
Last Tested: 2026-10-09 20:40
Transport: Streamable HTTP · MCP 2025-11-25
URL
Repository: coltongriffith/mapviewer2
GitHub Stars: 1

TDQS

A4.6/5.0

Scored 2026-10-01 21:40 across 3 tools

Disambiguation5/5

Each tool has a clearly distinct role: capability discovery, claim search, and map generation. There is no overlap between searching registries and previewing a map, and the descriptions reinforce the intended order of use.

Naming Consistency5/5

All three names follow a strict verb_noun snake_case pattern (get_mapping_capabilities, preview_exploration_map, search_mineral_claims). The convention is predictable and readable.

Tool Count4/5

Three tools map cleanly onto a discover-search-preview workflow, so nothing feels redundant. The set is on the thin side, but each tool earns its place for a narrowly scoped mapping service.

Completeness4/5

The core lifecycle (check capabilities, find claims, generate a shareable map) is covered with no dead ends. Minor gaps exist around saved-map retrieval or direct export/download, and advanced layouts are explicitly deferred to user-supplied data.

Available Tools

3 tools

get_mapping_capabilitiesGet ExplorationMaps mapping capabilitiesA

Read-onlyIdempotent

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
No output parameters

TDQS

A4.5/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, idempotent read. The description adds the scope of information returned but doesn't mention any specific behavioral aspects like rate limits or caching, which is acceptable given the rich annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no redundancy. The first sentence enumerates the returned information, and the second gives usage guidance. Front-loaded and precise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the zero parameters and the output schema exists, the description is complete enough. It tells the agent what to expect and when to use it. The output schema will define the exact structure of the capabilities.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero parameters, so the schema provides no parameter documentation. The description fully describes the output categories, compensating for the absence of parameters. This is above baseline 4.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it returns the map types, mineral-registry jurisdictions, context overlays, search modes, and styles supported by ExplorationMaps. This is specific and distinct from siblings, as it is about capabilities, not previewing a map or searching claims.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use this when deciding whether ExplorationMaps can fulfill a mapping request or when a jurisdiction is unclear, providing clear context for when to call it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

preview_exploration_mapCreate a mineral exploration map previewAInspect

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. Free use allows 10 previews per hour; allowance in the result reports how many remain.

ParametersJSON Schema

Name	Required	Description	Default
`inset`	No
`style`	No	ExplorationMaps visual theme.	investor_clean
`title`	No	Optional finished-map title.
`search`	No
`basemap`	No	Main map basemap. Defaults by map type; geology uses the published bedrock overlay.
`company`	No
`include`	No	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.	all
`branding`	No
`location`	No
`map_type`	No	The mining-specific map format to create.	investor
`subtitle`	No	Optional subtitle shown in the map frame.
`neighbours`	No
`annotations`	No
`facts_panel`	No	Verified, published project facts, drawn in the project callout. claims must equal the number of mapped claims.
`jurisdiction`	No	Mineral-registry jurisdiction.	bc
`claim_numbers`	No	Exact claim identifiers to map. Overrides search selection; all requested claims must be found.
`claims_callout`	No
`basemap_opacity`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`title`	Yes
`source`	Yes
`status`	Yes
`caption`	No
`alt_text`	No
`map_type`	Yes
`warnings`	Yes
`allowance`	No
`share_url`	Yes
`claims_found`	Yes
`layers_empty`	No
`layers_applied`	No
`expires_in_days`	Yes
`branding_applied`	No
`png_download_url`	No
`claims_found_primary`	No
`claims_found_neighbours`	No

TDQS

A4.9/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations (readOnly=false, destructive=false, openWorld=true), the description discloses rate limits ('10 previews per hour; allowance in the result reports how many remain'), the returned artifact (shareable URL), and hard scope boundaries (no drill/NI 43-101 output). This is materially more than the annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Seven tight sentences, front-loaded with purpose and required inputs, then data rules, feature set, exclusions, and limits. Each sentence carries distinct information with no restatement of the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, return values need not be explained, and the description still notes the URL and remaining-allowance fields. For an 18-param, zero-required, nested-object tool it covers the selection logic, constraints, and limits an agent needs before calling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 50% schema description coverage across 18 params, the description compensates well: it frames search/location/claim_numbers as the input trio, and calls out neighbours, project callout, locator inset, basemap selection, and the facts/branding rules. It does not add detail for style, branding fields, include, map_type, jurisdiction, or basemap_opacity, so a few params rely entirely on schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete verb+resource+outcome: 'Create a branded mineral exploration map from public registry claims and return a shareable URL.' It also clarifies role relative to the search sibling ('search its claims first and pass exact claim_numbers'), so an agent can tell what this tool does versus search_mineral_claims.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an entry requirement ('Provide at least one of search, location or claim_numbers'), a workflow for the specific-project case, data-integrity guidance ('never invent ownership, targets, grades or coordinates'), and an explicit when-not ('this tool does not generate drill results'). Conditions are stated rather than inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_mineral_claimsSearch mineral claims and tenureA

Read-onlyIdempotent

Inspect

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.

ParametersJSON Schema

Name	Required	Description	Default
`bbox`	No	Optional [minLng,minLat,maxLng,maxLat] spatial query.
`limit`	No	Maximum claim summaries returned to the model.
`query`	No	Company/holder name, claim number, or claim name.
`search_type`	No	Search by holder/company, claim number, or claim name.	company
`jurisdiction`	Yes	Mineral-registry jurisdiction.

Output Schema

ParametersJSON Schema

Name	Required	Description
`count`	Yes
`claims`	Yes
`source`	Yes
`returned`	Yes
`warnings`	Yes
`jurisdiction`	Yes

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish read-only, open-world, and idempotent behavior. The description adds value beyond annotations by disclosing jurisdiction-specific behavior ('Claim-name search is available for British Columbia and US BLM jurisdictions') and that returned fields depend on registry supply. It also warns that results are informational, not a legal title opinion.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, each earning its place: purpose, return values, usage instruction, and legal disclaimer. The most important information is front-loaded, with no redundancy or filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return-value detail is covered elsewhere. The description covers search modes, jurisdictional restrictions, clustering workflow, and legal limitations, giving an agent everything needed to decide when to call the tool and how to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description earns a 4 by clarifying that query and bbox can be used together or separately, and by constraining claim-name search to specific jurisdictions—context not fully captured in the schema parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Search public mineral-claim registries by holder, exact claim number, claim name, or geographic bounding box.' It also enumerates returned fields (claim number, name, holder, status, expiry, area, centroid), making the tool's scope unambiguous and clearly distinct from the mapping/capability siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives actionable guidance: 'provide query, bbox, or both' and 'Cluster results geographically before selecting a specific project.' It also includes a when-not-to-use caveat by stating results are not a legal title opinion. It does not explicitly name sibling alternatives, but the context is clear enough for correct selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

1 tool updateOct 1, 2026
- Changedpreview_exploration_map1 field changed
  - addedOutput schema / properties / png_download_url
```
Added value: +{
+  "format": "uri",
+  "type": "string"
+}
```
1 tool updateOct 1, 2026
- Changedpreview_exploration_map1 field changed
  - changedOutput schema / properties / expires_in_days / type
```
Previous value: -"integer"New value: +[
+  "integer",
+  "null"
+]
```

1 tool updateOct 1, 2026

Changedpreview_exploration_map1 field changed

addedOutput schema / properties / allowance

Added value: +{
+  "properties": {
+    "limit": {
+      "type": "integer"
+    },
+    "next_available_at": {
+      "format": "date-time",
+      "type": "string"
+    },
+    "remaining": {
+      "type": "integer"
+    },
+    "tier": {
+      "type": "string"
+    },
+    "window_seconds": {
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

2 tool updatesSep 23, 2026

Changedpreview_exploration_map3 fields changed

removedInput schema / anyOf

Removed value: -[
-  {
-    "required": [
-      "search"
-    ]
-  },
-  {
-    "required": [
-      "location"
-    ]
-  },
-  {
-    "required": [
-      "claim_numbers"
-    ]
-  }
-]

addedInput schema / properties / facts_panel / description

Added value: +"Verified, published project facts, drawn in the project callout. claims must equal the number of mapped claims."

changedInput schema / properties / include / description

Previous value: -"Available reference overlays; all enables the supported roads, settlements, labels, rail and geology overlays."New value: +"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."

Changedsearch_mineral_claims1 field changed

removedInput schema / anyOf

Removed value: -[
-  {
-    "required": [
-      "query"
-    ]
-  },
-  {
-    "required": [
-      "bbox"
-    ]
-  }
-]

1 tool updateSep 22, 2026

Changedpreview_exploration_map25 fields changed

changedInput schema / anyOf

Previous value: -[
-  {
-    "required": [
-      "search"
-    ]
-  },
-  {
-    "required": [
-      "location"
-    ]
-  }
-]New value: +[
+  {
+    "required": [
+      "search"
+    ]
+  },
+  {
+    "required": [
+      "location"
+    ]
+  },
+  {
+    "required": [
+      "claim_numbers"
+    ]
+  }
+]

addedInput schema / properties / annotations

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "label": {
+        "type": "string"
+      },
+      "lat": {
+        "type": "number"
+      },
+      "lng": {
+        "type": "number"
+      },
+      "type": {
+        "enum": [
+          "target",
+          "airstrip",
+          "camp",
+          "mine",
+          "deposit",
+          "other"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "label",
+      "lat",
+      "lng"
+    ],
+    "type": "object"
+  },
+  "maxItems": 30,
+  "type": "array"
+}

addedInput schema / properties / basemap

Added value: +{
+  "description": "Main map basemap. Defaults by map type; geology uses the published bedrock overlay.",
+  "enum": [
+    "white",
+    "light_grey",
+    "dark",
+    "terrain",
+    "topo",
+    "satellite",
+    "satellite_hybrid",
+    "hillshade",
+    "geology"
+  ],
+  "type": "string"
+}

addedInput schema / properties / basemap_opacity

Added value: +{
+  "default": 1,
+  "maximum": 1,
+  "minimum": 0,
+  "type": "number"
+}

addedInput schema / properties / branding

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "accent_color": {
+      "pattern": "^#[0-9a-fA-F]{6}$",
+      "type": "string"
+    },
+    "font": {
+      "maxLength": 80,
+      "type": "string"
+    },
+    "logo_url": {
+      "format": "uri",
+      "type": "string"
+    },
+    "logo_url_dark": {
+      "format": "uri",
+      "type": "string"
+    },
+    "primary_color": {
+      "pattern": "^#[0-9a-fA-F]{6}$",
+      "type": "string"
+    },
+    "website": {
+      "format": "uri",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / claim_numbers

Added value: +{
+  "description": "Exact claim identifiers to map. Overrides search selection; all requested claims must be found.",
+  "items": {
+    "pattern": "^[A-Za-z0-9.-]{1,40}$",
+    "type": "string"
+  },
+  "maxItems": 40,
+  "minItems": 1,
+  "type": "array",
+  "uniqueItems": true
+}

addedInput schema / properties / claims_callout

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "anchor": {
+      "enum": [
+        "auto"
+      ],
+      "type": "string"
+    },
+    "fields": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "show": {
+      "default": true,
+      "type": "boolean"
+    },
+    "source_note": {
+      "type": "string"
+    },
+    "style": {
+      "enum": [
+        "brand",
+        "technical",
+        "minimal"
+      ],
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedInput schema / properties / facts_panel

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "access": {
+      "type": "string"
+    },
+    "claims": {
+      "type": "integer"
+    },
+    "commodity": {
+      "type": "string"
+    },
+    "hectares": {
+      "type": "number"
+    },
+    "ownership": {
+      "type": "string"
+    },
+    "project": {
+      "type": "string"
+    },
+    "tickers": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / include / default

Previous value: -[
-  "claims",
-  "roads",
-  "settlements"
-]New value: +"all"

changedInput schema / properties / include / description

Previous value: -"Context layers to turn on in the finished map."New value: +"Available reference overlays; all enables the supported roads, settlements, labels, rail and geology overlays."

removedInput schema / properties / include / items

Removed value: -{
-  "enum": [
-    "claims",
-    "roads",
-    "settlements",
-    "labels",
-    "rail",
-    "geology"
-  ],
-  "type": "string"
-}

removedInput schema / properties / include / maxItems
```
Removed value: -8
```

addedInput schema / properties / include / oneOf

Added value: +[
+  {
+    "enum": [
+      "all"
+    ],
+    "type": "string"
+  },
+  {
+    "items": {
+      "enum": [
+        "claims",
+        "roads",
+        "settlements",
+        "labels",
+        "rail",
+        "geology"
+      ],
+      "type": "string"
+    },
+    "maxItems": 8,
+    "type": "array",
+    "uniqueItems": true
+  }
+]

removedInput schema / properties / include / type
```
Removed value: -"array"
```
removedInput schema / properties / include / uniqueItems
```
Removed value: -true
```

addedInput schema / properties / inset

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "basemap": {
+      "enum": [
+        "white",
+        "light_grey",
+        "dark",
+        "terrain",
+        "topo",
+        "satellite",
+        "satellite_hybrid",
+        "hillshade",
+        "geology"
+      ],
+      "type": "string"
+    },
+    "show": {
+      "default": true,
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

changedInput schema / properties / map_type / default
```
Previous value: -"claims"New value: +"investor"
```

addedInput schema / properties / neighbours

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "label_holders": {
+      "default": true,
+      "type": "boolean"
+    },
+    "max_holders": {
+      "maximum": 8,
+      "minimum": 0,
+      "type": "integer"
+    },
+    "show": {
+      "default": true,
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / alt_text
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / branding_applied
```
Added value: +{
+  "type": "object"
+}
```
addedOutput schema / properties / caption
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / claims_found_neighbours
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / claims_found_primary
```
Added value: +{
+  "type": "integer"
+}
```

addedOutput schema / properties / layers_applied

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / layers_empty

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

3 tool updatesSep 21, 2026
- First observedget_mapping_capabilities
- First observedpreview_exploration_map
- First observedsearch_mineral_claims

Related MCP Connectors

Blm Mining Claims
io.github.pipeworx-io
BLM mining claims (MLRS) — fleet #2826.
1
GreenlandAI B
ai.greenlandai
GreenlandAI: world graph & map (companies, deposits, commodities), marketplace, wallets, proofs.
Blockchain Cryptocurrency Web3 & Decentralized Tech
431
Msha Mines
io.github.pipeworx-io
MSHA mine records — search a US mine by operator or mine name, or look up
1
BoardwalkOAuth
com.boardwalkai.mcp
US pre-construction land-use filings, alerts, lists, and exports.
Real Estate Government Data
1

Related MCP Servers

usgs-mrdata
Government Data Open Data
pipeworx-io
A
license
Not graded
quality
C
maintenance
Enables searching and retrieving mineral deposit records from the Mineral Resources Data System. Provides tools for area-based commodity counts and full deposit details.
Updated 15 days ago (2026-09-26 22:11 UTC)
77 npm
MIT
RockHound
Open Data Government Data Location Services
crjiminez03
A
license
Not graded
quality
B
maintenance
Enables AI agents to query curated spatial data about Colorado rockhounding, including finding vacant mining claims near mineral occurrences and checking land access at coordinates.
Updated a month ago (2026-08-29 15:35 UTC)
1
MIT
mcp-server-blm-mlrs
Government Data Energy Open Data
GSA-TTS
F
license
A
quality
D
maintenance
Enables querying and retrieving details of U.S. BLM geothermal leases from the MLRS database, including search and single-lease lookup.
Updated 9 days ago (2026-10-02 06:13 UTC)
2
-
UrbanKit County Parcel Atlas
Government Data Open Data Location Services
urbankitstudio
A
license
A
quality
A
maintenance
Query verified parcel ArcGIS REST endpoints for 150+ US counties across all 50 states — search by owner name, APN, or address. No API key; built on public county GIS data.
Updated 21 hours ago (2026-10-10 17:12 UTC)
4
4
1,256 npm
1
MIT

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Server Details

Available Tools

Output Schema

Output Schema

Output Schema

Tool Schema Changelog

Related MCP Connectors

Related MCP Servers

Glama MCP Gateway

Resources