Home / MCP registry index / io.github.adriancasas/geo360-concierge

GEO360 Sovereign Concierge & B2A Clearinghouse

io.github.adriancasas/geo360-concierge in the official MCP registry. Endpoint https://geo360.apolloproject.cloud/mcp. Source: github.com/adriancasas/geo360-concierge.

The registry describes it as: Sovereign AI platform for travel, luxury UHNW, and industrial wholesale B2A execution.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http geo360-concierge https://geo360.apolloproject.cloud/mcp

{
  "mcpServers": {
    "geo360-concierge": {
      "url": "https://geo360.apolloproject.cloud/mcp"
    }
  }
}

code --add-mcp '{"name":"geo360-concierge","type":"http","url":"https://geo360.apolloproject.cloud/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

geo360_search_car_rentals geo360_search_flights geo360_get_esim_connectivity geo360_claim_flight_delay geo360_active_mobility geo360_luggage_storage geo360_generate_affiliate_link geo360_hold_offer geo360_book_offer geo360_kam_handshake geo360_vip_aviation_estimate geo360_vip_aviation_confirm geo360_vip_empty_legs geo360_vip_sanctuary_search geo360_vip_marine_charter geo360_vip_master_combo geo360_acommerce_rfq geo360_acommerce_settle geo360_swiss_escrow_deposit geo360_logistics_dispatch_packet geo360_logistics_delivery_confirm geo360_swiss_escrow_cosign geo360_swiss_escrow_disburse geo360_b2a_price_context geo360_b2a_route_risk geo360_b2a_customs_gate geo360_escrow_status geo360_b2a_run_cycle geo360_aff2_search geo360_aff2_hold geo360_aff2_confirm geo360_aff2_status geo360_aff2_session_status geo360_aff2_settle geo360_catalog_discovery geo360_session_status geo360_system_health

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-adriancasas-geo360-concierge/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-adriancasas-geo360-concierge)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Travel MCP servers