Data Collection

atlasemoji.com

Manages and synchronizes geographic and operational data, including manifest validation and workflow monitoring for Atlasemoji platforms.

1 endpoint17 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://atlasemoji.com/api/mcp

No auth detected

MCP server metadata

Name: Atlasemoji MCP
Version: 0.1.2

Capabilities

tools.listChanged

Known tools 17

list_capabilities

Discover how Atlasemoji supports Atlas DataSynch, GIS, geofencing, CRM, inventory, Atlas Intercept, handheld scanning, APIs, integrations, routing, storytelling, learning, and partner workflows.

Inferred read-only

get_datasynch_run_status

Support Atlas DataSynch operations by retrieving recent processing and workflow status for an authorized company, workspace, or manifest.

Inferred read-only

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.

Inferred read-only

validate_manifest_schema

Prepare geographic and operational manifest data for Atlasemoji use.

Inferred read-only

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.

Inferred read-only

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 returning normalized coordinates.

Inferred read-only

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 basic structure.

Inferred read-only

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, inventory, telemetry, geofences, and DataSynch workflows.

Inferred read-only

preview_geofence

Prepare a radius-based geofence for an Atlasemoji location-aware workflow.

Inferred read-only

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.

Inferred read-only

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 DataSynch workflows.

Inferred read-only

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, or manifest.

Inferred read-only

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.

Inferred read-only

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 operational records.

Inferred read-only

wanderloop.research_place

Assemble a cited, geographically grounded Wanderloop research package for a location.

Inferred read-only

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.

Inferred read-only

wanderloop.list_provider_capabilities

List every registered Wanderloop source integration without dropping unavailable or unconfigured providers.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.atlasemoji-mcp]
url = "https://atlasemoji.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "atlasemoji-mcp": {
      "type": "http",
      "url": "https://atlasemoji.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: atlasemoji-mcp
Remote MCP URL: https://atlasemoji.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "atlasemoji-mcp": {
      "url": "https://atlasemoji.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "atlasemoji-mcp": {
      "type": "http",
      "url": "https://atlasemoji.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "atlasemoji-mcp",
  "transport": "streamable-http",
  "url": "https://atlasemoji.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for atlasemoji.com was fetched 2026-07-27T08:30:11.714Z and is being refreshed.

Trust status Trusted

atlasemoji.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.