AWS-GeoPlaces-MCP-Server

Created By
dxsima year ago
MCP server to directly access AWS location services using the GeoPlaces API, provides direct geocoding or reverse-geocoding capabilities like Google Maps API
Overview

what is AWS-GeoPlaces-MCP-Server?

AWS-GeoPlaces-MCP-Server is a project that allows users to directly access AWS location services through the GeoPlaces API, providing geocoding and reverse-geocoding capabilities.

how to use AWS-GeoPlaces-MCP-Server?

To use the server, follow the setup instructions to install the necessary tools and create a virtual environment. Then, create your MCP using Python and run your server in the MCP Inspector.

key features of AWS-GeoPlaces-MCP-Server?

  • Direct access to AWS location services
  • Geocoding and reverse-geocoding capabilities
  • Easy setup with Python project management tools

use cases of AWS-GeoPlaces-MCP-Server?

  1. Converting addresses into geographic coordinates (geocoding).
  2. Finding addresses from geographic coordinates (reverse-geocoding).
  3. Integrating location services into applications for enhanced user experience.

FAQ from AWS-GeoPlaces-MCP-Server?

  • What is geocoding?

Geocoding is the process of converting addresses into geographic coordinates.

  • What is reverse-geocoding?

Reverse-geocoding is the process of converting geographic coordinates into a human-readable address.

  • Is there a cost associated with using AWS location services?

Yes, AWS location services may incur costs based on usage.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dxsim
Star
0
Language
Python
License
Apache-2.0 license
Tags

Recommend Servers

View All
Gpt Scrambler

2 days 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.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago