Geocode MCP SSE Server

Created By
aimioxa year ago
Provides real-time access to geocoding and reverse geocoding services. No API key required.
Overview

what is Geocode MCP SSE Server?

Geocode MCP SSE Server provides real-time access to geocoding and reverse geocoding services without the need for an API key.

how to use Geocode MCP SSE Server?

To use the Geocode MCP SSE Server, simply send requests to the server endpoints for geocoding or reverse geocoding operations.

key features of Geocode MCP SSE Server?

  • Real-time geocoding and reverse geocoding services
  • No API key required for access
  • Lightweight and efficient framework for location services

use cases of Geocode MCP SSE Server?

  1. Integrating geocoding services into web applications
  2. Providing location-based services in mobile apps
  3. Enhancing data analysis with geographical information

FAQ from Geocode MCP SSE Server?

  • Do I need an API key to use the Geocode MCP SSE Server?

No, the server does not require an API key for access.

  • What types of geocoding does this server support?

The server supports both geocoding (address to coordinates) and reverse geocoding (coordinates to address).

  • Is there any rate limit for using the server?

Currently, there are no specified rate limits, but usage may be monitored for performance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aimiox
Star
-
Language
-
License
-
Category

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.

21 hours ago