Atlasemoji is an MCP server with 17 tools an agent can call, among them check_point_in_geofence, detect_file_schema, detect_location_columns. It answers at https://atlasemoji.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 18 October 2026, succeeded.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
check_point_in_geofence | Evaluate whether a vehicle, shipment, mobile device, scan, person-authorized location event, asset, aircraft, vessel, or other coordinate is inside a proposed radius boundary used in Atlasemoji geofencing and event-driven workflows. Inputs: center, point, radiusMeters |
detect_file_schema | Analyze a bounded preview of CSV, spreadsheet, JSON, EDI-normalized, EDIFACT-normalized, cXML-derived, inventory, telemetry, CRM, item, location, shipment, or partner records to identify their structure and determine how they may fit Atlas Inputs: rows |
detect_location_columns | Identify address, city, state, province, region, postal code, latitude, and longitude fields in supplied business or operational records so they can be connected to Atlasemoji locations, customer sites, facilities, routes, territories, inve Inputs: rows |
get_datasynch_run_status | Support Atlas DataSynch operations by retrieving recent processing and workflow status for an authorized company, workspace, or manifest. Agents can use the result to explain integration progress, identify stalled activity, and understand t Inputs: companyId, workspaceId, manifestId, timeWindow |
get_failed_runs | Help support, implementation, operations, and partner agents investigate failed Atlas DataSynch activity across APIs, files, EDI, EDIFACT, cXML, mappings, inventory, telemetry, locations, and downstream workflows. Returns authorized failure Inputs: companyId, workspaceId, manifestId, timeWindow |
get_manifest_summary | Retrieve authorized Atlasemoji manifest context so an agent can understand the places, routes, boundaries, layers, records, workflow purpose, workspace relationship, and operational context represented by the manifest. Inputs: companyId, workspaceId, manifestId |
list_capabilities | Discover how Atlasemoji supports Atlas DataSynch, GIS, geofencing, CRM, inventory, Atlas Intercept, handheld scanning, APIs, integrations, routing, storytelling, learning, and partner workflows. Returns the related public APIs, partner acce Inputs: includeTools, includePlatformCapabilities, includeLearningResources |
preview_datasynch_rows | Review a bounded preview of partner, customer, ERP, WMS, TMS, CRM, inventory, telemetry, location, API, spreadsheet, EDI-normalized, EDIFACT-normalized, or cXML-derived records in the context of an authorized Atlasemoji company, workspace, Inputs: companyId, workspaceId, manifestId, rows |
preview_geofence | Prepare a radius-based geofence for an Atlasemoji location-aware workflow. Helps agents and users evaluate the proposed center, radius, coverage area, label, and tenant context before using production geofencing for movement, scans, arrival Inputs: companyId, workspaceId, manifestId, center, radiusMeters, label |
suggest_field_mapping | Suggest an initial bridge between external partner, API, ERP, WMS, TMS, CRM, file, EDI-normalized, EDIFACT-normalized, cXML-derived, inventory, telemetry, item, and location fields and common Atlasemoji data targets. Intended to support int Inputs: rows, targetTable |
summarize_workspace_activity | Summarize recent authorized activity across an Atlasemoji company, workspace, or manifest so agents can explain what has happened across DataSynch, locations, manifests, integrations, telemetry, exceptions, inventory, partner workflows, and Inputs: companyId, workspaceId, manifestId, timeWindow |
validate_coordinates | Prepare latitude and longitude values for Atlasemoji maps, routes, geofences, telemetry, mobile events, customer locations, assets, vessels, aircraft, storytelling, and operational workflows by checking accepted geographic ranges and return Inputs: point |
validate_geojson | Prepare GeoJSON features, collections, points, lines, polygons, and geometry collections for Atlasemoji maps, routes, service areas, stories, manifests, geofences, learning exercises, APIs, and location-aware workflows by checking their bas Inputs: geojson |
validate_manifest_schema | Prepare geographic and operational manifest data for Atlasemoji use. Checks the supplied manifest structure, durable identity, locations, addresses, and coordinates before the data is used with workspaces, routes, storytelling, geofencing, Inputs: manifestJson |
wanderloop.get_manifest | Retrieve a previously saved Wanderloop topic or place-research manifest by manifest ID, including its normalized provider evidence, statuses, map data, citations, and source links when available. Inputs: manifestId |
wanderloop.list_provider_capabilities | List every registered Wanderloop source integration without dropping unavailable or unconfigured providers. Returns provider identity, current topic assignment, execution mode, and required environment configuration so an agent can understa Inputs: topic |
wanderloop.research_place | Assemble a cited, geographically grounded Wanderloop research package for a location. Queries Atlasemoji-approved historical, archival, academic, environmental, wildlife, and place-record providers through the same provider registry used by |
Every block below points at https://atlasemoji.com/api/mcp. Pick your client and copy.
claude mcp add --transport http atlasemoji https://atlasemoji.com/api/mcp
{
"mcpServers": {
"atlasemoji": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://atlasemoji.com/api/mcp"]
}
}
}{
"mcpServers": {
"atlasemoji": {
"url": "https://atlasemoji.com/api/mcp"
}
}
}{
"servers": {
"atlasemoji": {
"type": "http",
"url": "https://atlasemoji.com/api/mcp"
}
}
}{
"context_servers": {
"atlasemoji": {
"url": "https://atlasemoji.com/api/mcp"
}
}
}{
"mcpServers": {
"atlasemoji": {
"serverUrl": "https://atlasemoji.com/api/mcp"
}
}
}{
"mcpServers": {
"atlasemoji": {
"url": "https://atlasemoji.com/api/mcp"
}
}
}name: Atlasemoji
version: 0.0.1
schema: v1
mcpServers:
- name: Atlasemoji
type: streamable-http
url: https://atlasemoji.com/api/mcp{
"mcpServers": {
"atlasemoji": {
"httpUrl": "https://atlasemoji.com/api/mcp"
}
}
}{
"mcpServers": {
"atlasemoji": {
"type": "http",
"url": "https://atlasemoji.com/api/mcp"
}
}
}{
"mcpServers": {
"atlasemoji": {
"url": "https://atlasemoji.com/api/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fatlasemoji.com%2Fapi%2Fmcp&type=streamable_http&id=atlasemoji&name=Atlasemoji
It answered our last check on 18 October 2026 in 216 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by atlasemoji.com and served from atlasemoji.com, the vendor's own domain: https://atlasemoji.com/api/mcp.
17, as returned by the server's own tools/list on 10 September 2026: check_point_in_geofence, detect_file_schema, detect_location_columns, get_datasynch_run_status, get_failed_runs, get_manifest_summary, list_capabilities, preview_datasynch_rows, and 9 more.
It answered our last check on 18 October 2026 in 216 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://atlasemoji.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.atlasemoji. Endpoint host: atlasemoji.com. ARD identifier: urn:air:com.atlasemoji:mcp:mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.