MCP server for Mireye Earth — federal-source-cited geospatial data for any MCP-aware agent.
Developed in a private monorepo. This repository (Mireye-Labs/mireye-earth-mcp) is the published source of the PyPI package, snapshot-synced on every release. Issues and PRs are welcome here (changes are applied upstream and re-synced; the test suite runs in the monorepo); releases land via PyPI. Expose Mireye Earth's and endpoints to MCP clients that need a local stdio adapter (Claude Desktop,…
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Developed in a private monorepo. This repository (Mireye-Labs/mireye-earth-mcp) is the published source of the PyPI package, snapshot-synced on every release. Issues and PRs are welcome here (changes are applied upstream and re-synced; the test suite runs in the monorepo); releases land via PyPI. Expose Mireye Earth's and endpoints to MCP clients that need a local stdio adapter (Claude Desktop, Cursor, custom agents built on the Python SDK) as native tools — no HTTP wiring required. This is a…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.