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

An MCP server sees every request your assistant sends it, and a server that connects you to other services also holds keys to them. The protocol leaves most of the trust decisions to the operator. Its transport specification says so plainly for remote servers:

“Servers SHOULD implement proper authentication for all connections”

Source: MCP specification, Transports, Security Warning (version 2025-06-18). “Should” leaves it to each server. So before connecting one, check for yourself. Below are seven checks and what Datailo’s hub answered on 24 September 2026, when we ran each one against the live server.

The checklist

#CheckHow to test itDatailo’s answer
1Does it refuse work before sign-in?Call a data tool without signing inRefused: sign_in_required, with the steps to sign in
2What does it store about you?Read the privacy notice, then ask the serverEmail, hashed codes and keys, service links with the service’s key encrypted, call records without arguments or results
3Does it store your questions?The privacy notice’s call-record lineNo: “Never the arguments you sent and never the result”
4Can you revoke its access to a service?Disable a service, then call itRevoked; the next call was refused with not_enabled
5Can you get your data out and delete it?Look for export and deletion routes/api/account/export with your key; deletion by emailed confirmation
6Do its tools say what they change?Read the tool annotations in tools/list8 of 15 tools marked read-only; datailo_disable marked destructive
7Where does your data go next?The list of services and sub-processorsEach enabled service gets your email and hub account id; a service without accounts gets nothing that identifies you

1. Before sign-in

Our test called datailo_invoke on a fresh connection without signing in. The hub refused in 72 ms with the error sign_in_required and told the assistant how to proceed: sign in with datailo_connect, or pass the session value a client without its own session received earlier. Browsing the catalogue works without an account; calling a service’s tools does not.

2 and 3. What it keeps

datailo_account returned the account’s email, its tier, how it was authenticated (via: key), the three service links and two privacy routes. The privacy notice lists each category the hub stores. For your questions, the line that matters is the one on call records:

“For a call through the hub: time, account, service, tool, whether it succeeded, how long it took, and whether it came from our own testing or monitoring (a label, not your address). Never the arguments you sent and never the result.”

A hub stores less than the services behind it. The work you do at a service, such as a saved tender decision, stays at that service under its own notice.

4. Revoking access

datailo_disable for Victano took 169 ms and answered: “The hub’s key for this service was revoked; your account and data at the service remain yours.” The next call to Victano through the hub came back refused, not_enabled, with the instruction to enable it again. Revocation took effect on the next call.

5. Export and deletion

The account record names both routes: https://datailo.com/api/account/export and https://datailo.com/api/account/delete, the second with the note “Deletion requires a separate inbox confirmation.” The privacy notice gives the reason: “a request typed into a chat is not proof that the account holder wants it gone.”

6. Tool annotations

MCP tools can carry hints that tell a client what a tool does: read-only, destructive, idempotent. Clients can use them to ask you before a risky call. Datailo’s tools/list on 24 September 2026:

HintTools
Read-onlydatailo_start_here, datailo_account, datailo_catalog, datailo_describe, datailo_tools, datailo_tool_schema, datailo_workflows, datailo_workflow (8 of 15)
Changes something, not destructivedatailo_connect, datailo_connect_verify, datailo_enable, datailo_plan, datailo_feedback
Destructivedatailo_disable
Depends on the service tooldatailo_invoke (not read-only; what it changes depends on the tool it calls)

Annotations are hints written by the server’s author. A client can show them to you, but it cannot verify them.

7. Where your data goes next

A hub is a new party between you and each service. Datailo’s notice states what it passes on: for a service with accounts, “your email address and your hub account id”; a service without accounts (Rekvira) “receives nothing that identifies you”. The sub-processors page lists the providers the hub itself uses.

The recorded run

Before you connect an MCP server that holds keys to other services: what does it store, what can you revoke, and what does it refuse? Recorded 24 Sep 2026 through https://mcp.datailo.com/mcp; 8 calls, each with the time it took from our test machine.

Every call in the run (8)
  1. datailo_connect email=content-proof@example.test 63 ms. sign-in started with an email address
  2. datailo_connect_verify request_id=[redacted], code=[redacted] 29 ms. signed in; the hub issued a key for the later calls
  3. datailo_invoke (not signed in) service=rekvira, tool=list_regulations 72 ms. Not signed in on this call. If the user already signed in earlier in this conversation, pass session=<the session value datailo_connect_verify returned> on this and every later call (this client…
  4. datailo_enable service=victano 322 ms. Victano switched on (partner)
  5. datailo_enable service=rekvira 33 ms. Rekvira switched on (keyless)
  6. datailo_account 30 ms. what the hub holds for this account
  7. datailo_disable service=victano 169 ms.
  8. datailo_invoke service=victano, tool=search_opportunities 32 ms. victano is not enabled on your account. Call datailo_enable(service='victano').

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: show me what the hub holds about my account, then switch Victano off and confirm that a Victano call no longer goes through.