pulsemcp scanned Safe content atomic mcp-remote

Axion (Google Earth Engine)

This Earth Engine MCP server by Dhenenjay provides geospatial analysis and satellite imagery processing through Google Earth Engine integration, featuring comprehensive tools for NDVI/NDWI calculations, crop classification, wildfire risk assessment, and interactive map generation. Built with Next.js and TypeScript, it offers consolidated tools that replace 32+ individual operations with 6 super-tools for better MCP stability, supports shapefile boundary conversion for place names, and includes specialized models for agricultural monitoring, flood risk analysis, and deforestation detection with ground truth validation data. The implementation features both HTTP SSE and STDIO transports for Claude Desktop compatibility, Redis/in-memory caching for map sessions, and production deployment on Render with automatic Earth Engine authentication, making it valuable for environmental researchers, agricultural analysts, and geospatial professionals who need AI-assisted satellite data analysis and automated earth observation workflows.

Cognium trust score

46%

Tier

Scanned

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: database
Source: PulseMCP
Repository: github.com/dhenenjay/axion-mcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Axion (Google Earth Engine) from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"