Atlasemoji
REMOTE · ATLASEMOJI.COM
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
Available components
Last scanned (1 hour ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2085 tokens (~109/item across 19 items; 19 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
- Structured output schemas are declared (5% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Oct 26 0
- Tool “list_capabilities” rewrote its description, which is the text the model reads security
- Tool coverage: 95% → 88% ▼ functional
- First check of Tool coverage: 5 functional
- Server version: 0.1.2 → 0.2.0 functional
- New tool “get_atlas_profile” functional
- New tool “verify_atlas_agent” functional
- 30 Sept 26 0
- Tool “list_capabilities” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://atlasemoji.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atlasemoji.com | CN=WR3,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | RSA 2048 | SHA256-RSA | db367a1788f802db10a8bec64fee03a7 |
| SANs: atlasemoji.com, *.atlasemoji.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of atlasemoji.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| atlasemoji.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://atlasemoji.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://atlasemoji.com/api/mcp | HTTPS enforced | 301 | https://atlasemoji.com:443/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_point_in_geofence Evaluate a Location Against a Geofence ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| center | object | yes | Center coordinate of the radius geofence. |
| point | object | yes | Coordinate to test against the radius geofence. |
| radiusMeters | number | yes | Radius in meters. Accepted range is 1 through 100,000 meters. |
No output schema declared.
No examples provided.
detect_file_schema Prepare Partner and Operational Data for Atlas DataSynch ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| rows | array | yes | 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. |
No output schema declared.
No examples provided.
detect_location_columns Identify Location Data for Atlasemoji ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| rows | array | yes | Between 1 and 100 preview records whose column names should be inspected for likely location fields. |
No output schema declared.
No examples provided.
get_atlas_profile Get the connected Atlasemoji profile ~49
Return the Atlasemoji profile represented by the current authenticated MCP credentials so ChatGPT can identify the connected Atlas account. This operation is read-only and never accepts a user or account identifier from the model.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | – | |
| id | string | yes | – |
| name | string | – | – |
| nickname | string | – | – |
No examples provided.
get_datasynch_run_status Review Atlas DataSynch Workflow Status ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | string | yes | 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. |
No output schema declared.
No examples provided.
get_failed_runs Review DataSynch Failures and Exceptions ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | string | yes | 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. |
No output schema declared.
No examples provided.
get_manifest_summary Understand an Atlasemoji Manifest ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | string | yes | Required Atlasemoji company or tenant identifier used to enforce tenant authorization. |
| manifestId | string | yes | Required Atlasemoji manifest identifier to summarize. |
| workspaceId | string | – | Optional Atlasemoji workspace identifier used to narrow the authorized operation. |
No output schema declared.
No examples provided.
list_capabilities Discover Atlasemoji Solutions and Agent Capabilities ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
preview_datasynch_rows Preview Data for an Atlas DataSynch Workflow ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
preview_geofence Prepare an Atlasemoji Geofence ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| center | object | yes | Center coordinate of the proposed radius geofence. |
| companyId | string | yes | 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 | yes | Radius in meters. Accepted range is 1 through 100,000 meters. |
| workspaceId | string | – | Optional Atlasemoji workspace identifier used to narrow the authorized operation. |
No output schema declared.
No examples provided.
suggest_field_mapping Prepare a DataSynch Field Mapping ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| rows | array | yes | 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. |
No output schema declared.
No examples provided.
summarize_workspace_activity Summarize Atlasemoji Workspace Activity ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companyId | string | yes | 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. |
No output schema declared.
No examples provided.
validate_coordinates Prepare Coordinates for Atlasemoji GIS Workflows ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| point | object | yes | Coordinate pair to validate and normalize. |
No output schema declared.
No examples provided.
validate_geojson Prepare GeoJSON for Atlasemoji ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| geojson | object | yes | A GeoJSON Feature, FeatureCollection, Geometry, or GeometryCollection object for basic structural inspection. |
No output schema declared.
No examples provided.
validate_manifest_schema Prepare a Manifest for Atlasemoji Workflows ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| manifestJson | object | yes | Manifest-like JSON object to inspect locally. The object is not saved or published. |
No output schema declared.
No examples provided.
verify_atlas_agent Verify an Atlas Agent Connection ~86
Complete proof of life for an already configured Atlas Agent MCP connection. The authenticated MCP principal must be authorized for the requested company and for this tool. Atlas verifies that the connection belongs to the requested Agent and records the current Manifest revision before returning a sanitized Connection Card.
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | – |
| companyId | string | yes | – |
| connectionId | string | yes | – |
No output schema declared.
No examples provided.
wanderloop.get_manifest Wanderloop — Get Saved Manifest ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| manifestId | string | yes | – |
No output schema declared.
No examples provided.
wanderloop.list_provider_capabilities Wanderloop — List Provider Capabilities ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | – |
No output schema declared.
No examples provided.
wanderloop.research_place Wanderloop — Research a Place ~87
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Atlasemoji MCP server?
Atlasemoji is a hosted endpoint at https://atlasemoji.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · atlasemoji.com
claude mcp add --transport http com-atlasemoji-mcp 'https://atlasemoji.com/api/mcp'
What is the Atlasemoji MCP server?
Atlasemoji is an MCP server listed in the public MCP registry as com.atlasemoji/mcp. AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows. This page covers its hosted endpoint (https://atlasemoji.com/api/mcp).
Is the Atlasemoji MCP server safe to use?
Atlasemoji scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Atlasemoji MCP server expose?
Atlasemoji exposes 19 tools: list_capabilities, get_atlas_profile, verify_atlas_agent, get_datasynch_run_status, get_failed_runs, and 14 more. Their descriptions and schemas cost roughly 2,085 tokens of context every time the server is loaded.
Does the Atlasemoji MCP server require authentication?
No. We connected to Atlasemoji without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Atlasemoji MCP server still maintained?
Atlasemoji is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.