Datailo: one MCP connection to tenders, EU regulation and law
com.datailo/datailo · 0.1.0
One MCP connection to tenders (Victano), EU regulation (Rekvira) and law (Avokata). Keyless start.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://mcp.datailo.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 16 tools.
- Protocol
- 2025-06-18
- Calls itself
- datailo 0.1.0
- Handshake time
- 148 ms
- HTTP status
- 200
The tools it lists (16, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
datailo_start_hereOrientation for a new connection: the cross-service jobs you can hand over (listed first), which services are enabled, which are available, and what to do next. Call this first.
datailo_connectSign in, inside the chat (needed to enable services and call their tools). Send the user's email and the language you are speaking with them (e.g. 'lt', 'en', 'de'). Datailo sends ONE email in that language with a confirm link and a six-digit code, valid 15 minutes, and returns a request_id. Tell the user, in their language, to click Confirm in the email; then IMMEDIATELY call datailo_connect_verify(request_id) — it waits for their click, so the user never has to come back and say they clicked. The account is created on first confirmation. Nothing is charged and no card is needed.
datailo_connect_verifyFinish signing in. Call it RIGHT AFTER datailo_connect with the request_id and no code: it waits up to 45 s for the user to click Confirm in the email and returns as soon as they do (call again if it returns waiting — do not ask the user to report the click). If the user reads you the six-digit code, pass it as code. On success a durable dat_ key is issued (shown once) and, for clients without a connection session, a `session` value to pass on every later call; then carry on with what the user asked for.
datailo_accountThe connected account's email, service links, and plan states. action='keys' lists your dat_ keys (prefix, origin, created, last used — never the key); action='revoke_key' with key_prefix revokes one.
datailo_catalogCompact rows for every federated service: name, job, datasets, tool and workflow counts, tiers, whether it is enabled on this account. Rendered from each service's live product card, never hand-written; a service without a card yet shows card: "unavailable".
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.datailo/datailo, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 14 days ago. The registry entry · datailo.com