{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"npm_npm-amapamap-maps-mcp-server","slug":"npm-amapamap-maps-mcp-server","name":"@amap/amap-maps-mcp-server","type":"mcp","url":"https://www.npmjs.com/package/@amap/amap-maps-mcp-server","page_url":"https://unfragile.ai/npm-amapamap-maps-mcp-server","categories":["mcp-servers"],"tags":[],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"npm_npm-amapamap-maps-mcp-server__cap_0","uri":"capability://tool.use.integration.amap.geocoding.and.reverse.geocoding.via.mcp.protocol","name":"amap geocoding and reverse geocoding via mcp protocol","description":"Exposes AMap's geocoding API through the Model Context Protocol, allowing LLM agents to convert addresses to coordinates and coordinates to addresses. Implements MCP tool schema binding that wraps AMap REST API endpoints, handling request serialization, response parsing, and error translation into structured tool results that Claude and other MCP-compatible clients can consume.","intents":["I need my AI agent to convert user-provided addresses into latitude/longitude for map operations","I want to reverse-geocode coordinates back to human-readable addresses within an LLM conversation","I need to validate address inputs by geocoding them before passing to downstream mapping services"],"best_for":["LLM application developers building location-aware agents","Teams integrating AMap services with Claude or other MCP-compatible AI models","Developers prototyping location-based AI workflows in China/Asia-Pacific regions"],"limitations":["Geocoding accuracy and coverage limited to AMap's data quality (primarily optimized for China)","Rate limiting enforced by AMap API tier; no built-in request batching or queue management","Requires valid AMap API key with geocoding service enabled; no fallback to alternative providers","MCP protocol overhead adds ~50-100ms per request compared to direct REST calls"],"requires":["AMap API key with geocoding service enabled","MCP-compatible client (Claude Desktop, or custom MCP host)","Node.js 14+ for running the MCP server","Network access to AMap API endpoints (api.amap.com)"],"input_types":["address string (Chinese or English)","latitude/longitude coordinates (decimal degrees)"],"output_types":["structured JSON with coordinates, address components, and confidence scores","formatted address strings"],"categories":["tool-use-integration","location-services"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-amapamap-maps-mcp-server__cap_1","uri":"capability://tool.use.integration.route.planning.and.directions.retrieval.via.mcp","name":"route planning and directions retrieval via mcp","description":"Wraps AMap's routing API (driving, walking, transit) through MCP tool schema, enabling LLM agents to request turn-by-turn directions, distance/duration estimates, and route alternatives. Translates AMap's polyline-encoded route geometry and step-by-step instructions into structured tool outputs that agents can reason about and present to users.","intents":["I need my agent to calculate driving directions between two addresses and summarize the route","I want to compare multiple route options (fastest vs shortest) and let the agent choose based on context","I need to get transit directions with stop information for multi-modal trip planning"],"best_for":["Developers building conversational navigation assistants","Teams creating trip planning or logistics optimization agents","Location-based chatbots that need to provide directions within conversations"],"limitations":["Route alternatives limited to AMap's algorithm output; no custom optimization criteria","Real-time traffic data integration depends on AMap API tier; may not reflect current conditions","Polyline decoding adds computational overhead; large routes (100+ waypoints) may exceed token budgets","Transit routing availability varies by city; limited outside major Chinese metropolitan areas"],"requires":["AMap API key with routing service enabled","MCP-compatible client","Node.js 14+","Valid origin and destination coordinates or addresses"],"input_types":["origin address or coordinates","destination address or coordinates","route type parameter (driving, walking, transit)","optional waypoints array"],"output_types":["structured route object with distance, duration, polyline geometry","step-by-step instruction array","traffic condition summary"],"categories":["tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-amapamap-maps-mcp-server__cap_2","uri":"capability://tool.use.integration.place.search.and.poi.discovery.via.mcp","name":"place search and poi discovery via mcp","description":"Implements MCP tool bindings for AMap's place search API, enabling agents to discover points of interest (restaurants, hotels, gas stations, etc.) by keyword, category, or proximity. Handles spatial queries (nearby search, polygon/circle search) and returns ranked results with ratings, contact info, and business hours, allowing agents to help users find relevant locations.","intents":["I need my agent to find nearby restaurants matching user preferences and compare options","I want to search for specific business types (e.g., 'ATM') within a geographic area","I need to retrieve detailed business information (hours, phone, ratings) for locations the agent recommends"],"best_for":["Developers building location-based recommendation agents","Teams creating local search chatbots for travel or lifestyle apps","Agents that need to discover services (hotels, restaurants, transport) during trip planning"],"limitations":["Search results limited to AMap's POI database; coverage gaps in rural or less-developed regions","Pagination limited to 20 results per request; discovering large result sets requires multiple calls","Business information (hours, ratings) may be stale; no real-time update guarantees","Category taxonomy is AMap-specific; mapping user queries to AMap categories requires custom logic"],"requires":["AMap API key with place search service enabled","MCP-compatible client","Node.js 14+","Valid search keyword or category code"],"input_types":["search keyword string","POI category code","center coordinates for proximity search","search radius in meters","optional polygon or circle geometry for bounded search"],"output_types":["ranked array of POI objects with name, address, coordinates, rating, contact info","business hours and service information","distance from search center"],"categories":["tool-use-integration","search-retrieval"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-amapamap-maps-mcp-server__cap_3","uri":"capability://tool.use.integration.static.map.image.generation.with.markers.and.overlays.via.mcp","name":"static map image generation with markers and overlays via mcp","description":"Wraps AMap's static map API through MCP, allowing agents to generate map images with customizable markers, polylines, and polygons for visualization in chat interfaces. Constructs image URLs with encoded geometry, styling parameters, and zoom levels, returning image URLs that clients can render or embed in responses.","intents":["I need my agent to generate a map image showing a route or location for visual presentation","I want to create a map visualization with multiple markers (e.g., search results) for the user","I need to overlay a polygon or service area on a map image for context"],"best_for":["Developers building visual location-aware chatbots","Teams creating trip planning or real estate agents that need map visualizations","Agents that need to communicate geographic information through images"],"limitations":["Static images only; no interactive map capabilities","Image size and complexity limited by AMap API constraints (typically 1280x1024 max)","Marker count limited; dense visualizations (100+ markers) may exceed URL length limits","No real-time data overlay (traffic, weather); images are static snapshots","Styling options limited to AMap's predefined themes; custom cartography not supported"],"requires":["AMap API key with static map service enabled","MCP-compatible client with image rendering capability","Node.js 14+","Valid center coordinates or geometry to visualize"],"input_types":["center coordinates or bounding box","zoom level (1-18)","array of marker objects with coordinates and labels","optional polyline or polygon geometry","map style parameter"],"output_types":["image URL (PNG format)","base64-encoded image data (optional)"],"categories":["tool-use-integration","image-visual"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-amapamap-maps-mcp-server__cap_4","uri":"capability://tool.use.integration.distance.matrix.calculation.for.multi.point.routing.via.mcp","name":"distance matrix calculation for multi-point routing via mcp","description":"Exposes AMap's distance matrix API through MCP, enabling agents to calculate distances and travel times between multiple origin-destination pairs in a single request. Supports driving, walking, and transit modes, returning a matrix of distances/durations that agents can use for optimization, comparison, or decision-making.","intents":["I need my agent to calculate travel times between multiple locations for comparison","I want to find the closest location from a set of options based on travel distance","I need to optimize a delivery route by calculating distances between all waypoints"],"best_for":["Developers building logistics or delivery optimization agents","Teams creating multi-location comparison tools","Agents that need to reason about relative distances between many locations"],"limitations":["Matrix size limited by AMap API (typically 10x10 or 100 total pairs); large networks require multiple requests","Calculation time increases with matrix size; large matrices may timeout","No real-time traffic integration in distance matrix; uses average conditions","Results are symmetric (distance A→B equals B→A); one-way routing not supported"],"requires":["AMap API key with distance matrix service enabled","MCP-compatible client","Node.js 14+","Array of origin and destination coordinates"],"input_types":["array of origin coordinates","array of destination coordinates","route type (driving, walking, transit)"],"output_types":["2D matrix of distances (meters)","2D matrix of durations (seconds)","status codes for each pair"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-amapamap-maps-mcp-server__cap_5","uri":"capability://tool.use.integration.ip.based.location.lookup.via.mcp","name":"ip-based location lookup via mcp","description":"Implements MCP tool binding for AMap's IP location API, enabling agents to determine geographic location from IP addresses. Returns city-level or more granular location data, allowing agents to infer user location context or validate geographic constraints without explicit user input.","intents":["I need my agent to infer the user's approximate location from their IP address","I want to validate that a user is in a specific region before providing location-specific services","I need to provide location-aware recommendations based on IP geolocation"],"best_for":["Developers building location-aware chatbots that need implicit location context","Teams creating region-specific service agents","Agents that need to validate geographic constraints for compliance or service availability"],"limitations":["IP geolocation accuracy varies; city-level precision typical, street-level rare","VPN/proxy usage defeats accuracy; cannot distinguish actual user location","Privacy concerns; IP lookup may violate user privacy expectations without explicit consent","Coverage gaps in some regions; rural or less-developed areas may have inaccurate data"],"requires":["AMap API key with IP location service enabled","MCP-compatible client","Node.js 14+","Valid IP address (IPv4 or IPv6)"],"input_types":["IP address string"],"output_types":["structured location object with city, province, country","coordinates (latitude/longitude)","ISP information"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"npm_npm-amapamap-maps-mcp-server__cap_6","uri":"capability://tool.use.integration.mcp.protocol.transport.and.tool.schema.binding","name":"mcp protocol transport and tool schema binding","description":"Implements the Model Context Protocol (MCP) server framework, handling bidirectional JSON-RPC communication with MCP clients (Claude, custom hosts), tool schema definition and validation, and request/response marshaling. Manages the lifecycle of tool invocations, error handling, and result serialization according to MCP specification.","intents":["I need to expose AMap services as callable tools within Claude or other MCP-compatible AI models","I want to integrate AMap capabilities into my existing MCP-based agent infrastructure","I need to ensure tool schemas are properly validated and compatible with my MCP client"],"best_for":["Developers integrating AMap with Claude or other MCP-compatible models","Teams building MCP-based agent ecosystems","Organizations standardizing on MCP for AI tool integration"],"limitations":["MCP protocol overhead adds latency (~50-100ms per request) compared to direct API calls","Tool invocation is synchronous; no built-in support for long-running operations or streaming","Schema validation is strict; malformed requests from clients result in errors rather than graceful degradation","No built-in caching or request deduplication; repeated identical requests incur full API costs"],"requires":["MCP-compatible client (Claude Desktop, custom MCP host, etc.)","Node.js 14+","MCP client library or SDK"],"input_types":["JSON-RPC 2.0 requests with tool name and parameters"],"output_types":["JSON-RPC 2.0 responses with tool results or error codes"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":24,"verified":false,"data_access_risk":"high","permissions":["AMap API key with geocoding service enabled","MCP-compatible client (Claude Desktop, or custom MCP host)","Node.js 14+ for running the MCP server","Network access to AMap API endpoints (api.amap.com)","AMap API key with routing service enabled","MCP-compatible client","Node.js 14+","Valid origin and destination coordinates or addresses","AMap API key with place search service enabled","Valid search keyword or category code"],"failure_modes":["Geocoding accuracy and coverage limited to AMap's data quality (primarily optimized for China)","Rate limiting enforced by AMap API tier; no built-in request batching or queue management","Requires valid AMap API key with geocoding service enabled; no fallback to alternative providers","MCP protocol overhead adds ~50-100ms per request compared to direct REST calls","Route alternatives limited to AMap's algorithm output; no custom optimization criteria","Real-time traffic data integration depends on AMap API tier; may not reflect current conditions","Polyline decoding adds computational overhead; large routes (100+ waypoints) may exceed token budgets","Transit routing availability varies by city; limited outside major Chinese metropolitan areas","Search results limited to AMap's POI database; coverage gaps in rural or less-developed regions","Pagination limited to 20 results per request; discovering large result sets requires multiple calls","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.24,"ecosystem":0.3,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:23.903Z","last_scraped_at":"2026-05-03T14:23:35.035Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=npm-amapamap-maps-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=npm-amapamap-maps-mcp-server"}},"signature":"DfHaFyv3AONnYNvf0WhPpdeDF5/qfGYxcp7oyL+8Iov8nIvVnvIK0zbVSEmnKDjd41+1Pq3dweRXGlgIxeTLAw==","signedAt":"2026-06-20T02:30:59.702Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/npm-amapamap-maps-mcp-server","artifact":"https://unfragile.ai/npm-amapamap-maps-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=npm-amapamap-maps-mcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}