@zealgeo/mcp-geo-server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is @zealgeo/mcp-geo-server?

@zealgeo/mcp-geo-server is a geospatial processing tool server based on the Model Context Protocol (MCP) that provides functionalities for coordinate system conversion, distance calculation, and area calculation.

How to use @zealgeo/mcp-geo-server?

To use the server, install it via npm with the command: npx -y @zealgeo/mcp-geo-server. You can then access its various tools for geospatial analysis.

Key features of @zealgeo/mcp-geo-server?

  • Supports conversion between multiple coordinate systems: BD09, GCJ02, WGS84, and Web Mercator.
  • Provides methods for calculating distances and areas based on geospatial data.
  • Allows input in various coordinate systems for flexible usage.

Use cases of @zealgeo/mcp-geo-server?

  1. Converting coordinates between different systems for mapping applications.
  2. Calculating distances for route planning and logistics.
  3. Determining areas for land use and environmental studies.

FAQ from @zealgeo/mcp-geo-server?

  • What coordinate systems are supported?

The server supports BD09, GCJ02, WGS84, and Web Mercator coordinate systems.

  • How accurate are the calculations?

The accuracy of conversions and calculations depends on the quality of the input data.

  • Is there any cost to use the server?

No, the server is open-source and free to use under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

7 hours ago