Geocoding MCP Server

Created By
geocoding-aia year ago
MCP server to access free geocoding
Overview

what is Geocoding MCP Server?

The Geocoding MCP Server is a Model Context Protocol (MCP) server that provides geocoding services by integrating with the Nominatim API, allowing users to convert addresses into geographic coordinates and vice versa.

how to use Geocoding MCP Server?

To use the Geocoding MCP Server, you need to install it via Node.js and configure it in your MCP client, such as Claude Desktop, by adding the appropriate command to your configuration file.

key features of Geocoding MCP Server?

  • Integration with the Nominatim API for accurate geocoding.
  • Easy installation and configuration for various MCP clients.
  • Supports Node.js environment for seamless operation.

use cases of Geocoding MCP Server?

  1. Converting user addresses into latitude and longitude for mapping applications.
  2. Reverse geocoding to find addresses from geographic coordinates.
  3. Enhancing location-based services in mobile and web applications.

FAQ from Geocoding MCP Server?

  • What is the primary function of the Geocoding MCP Server?

It provides geocoding services by converting addresses to coordinates and vice versa using the Nominatim API.

  • Is there a specific Node.js version required?

Yes, Node.js version 18.0.0 or higher is required to run the server.

  • Can I use this server with other MCP clients?

Yes, it can be configured to work with various MCP clients that support the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
geocoding-ai
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Payai X402 Tools

6 hours ago
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.

a day ago