_ registry / mcp http-sse · checked 18m ago

Atlasemoji MCP

https://atlasemoji.com

Registry code: f68024acb8b1cc19

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://atlasemoji.com/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Atlasemoji MCP live?
Yes — it answered the hub's last check (checked 18m ago). It answered 100% of checks over the last 30 days.
Is Atlasemoji MCP free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does Atlasemoji MCP have?
19 tools: verify_atlas_agent, get_failed_runs, get_datasynch_run_status, suggest_field_mapping, validate_coordinates, wanderloop.get_manifest, detect_file_schema, wanderloop.research_place, ….
Is Atlasemoji MCP safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.4%

latency
1,123ms

last good check

priced tools
0

of 19 tools

_ answered our checks, 90 days 501 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
maps travel & places geocoding & maps
used for
  • check a point against a geofence
  • validate coordinates and geojson
  • detect location columns in a file
  • suggest field mappings for data sync
  • research a place with citations
takes → gives
text, data, documents → data
tools
19 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 19 tools
1 open2 auth-required 16 never probed 3 of 19 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • wanderloop.list_provider_capabilities reads open 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "topic": {
      "enum": [
        "record",
        "life",
        "study"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • list_capabilities reads auth-required 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "includeTools": {
      "type": "boolean",
      "default": true,
      "description": "Include currently callable Atlasemoji MCP tools and show which solutions each tool supports."
    },
    "includeLearningResources": {
      "type": "boolean",
      "default": true,
      "description": "Include Atlasemoji learning, help, quick-start, glossary, and MCP documentation resources."
    },
    "includePlatformCapabilities": {
      "type": "boolean",
      "default": true,
      "description": "Include the complete Atlasemoji solution catalog with business outcomes, APIs, production capabilities, learning opportunities, access requirements, and next actions."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • get_atlas_profile reads auth-required 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • verify_atlas_agent reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "companyId",
    "agentId",
    "connectionId"
  ],
  "properties": {
    "agentId": {
      "type": "string",
      "maxLength": 180,
      "minLength": 1
    },
    "companyId": {
      "type": "string",
      "maxLength": 180,
      "minLength": 1
    },
    "connectionId": {
      "type": "string",
      "maxLength": 180,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • get_failed_runs reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "companyId"
  ],
  "properties": {
    "companyId": {
      "type": "string",
      "minLength": 1,
      "description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
    },
    "manifestId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji manifest identifier used to narrow the authorized operation."
    },
    "timeWindow": {
      "enum": [
        "1h",
        "6h",
        "24h",
        "7d",
        "30d"
      ],
      "type": "string",
      "default": "24h",
      "description": "Time window used for read-only operational summaries and diagnostics."
    },
    "workspaceId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
    }
  },
  "additionalProperties": false
}
    arguments 37 lines
  • get_datasynch_run_status reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "companyId"
  ],
  "properties": {
    "companyId": {
      "type": "string",
      "minLength": 1,
      "description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
    },
    "manifestId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji manifest identifier used to narrow the authorized operation."
    },
    "timeWindow": {
      "enum": [
        "1h",
        "6h",
        "24h",
        "7d",
        "30d"
      ],
      "type": "string",
      "default": "24h",
      "description": "Time window used for read-only operational summaries and diagnostics."
    },
    "workspaceId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
    }
  },
  "additionalProperties": false
}
    arguments 37 lines
  • suggest_field_mapping reads unknown 18m ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "rows"
  ],
  "properties": {
    "rows": {
      "type": "array",
      "items": {
        "type": "object",
        "description": "One preview record represented as an object of source column names and values.",
        "additionalProperties": {}
      },
      "maxItems": 100,
      "minItems": 1,
      "description": "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": {
      "enum": [
        "locations",
        "items",
        "inventory",
        "telemetry",
        "crm"
      ],
      "type": "string",
      "description": "Optional Atlasemoji target-table family. When omitted, the tool uses its heuristic business-object candidate."
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • validate_coordinates reads unknown 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "point"
  ],
  "properties": {
    "point": {
      "type": "object",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude in decimal degrees between -90 and 90."
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude in decimal degrees between -180 and 180."
        }
      },
      "description": "Coordinate pair to validate and normalize.",
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}
    arguments 33 lines
  • wanderloop.get_manifest reads unknown 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "manifestId"
  ],
  "properties": {
    "manifestId": {
      "type": "string",
      "maxLength": 300,
      "minLength": 1
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • detect_file_schema reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "rows"
  ],
  "properties": {
    "rows": {
      "type": "array",
      "items": {
        "type": "object",
        "description": "One preview record represented as an object of source column names and values.",
        "additionalProperties": {}
      },
      "maxItems": 100,
      "minItems": 1,
      "description": "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."
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • wanderloop.research_place reads unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • preview_geofence reads unknown 18m ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "companyId",
    "center",
    "radiusMeters"
  ],
  "properties": {
    "label": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional human-readable label for the calculation-only preview."
    },
    "center": {
      "type": "object",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude in decimal degrees between -90 and 90."
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude in decimal degrees between -180 and 180."
        }
      },
      "description": "Center coordinate of the proposed radius geofence.",
      "additionalProperties": false
    },
    "companyId": {
      "type": "string",
      "minLength": 1,
      "description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
    },
    "manifestId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji manifest identifier used to narrow the authorized operation."
    },
    "workspaceId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
    },
    "radiusMeters": {
      "type": "number",
      "maximum": 100000,
      "minimum": 1,
      "description": "Radius in meters. Accepted range is 1 through 100,000 meters."
    }
  },
  "additionalProperties": false
}
    arguments 61 lines
  • validate_manifest_schema reads unknown 18m ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "manifestJson"
  ],
  "properties": {
    "manifestJson": {
      "type": "object",
      "description": "Manifest-like JSON object to inspect locally. The object is not saved or published.",
      "additionalProperties": {}
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • preview_datasynch_rows reads unknown 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "companyId",
    "rows"
  ],
  "properties": {
    "rows": {
      "type": "array",
      "items": {
        "type": "object",
        "description": "One preview record represented as an object of source column names and values.",
        "additionalProperties": {}
      },
      "maxItems": 100,
      "minItems": 1,
      "description": "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."
    },
    "companyId": {
      "type": "string",
      "minLength": 1,
      "description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
    },
    "manifestId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji manifest identifier used to narrow the authorized operation."
    },
    "workspaceId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
    }
  },
  "additionalProperties": false
}
    arguments 37 lines
  • check_point_in_geofence reads unknown 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "center",
    "point",
    "radiusMeters"
  ],
  "properties": {
    "point": {
      "type": "object",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "latitude": {
          "$ref": "#/properties/center/properties/latitude"
        },
        "longitude": {
          "$ref": "#/properties/center/properties/longitude"
        }
      },
      "description": "Coordinate to test against the radius geofence.",
      "additionalProperties": false
    },
    "center": {
      "type": "object",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Latitude in decimal degrees between -90 and 90."
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Longitude in decimal degrees between -180 and 180."
        }
      },
      "description": "Center coordinate of the radius geofence.",
      "additionalProperties": false
    },
    "radiusMeters": {
      "type": "number",
      "maximum": 100000,
      "minimum": 1,
      "description": "Radius in meters. Accepted range is 1 through 100,000 meters."
    }
  },
  "additionalProperties": false
}
    arguments 58 lines
  • detect_location_columns reads unknown 22h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "rows"
  ],
  "properties": {
    "rows": {
      "type": "array",
      "items": {
        "type": "object",
        "additionalProperties": {}
      },
      "maxItems": 100,
      "minItems": 1,
      "description": "Between 1 and 100 preview records whose column names should be inspected for likely location fields."
    }
  },
  "additionalProperties": false
}
    arguments 20 lines
  • summarize_workspace_activity reads unknown 20h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "companyId"
  ],
  "properties": {
    "companyId": {
      "type": "string",
      "minLength": 1,
      "description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
    },
    "manifestId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji manifest identifier used to narrow the authorized operation."
    },
    "timeWindow": {
      "enum": [
        "1h",
        "6h",
        "24h",
        "7d",
        "30d"
      ],
      "type": "string",
      "default": "24h",
      "description": "Time window used for read-only operational summaries and diagnostics."
    },
    "workspaceId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
    }
  },
  "additionalProperties": false
}
    arguments 37 lines
  • get_manifest_summary reads unknown 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "companyId",
    "manifestId"
  ],
  "properties": {
    "companyId": {
      "type": "string",
      "minLength": 1,
      "description": "Required Atlasemoji company or tenant identifier used to enforce tenant authorization."
    },
    "manifestId": {
      "type": "string",
      "minLength": 1,
      "description": "Required Atlasemoji manifest identifier to summarize."
    },
    "workspaceId": {
      "type": "string",
      "minLength": 1,
      "description": "Optional Atlasemoji workspace identifier used to narrow the authorized operation."
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • validate_geojson reads unknown 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "geojson"
  ],
  "properties": {
    "geojson": {
      "type": "object",
      "description": "A GeoJSON Feature, FeatureCollection, Geometry, or GeometryCollection object for basic structural inspection.",
      "additionalProperties": {}
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f68024acb8b1cc19.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f68024acb8b1cc19/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f68024acb8b1cc19/badge.svg)](https://brick.blue/agent/f68024acb8b1cc19?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.