AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
Déduit des transports déclarés par cette annonce (streamable-http). Un client absent de cette liste n’est pas écarté pour autant — c’est simplement quelque chose que Forge ne peut pas confirmer.
La vérification confirme l’identité de l’éditeur (la propriété du dépôt), pas la sûreté du code. L’analyse de sécurité couvre les CVE connues et les scripts d’installation suspects.
Lu depuis un véritable échange MCP initialize → tools/list contre l’endpoint déclaré. Aucun outil n’a été invoqué — tools/list est l’appel d’introspection en lecture seule que le protocole prévoit pour cela. Cela reflète ce que le serveur annonçait à cet instant ; un endpoint hébergé n’est figé sur aucune version et peut changer sans préavis.
https://atlasemoji.com/api/mcp17 outils · 293 mslist_capabilitiesDiscover 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, learn…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, learn…
| Paramètre | Type | Description |
|---|---|---|
| includeTools | boolean | Include currently callable Atlasemoji MCP tools and show which solutions each tool supports. |
| includePlatformCapabilities | boolean | Include the complete Atlasemoji solution catalog with business outcomes, APIs, production capabilities, learning opportunities, access requirements, and next a… |
| includeLearningResources | boolean | Include Atlasemoji learning, help, quick-start, glossary, and MCP documentation resources. |
get_datasynch_run_statusSupport 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, telemetr…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, telemetr…
| Paramètre | Type | Description |
|---|---|---|
| companyId* | string | Required Atlasemoji company or tenant identifier used to enforce tenant authorization. |
| workspaceId | string | Optional Atlasemoji workspace identifier used to narrow the authorized operation. |
| manifestId | string | Optional Atlasemoji manifest identifier used to narrow the authorized operation. |
| timeWindow | string | Time window used for read-only operational summaries and diagnostics. |
get_failed_runsHelp 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.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.
| Paramètre | Type | Description |
|---|---|---|
| companyId* | string | Required Atlasemoji company or tenant identifier used to enforce tenant authorization. |
| workspaceId | string | Optional Atlasemoji workspace identifier used to narrow the authorized operation. |
| manifestId | string | Optional Atlasemoji manifest identifier used to narrow the authorized operation. |
| timeWindow | string | Time window used for read-only operational summaries and diagnostics. |
validate_manifest_schemaPrepare 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.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.
| Paramètre | Type | Description |
|---|---|---|
| manifestJson* | object | Manifest-like JSON object to inspect locally. The object is not saved or published. |
get_manifest_summaryRetrieve 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.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.
| Paramètre | Type | Description |
|---|---|---|
| companyId* | string | Required Atlasemoji company or tenant identifier used to enforce tenant authorization. |
| workspaceId | string | Optional Atlasemoji workspace identifier used to narrow the authorized operation. |
| manifestId* | string | Required Atlasemoji manifest identifier to summarize. |
validate_coordinatesPrepare 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.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.
| Paramètre | Type | Description |
|---|---|---|
| point* | object | Coordinate pair to validate and normalize. |
validate_geojsonPrepare 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.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.
| Paramètre | Type | Description |
|---|---|---|
| geojson* | object | A GeoJSON Feature, FeatureCollection, Geometry, or GeometryCollection object for basic structural inspection. |
detect_location_columnsIdentify 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.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.
| Paramètre | Type | Description |
|---|---|---|
| rows* | array | Between 1 and 100 preview records whose column names should be inspected for likely location fields. |
preview_geofencePrepare 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 downstrea…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 downstrea…
| Paramètre | Type | Description |
|---|---|---|
| companyId* | string | Required Atlasemoji company or tenant identifier used to enforce tenant authorization. |
| workspaceId | string | Optional Atlasemoji workspace identifier used to narrow the authorized operation. |
| manifestId | string | Optional Atlasemoji manifest identifier used to narrow the authorized operation. |
| center* | object | Center coordinate of the proposed radius geofence. |
| radiusMeters* | number | Radius in meters. Accepted range is 1 through 100,000 meters. |
| label | string | Optional human-readable label for the calculation-only preview. |
check_point_in_geofenceEvaluate 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.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.
| Paramètre | Type | Description |
|---|---|---|
| center* | object | Center coordinate of the radius geofence. |
| point* | object | Coordinate to test against the radius geofence. |
| radiusMeters* | number | Radius in meters. Accepted range is 1 through 100,000 meters. |
detect_file_schemaAnalyze 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.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.
| Paramètre | Type | Description |
|---|---|---|
| rows* | array | 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 M… |
preview_datasynch_rowsReview 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.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.
| Paramètre | Type | Description |
|---|---|---|
| companyId* | string | Required Atlasemoji company or tenant identifier used to enforce tenant authorization. |
| workspaceId | string | Optional Atlasemoji workspace identifier used to narrow the authorized operation. |
| manifestId | string | Optional Atlasemoji manifest identifier used to narrow the authorized operation. |
| rows* | array | 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 M… |
suggest_field_mappingSuggest 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.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.
| Paramètre | Type | Description |
|---|---|---|
| rows* | array | 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 M… |
| targetTable | string | Optional Atlasemoji target-table family. When omitted, the tool uses its heuristic business-object candidate. |
summarize_workspace_activitySummarize 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.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.
| Paramètre | Type | Description |
|---|---|---|
| companyId* | string | Required Atlasemoji company or tenant identifier used to enforce tenant authorization. |
| workspaceId | string | Optional Atlasemoji workspace identifier used to narrow the authorized operation. |
| manifestId | string | Optional Atlasemoji manifest identifier used to narrow the authorized operation. |
| timeWindow | string | Time window used for read-only operational summaries and diagnostics. |
wanderloop.research_placeAssemble 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, prov…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, prov…
Aucun schéma d’entrée n’a été publié pour cet outil.
wanderloop.get_manifestRetrieve 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.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.
| Paramètre | Type | Description |
|---|---|---|
| manifestId* | string | — |
wanderloop.list_provider_capabilitiesList 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…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…
| Paramètre | Type | Description |
|---|---|---|
| topic | string | — |
17 outils sur 17 ont publié une description.
Les noms et descriptions d’outils sont écrits par l’éditeur et affichés tels quels, comme du texte inerte. Ce sont les chaînes qu’un client MCP transmet à un modèle, alors Forge y recherche des motifs d’injection de prompt — tout constat apparaît avec l’analyse de sécurité ci-dessus. « Privilégié » est une correspondance de mot-clé sur le nom de l’outil, pas un audit de ce qu’il fait : un nom anodin peut tout de même tout faire.
AI-ready GIS, geofencing, DataSynch, CRM, inventory, routing, APIs, telemetry and workflows.
Les noms cliquables ouvrent l’index Forge de toutes les entrées observées exposant cet outil. Parcourir tous les outils indexés.
Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.