Atlas entry
api.triplogistics.app
9 capabilities over MCP. First atlas observation.
Surfaces
5 protocols checked
| ARD | Not found | No document retrieved |
|---|---|---|
| A2A | Not found | 0 skills |
| MCP | Valid | 2025-11-25 · 6 tools · 3 resources · prompts not advertised |
| OpenAPI | Not detected | 0 operations |
| WebMCP | Not detected | 0 declarative form tools · experimental |
Exact states and meaning
- ARDabsent
Exact state: not found · No document retrieved
The supported discovery location returned no matching document.
Not found does not prove the service exposes no such interface elsewhere.
Not observed / not fetched
- A2Aabsent
Exact state: not found · 0 skills
The supported discovery location returned no matching document.
Not found does not prove the service exposes no such interface elsewhere.
Not observed / not fetched
- MCPobserved
Exact state: valid · Revision 2025-11-25 · 6 tools · 3 resources · prompts not advertised
A usable protocol document was retrieved and validated.
Directly observed
- OpenAPIabsent
Exact state: not detected · 0 operations
No endpoint was established from the evidence and scope that InterfaceDelta inspected.
Not detected does not prove that no endpoint exists.
Not observed / not fetched
- WebMCPabsent
Exact state: not detected · 0 declarative form tools · experimental
No named declarative WebMCP form tools were observed in the origin root HTML.
Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.
Not observed / not fetched
Capabilities
9 · inventory complete
Summary of the AI readings · beta
The service lists 6 capabilities, and 3 have AI readings.
search_tours, search_esim and search_car_rentals are read as read-only.
Rows named: search_tours · search_esim · search_car_rentals
Written by code from the AI readings on this page: it groups them and says nothing they do not.
The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.
MCP tools 6
check_flight_compensationinputs
airline,issue(required)search_car_rentalsinputs
driver_age,dropoff_date(required),location(required),pickup_date(required)AI Reads only 0.80
search_esiminputs
days,destination(required)AI Reads only 0.85
search_luggage_storageinputs
location(required),nearsearch_toursinputs
currency,interest,location(required)AI Reads only 0.85
search_transfersinputs
from(required),passengers,to
MCP resources 3
name not shownname not shownname not shown
Not observed in this Passport: A2A skills, MCP prompts, OpenAPI operations.
Declared and observed
No tools declare hints.
A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.
Atlas history
1 observation
- 9 capabilities · MCP 2025-11-25 · MCP endpoint validFirst observation
Fingerprint and versions
- Fingerprint
4b19a5b89954da4101dddf5c559ca0a688e66d444939aac1eefcd1cd2ae9a9e5- Passport schema
- 0.5.0, passport-semantic-v4
- Consistency
- MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: match · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable
Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.
About this entry
app.triplogistics/trip-logistics-assistantListedOfficial MCP Registry · first listed 15 Sep 2026 · last listed 30 Oct 2026
Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal
Identity and snapshot
- Target key
sha256:dee2097b4c562e1bf3da0b0a8058de42f90534cff2c2c6c9873c4c8802bb6d88- Locator SHA-256
b55d0023015d55943894386d86e4edddc2c7e0d2c5fa4e0c4eb3fdafe2135942- Snapshot generated
- 4 Nov 2026, 00:59 UTC
The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.

