Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
ExplorationMaps is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Mining claim search and professional mineral exploration maps from public registries.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http explorationmaps-mcp https://www.explorationmaps.com/mcp/server
# 2 — ask your agent for something these tools do
# preview_exploration_map, search_mineral_claims, get_mapping_capabilities
ExplorationMaps costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http explorationmaps-mcp https://www.explorationmaps.com/mcp/serverReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
3 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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, loca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| map_type | string | no | The mining-specific map format to create. |
| title | string | no | Optional finished-map title. |
| subtitle | string | no | Optional subtitle shown in the map frame. |
| jurisdiction | string | no | Mineral-registry jurisdiction. |
| search | object | no | — |
| location | object | no | — |
| claim_numbers | array | no | Exact claim identifiers to map. Overrides search selection; all requested claims must be found. |
| 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. | |
| style | string | no | ExplorationMaps visual theme. |
| company | object | no | — |
| basemap | string | no | Main map basemap. Defaults by map type; geology uses the published bedrock overlay. |
| basemap_opacity | number | no | — |
| inset | object | no | — |
| neighbours | object | no | — |
| branding | object | no | — |
| facts_panel | object | no | Verified, published project facts, drawn in the project callout. claims must equal the number of mapped claims. |
| claims_callout | object | no | — |
| annotations | array | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | yes | Mineral-registry jurisdiction. |
| search_type | string | no | Search by holder/company, claim number, or claim name. |
| query | string | no | Company/holder name, claim number, or claim name. |
| bbox | array | no | Optional [minLng,minLat,maxLng,maxLat] spatial query. |
| limit | integer | no | Maximum claim summaries returned to the model. |
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.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ExplorationMaps or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish ExplorationMaps can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.