Earth

com.mireyePublished by mireye.comOfficial publisherv0.7.3Updated Nov 8, 2026

Mireye Earth: free public geospatial data, parcel enrichment, search, and cited answers.

VerifiedStreamable HTTPWeb executableLocation & LifestyleData & Analytics

Overview

AI-generated overview

Mireye Earth is a hosted MCP endpoint giving assistants free public geospatial data, parcel enrichment, search and cited answers.

What you can do
  • Enrich a location or matched parcel with preset field bundles such as power and water, each field carrying value, source, confidence and interpretation hints
  • Search public geospatial and parcel records with scalar filters, returning requested fields plus remarks and a pagination cursor
  • Fetch and Ask have their own response contracts, separate from Enrich and Search
  • A companion setup helper writes hosted MCP configuration for Claude Code, Codex and Cursor and installs a use-mireye skill
When to use it
Useful when an assistant needs cited geospatial or parcel-level facts, such as land, utility or location attributes, and you want a hosted endpoint rather than a local server. The setup helper is for wiring supported coding clients to that endpoint.
Requirements
Remote streamable HTTP endpoint at api.mireye.com with OAuth sign-in required in the client. The optional helper is a Python package run via uvx and needs a Mireye account, accepted customer terms, and a scoped setup API key supplied on standard input.
Before you install
The helper saves a scoped API key to a local credentials file and edits client configuration files, though it backs them up and preserves unrelated entries. Enrich and Search responses include billing information, so calls may incur charges. The doctor proof makes one free REST Fetch and does not verify hosted MCP OAuth, so confirm tools after signing in.

Installation

In SourceWeft

  1. Open Earth in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.mireye%2Fearth/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "earth": {
      "type": "http",
      "url": "https://api.mireye.com/mcp"
    }
  }
}

README

Mireye hosted MCP setup helper

mireye-mcp 0.7.3 configures Claude Code, Codex and Cursor to connect directly to https://api.mireye.com/mcp, and installs the use-mireye skill. The package runs no MCP server. Its default invocation refuses the retired local stdio transport; device login and local data tools are not included.

Sign in at Mireye agent setup, accept the current customer terms, copy the private setup prompt and paste it into your agent. The prompt supplies the scoped API key through standard input, never a process argument. The helper validates the account and exact setup-key identity before saving the key or changing client configuration.

bash
# The agent supplies the private key on stdin, without echoing or logging it.uvx --from mireye-mcp==0.7.3 mireye-mcp connect --all --api-key-stdin --attempt-id '<attempt-id>' --token-id '<token-id>'uvx --from mireye-mcp==0.7.3 mireye-mcp doctor --proof

connect writes native hosted configurations, without API keys or local launch commands. Restart your agent and authorize its hosted MCP connection using the client's OAuth sign-in. OAuth credentials remain managed by that client.

doctor --proof verifies the installed configuration and skill, checks the saved API key's account, and makes one free REST Fetch for elevation at 40.7128, -74.0060. It requires a finite value, ok status, source URL and timestamp before reporting the data proof. The API records the successful Fetch against the setup attempt. This proves the REST key/data path; it does not authorize or verify hosted MCP OAuth. Confirm the connected client's tools after OAuth sign-in.

Client / purposeConfigurationSkill / credentials
Claude Code~/.claude.json~/.claude/skills/use-mireye/SKILL.md
Codex~/.codex/config.toml~/.agents/skills/use-mireye/SKILL.md
Cursor~/.cursor/mcp.json~/.agents/skills/use-mireye/SKILL.md (shared with Codex)
Helper API key—~/.config/mireye-mcp/credentials.json (mode 0600)
Setup ownership—~/.config/mireye-mcp/onboarding.json

Setup preserves unrelated configuration, refuses custom conflicting entries or modified skills, and backs up changed configuration files. A process lock and content rechecks protect concurrent edits. Repeating connect reuses the saved key and files; it does not issue credentials or grant another promotional balance. An inherited shell key cannot replace an existing managed account. To switch accounts, remove the managed connection, run logout, then connect from that account's setup page. Authorize the correct account separately in the MCP client's OAuth flow.

bash
# Preview only: no key read, API requests, login save, lock or file changes.uvx --from mireye-mcp==0.7.3 mireye-mcp connect --all --dry-run# Reuse the saved key; --client can be repeated.uvx --from mireye-mcp==0.7.3 mireye-mcp connect --client codex# Read a redacted diagnostic report.uvx --from mireye-mcp==0.7.3 mireye-mcp doctor --proof --json# Remove unchanged owned entries/skills, retaining the helper API key.uvx --from mireye-mcp==0.7.3 mireye-mcp connect --all --remove# Remove the helper's saved key. --revoke also revokes its server-verified key ID.uvx --from mireye-mcp==0.7.3 mireye-mcp logout

--all skips absent supported clients; explicitly selecting an absent client fails. Existing identical manual entries remain unmanaged, including on removal. No project instructions or shell profiles are changed. Custom CODEX_HOME and CLAUDE_CONFIG_DIR locations require manual setup; use --config-home PATH for isolated tests. --base-url accepts the production API or loopback only and binds saved keys to that origin. Redirects never forward a key to another host. Legacy --api-key input remains accepted for compatibility; prefer stdin so the key cannot appear in process listings.

Native configurations follow the client documentation: Claude Code, Codex, and Cursor.

The official MCP registry entry is hosted-only. This package is not a local transport distribution, and installing it does not add a second data service.

Enrich results

The hosted mireye_enrich tool returns the same compact response as POST /v1/enrich. Each returned field contains value, source, confidence, and interpretation_hints, with unit only when defined. Failed fields are omitted. A matched parcel can return fields: {}.

Coordinates, geocode evidence, the analysis point, parcel match status and billing are included. mireye_enrich takes preset as a list of one or more bundle names, such as ["power", "water"].

mireye_search returns scalar filter values and every requested public Search or Enrich field as plain values in each match's fields, excluding top-level identity duplicates, using the matched parcel record's lat/lon pair. Every response carries remarks ([] when clean; branch on code and path) and next_cursor (null on the last page). Fetch and Ask have their own contracts. See the Enrich reference for the 525-field inventory, selectors and examples.

Source: README.md at commit 664af58

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

4
  1. v0.7.3LatestOct 22, 2026
  2. v0.7.2Oct 20, 2026
  3. v0.6.1Oct 20, 2026
  4. v0.5.0Sep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.