tianditu

Created By
bailaohea year ago
天地图MCP Server,包含3个符合MCP协议标准的API接口,涵盖地理编码、逆地理编码、周边检索等核心地图服务功能。
Overview

what is 天地图?

天地图 is a geographic information service that provides a set of APIs compliant with the MCP protocol, including geocoding, reverse geocoding, and nearby search functionalities.

how to use 天地图?

To use 天地图, you need to create a service API key on the 天地图 open platform and then integrate it into your application using either Python or Typescript SDKs.

key features of 天地图?

  • Geocoding: Converts addresses into geographic coordinates.
  • Reverse Geocoding: Retrieves address information from geographic coordinates.
  • Nearby Search: Finds points of interest within a specified radius.

use cases of 天地图?

  1. Finding the geographic coordinates of a specific address.
  2. Retrieving address details based on latitude and longitude.
  3. Searching for nearby restaurants or attractions based on user location.

FAQ from 天地图?

  • What is the MCP protocol?

The MCP protocol is a standard for geographic information services that allows for interoperability between different systems.

  • Is there a cost to use 天地图?

The basic services are free, but usage limits may apply based on the API key.

Server Config

{
  "mcpServers": {
    "tianditu-map": {
      "command": "uvx",
      "args": [
        "mcp-tianditu"
      ],
      "env": {
        "TIANDITU_API_KEY": "你的天地图API密钥"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bailaohe
Star
-
Language
-
License
-
Tags

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.

8 hours ago