Built from a run recorded on 24 Sep 2026 against the live services.

  • Connect and list tools

    34 ms

    median of 3 fresh connections, 15 tools

    measured in this run

    Recorded 24 Sep 2026

  • A hub-only call

    30 ms

    datailo_catalog, median of 5

    measured in this run

    Recorded 24 Sep 2026

  • A call through to a service

    280 ms

    Rekvira read_unit (GDPR Article 5(1)) via datailo_invoke, median of 3

    measured in this run

    Recorded 24 Sep 2026

The Model Context Protocol defines two standard ways for an assistant to talk to a server. In the first, stdio, the client starts the server as a program on your computer. In the second, the server runs somewhere else and the client reaches it over the web. The specification describes that second transport like this:

“In the Streamable HTTP transport, the server operates as an independent process that can handle multiple client connections. This transport uses HTTP POST and GET requests.”

Source: MCP specification, Transports (version 2025-06-18). The same page requires a single endpoint “that supports both POST and GET methods”, for example https://example.com/mcp. That URL is what you paste into a client.

What does a remote server look like from the client?

Datailo runs one at https://mcp.datailo.com/mcp. On 24 September 2026 we timed it from a test machine in the EU:

StepWhat happenedTime
Connect and list toolsA fresh connection: initialize, then tools/list, 15 tools. Three runs.68, 34 and 30 ms (median 34)
Sign indatailo_connect with an email, then datailo_connect_verify109 ms and 40 ms
A hub-only calldatailo_catalog, five times28 to 32 ms (median 30)
A call passed throughdatailo_invoke to Rekvira read_unit, GDPR Article 5(1), three times272, 446 and 280 ms (median 280)

The pattern is the one you would expect. A call the hub answers itself costs one network round trip. A call it passes to a data service adds that service’s work: Rekvira looked up the article and returned its full text, with the date it gives for its EUR-Lex copy, 2 September 2026.

How is a remote server different from a local one?

Local (stdio)Remote (Streamable HTTP)
Where it runsOn your computer, started by the clientOn a server, reached at one HTTPS endpoint
What you configureA command, arguments and often an API key in a JSON fileA URL, and a sign-in if the server asks for one
UpdatesYou update the packageThe operator updates the server; you see the new tools on the next tools/list
Works on phone and web clientsNoYes, where the client supports custom connectors
Who sees your requestsOnly the program on your machine (and whatever it calls)The server’s operator

The last row is the one to think about. A remote server receives the questions your assistant sends it. Before you connect one, read what its operator keeps; Datailo’s privacy notice lists what the hub stores.

How does sign-in work on a remote server?

The specification lets a server keep a session per connection (an Mcp-Session-Id header). Some clients do not keep one between calls. When our test sent a call before signing in, the hub answered with an instruction rather than a failure:

“Not signed in on this call. If the user already signed in earlier in this conversation, pass session= on this and every later call (this client keeps no connection session).”

That is the reply of the live server on 24 September 2026, from a second run we recorded the same day. An assistant can act on that reply without asking the user, which is why the hub writes its errors for a model to read.

The recorded run

What does a remote MCP server look like from the client side, and how long does each step take? Recorded 24 Sep 2026 through https://mcp.datailo.com/mcp; 11 calls, each with the time it took from our test machine.

Every call in the run (11)
  1. datailo_connect email=content-proof@example.test 109 ms. sign-in started with an email address
  2. datailo_connect_verify request_id=[redacted], code=[redacted] 40 ms. signed in; the hub issued a key for the later calls
  3. datailo_enable service=rekvira 85 ms. Rekvira switched on (keyless)
  4. datailo_catalog 28 ms. 3 services
  5. datailo_catalog 28 ms. 3 services
  6. datailo_catalog 32 ms. 3 services
  7. datailo_catalog 30 ms. 3 services
  8. datailo_catalog 30 ms. 3 services
  9. datailo_invoke → rekvira.read_unit regulation=gdpr, pinpoint=Article 5(1) 272 ms. GDPR Article 5(1), through the hub
    • Article 5(1) Personal data shall be: (a) processed lawfully, fairly and in a transparent manner in relation to the data subject (‘lawfulness, fairness and transparency’); (b) collected for specified, explicit and legitimate purposes…
  10. datailo_invoke → rekvira.read_unit regulation=gdpr, pinpoint=Article 5(1) 446 ms. GDPR Article 5(1), through the hub
    • Article 5(1) Personal data shall be: (a) processed lawfully, fairly and in a transparent manner in relation to the data subject (‘lawfulness, fairness and transparency’); (b) collected for specified, explicit and legitimate purposes…
  11. datailo_invoke → rekvira.read_unit regulation=gdpr, pinpoint=Article 5(1) 280 ms. GDPR Article 5(1), through the hub
    • Article 5(1) Personal data shall be: (a) processed lawfully, fairly and in a transparent manner in relation to the data subject (‘lawfulness, fairness and transparency’); (b) collected for specified, explicit and legitimate purposes…

Try it in your assistant

Add the address to your client (setup per client), then paste the prompt. Signing in takes an email code; the three services are free during the beta.

Connector address
https://mcp.datailo.com/mcp

Then say

Use Datailo: switch on Rekvira and read me Article 5(1) of the GDPR, with the date of the text it holds.