# Atlasemoji (remote · atlasemoji.com)

AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.

- Trust score: 71/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `atlasemoji.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-atlasemoji-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-atlasemoji-mcp/api-mcp)

## Channel facts

- Endpoint: `https://atlasemoji.com/api/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1950 tokens (~114/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 95% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-atlasemoji-mcp https://atlasemoji.com/api/mcp
```

### Codex

```toml
[mcp_servers.com-atlasemoji-mcp]
url = "https://atlasemoji.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-atlasemoji-mcp": {
      "type": "remote",
      "url": "https://atlasemoji.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-atlasemoji-mcp --url https://atlasemoji.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-atlasemoji-mcp:
    url: "https://atlasemoji.com/api/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 70, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (17)

### `list_capabilities` (~158 tokens)

Discover Atlasemoji Solutions and Agent 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 access paths, production capabilities, current MCP tools, learning opportunities, and access requirements for each solution.

Input parameters:

- `includeLearningResources` (boolean): Include Atlasemoji learning, help, quick-start, glossary, and MCP documentation resources.
- `includePlatformCapabilities` (boolean): Include the complete Atlasemoji solution catalog with business outcomes, APIs, production capabilities, learning opportunities, access requirements, and next actions.
- `includeTools` (boolean): Include currently callable Atlasemoji MCP tools and show which solutions each tool supports.

### `get_datasynch_run_status` (~155 tokens)

Review Atlas DataSynch Workflow 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 the current state of EDI, EDIFACT, cXML, API, file, telemetry, inventory, location, and partner-data workflows.

Input parameters:

- `companyId` (string, required): Required Atlasemoji company or tenant identifier used to enforce tenant authorization.
- `manifestId` (string): Optional Atlasemoji manifest identifier used to narrow the authorized operation.
- `timeWindow` (string): Time window used for read-only operational summaries and diagnostics.
- `workspaceId` (string): Optional Atlasemoji workspace identifier used to narrow the authorized operation.

### `get_failed_runs` (~140 tokens)

Review DataSynch Failures and Exceptions

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 and exception context without changing workflow records.

Input parameters:

- `companyId` (string, required): Required Atlasemoji company or tenant identifier used to enforce tenant authorization.
- `manifestId` (string): Optional Atlasemoji manifest identifier used to narrow the authorized operation.
- `timeWindow` (string): Time window used for read-only operational summaries and diagnostics.
- `workspaceId` (string): Optional Atlasemoji workspace identifier used to narrow the authorized operation.

### `validate_manifest_schema` (~89 tokens)

Prepare a Manifest for Atlasemoji Workflows

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, DataSynch, inventory, CRM, or other Atlasemoji workflows.

Input parameters:

- `manifestJson` (object, required): Manifest-like JSON object to inspect locally. The object is not saved or published.

### `get_manifest_summary` (~99 tokens)

Understand an Atlasemoji Manifest

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.

Input parameters:

- `companyId` (string, required): Required Atlasemoji company or tenant identifier used to enforce tenant authorization.
- `manifestId` (string, required): Required Atlasemoji manifest identifier to summarize.
- `workspaceId` (string): Optional Atlasemoji workspace identifier used to narrow the authorized operation.

### `validate_coordinates` (~66 tokens)

Prepare Coordinates for Atlasemoji GIS Workflows

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.

Input parameters:

- `point` (object, required): Coordinate pair to validate and normalize.

### `validate_geojson` (~84 tokens)

Prepare GeoJSON for Atlasemoji

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.

Input parameters:

- `geojson` (object, required): A GeoJSON Feature, FeatureCollection, Geometry, or GeometryCollection object for basic structural inspection.

### `detect_location_columns` (~92 tokens)

Identify Location Data for Atlasemoji

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.

Input parameters:

- `rows` (array, required): Between 1 and 100 preview records whose column names should be inspected for likely location fields.

### `preview_geofence` (~181 tokens)

Prepare an Atlasemoji 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, arrivals, exits, dwell, proximity, telemetry, alerts, or downstream actions.

Input parameters:

- `center` (object, required): Center coordinate of the proposed radius geofence.
- `companyId` (string, required): Required Atlasemoji company or tenant identifier used to enforce tenant authorization.
- `label` (string): Optional human-readable label for the calculation-only preview.
- `manifestId` (string): Optional Atlasemoji manifest identifier used to narrow the authorized operation.
- `radiusMeters` (number, required): Radius in meters. Accepted range is 1 through 100,000 meters.
- `workspaceId` (string): Optional Atlasemoji workspace identifier used to narrow the authorized operation.

### `check_point_in_geofence` (~108 tokens)

Evaluate a Location Against a 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.

Input parameters:

- `center` (object, required): Center coordinate of the radius geofence.
- `point` (object, required): Coordinate to test against the radius geofence.
- `radiusMeters` (number, required): Radius in meters. Accepted range is 1 through 100,000 meters.

### `detect_file_schema` (~113 tokens)

Prepare Partner and Operational Data for Atlas DataSynch

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.

Input parameters:

- `rows` (array, required): Between 1 and 100 preview rows from a CSV, spreadsheet, JSON, EDI-normalized, or other tabular payload. Rows are inspected in memory and are not committed by MCP preview tools.

### `preview_datasynch_rows` (~175 tokens)

Preview Data for an Atlas DataSynch Workflow

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.

Input parameters:

- `companyId` (string, required): Required Atlasemoji company or tenant identifier used to enforce tenant authorization.
- `manifestId` (string): Optional Atlasemoji manifest identifier used to narrow the authorized operation.
- `rows` (array, required): Between 1 and 100 preview rows from a CSV, spreadsheet, JSON, EDI-normalized, or other tabular payload. Rows are inspected in memory and are not committed by MCP preview tools.
- `workspaceId` (string): Optional Atlasemoji workspace identifier used to narrow the authorized operation.

### `suggest_field_mapping` (~146 tokens)

Prepare a DataSynch 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 integration design and human-reviewed mapping preparation.

Input parameters:

- `rows` (array, required): Between 1 and 100 preview rows from a CSV, spreadsheet, JSON, EDI-normalized, or other tabular payload. Rows are inspected in memory and are not committed by MCP preview tools.
- `targetTable` (string): Optional Atlasemoji target-table family. When omitted, the tool uses its heuristic business-object candidate.

### `summarize_workspace_activity` (~132 tokens)

Summarize Atlasemoji 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.

Input parameters:

- `companyId` (string, required): Required Atlasemoji company or tenant identifier used to enforce tenant authorization.
- `manifestId` (string): Optional Atlasemoji manifest identifier used to narrow the authorized operation.
- `timeWindow` (string): Time window used for read-only operational summaries and diagnostics.
- `workspaceId` (string): Optional Atlasemoji workspace identifier used to narrow the authorized operation.

### `wanderloop.research_place` (~87 tokens)

Wanderloop — Research a 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 the Wanderloop application. Returns evidence records, provider execution status, citations, GeoJSON map features, and saved manifest links. This is evidence assembly, not an unsupported AI-written story.

### `wanderloop.get_manifest` (~53 tokens)

Wanderloop — Get Saved 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.

Input parameters:

- `manifestId` (string, required)

### `wanderloop.list_provider_capabilities` (~72 tokens)

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 understand which historical, academic, archival, environmental, and natural-history sources Atlasemoji can invoke.

Input parameters:

- `topic` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-atlasemoji-mcp/api-mcp#diagnostics

## Score history

- 2026-08-03: 71
- 2026-08-02: 71
- 2026-08-01: 70
- 2026-07-31: 70
- 2026-07-30: 67
- 2026-07-29: 66
- 2026-07-28: 66
- 2026-07-27: 65
- 2026-07-26: 64

## Links

- Remote endpoint: https://atlasemoji.com/api/mcp
- Authorisation metadata: https://atlasemoji.com/.well-known/oauth-protected-resource/api/mcp
- Website: https://atlasemoji.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-atlasemoji-mcp/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-atlasemoji-mcp/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-atlasemoji-mcp/api-mcp