Datailo: one MCP connection to tenders, EU regulation and law

Name: Datailo: one MCP connection to tenders, EU regulation and law
Author: com.datailo

MCP serverMCP

One MCP connection to tenders (Victano), EU regulation (Rekvira) and law (Avokata). Keyless start.

by com.datailohomepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"datailo-one-mcp-connection-to-tenders-eu-regulat","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability54/54 checks ok

when	check	result	http	latency	detail
3 h ago	mcp initialize	ok	200	75 ms	server datailo 0.1.0 · protocol 2025-06-18 · 16 tools
10 h ago	mcp initialize	ok	200	68 ms	server datailo 0.1.0 · protocol 2025-06-18 · 16 tools
17 h ago	mcp initialize	ok	200	91 ms	server datailo 0.1.0 · protocol 2025-06-18 · 16 tools
23 h ago	mcp initialize	ok	200	54 ms	server datailo 0.1.0 · protocol 2025-06-18 · 16 tools
30 h ago	mcp initialize	ok	200	85 ms	server datailo 0.1.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	84 ms	server datailo 0.1.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	71 ms	server datailo 0.1.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	62 ms	server datailo 0.1.0 · protocol 2025-06-18 · 16 tools
2 d ago	mcp initialize	ok	200	56 ms	server datailo 0.1.0 · protocol 2025-06-18 · 16 tools
3 d ago	mcp initialize	ok	200	82 ms	server datailo 0.1.0 · protocol 2025-06-18 · 16 tools

Tools observed via MCP handshake

datailo_start_here — Orientation 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.
datailo_connect — Sign 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', '
datailo_connect_verify — Finish 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 retur
datailo_account — The connected account's email, service links, and plan states. action='keys' lists your dat_ keys (prefix, origin, created, last used — never the key); action='
datailo_catalog — Compact rows for every federated service: name, job, datasets, tool and workflow counts, tiers, whether it is enabled on this account. Rendered from each servic
datailo_describe — The full product card for one service: tagline, datasets, workflows, tiers, docs.
datailo_enable — Enable a federated service on your Datailo account. For services with an account model the hub links (or creates) your account there by your email and keeps an
datailo_disable — Disable a service: revokes the hub's key for it. Your account and data there remain yours.
datailo_plan — See a service's plan (action: status | enroll | change | discontinue). Everything is free during the beta: there is no paid plan to choose, nothing is charged a
datailo_tools — Search the tools of your enabled services (read live from each service). q takes words or a whole sentence: tools are ranked by the words they match, name and t
datailo_tool_schema — The full input schema for one tool of an enabled service, and how to call it.
datailo_invoke — Call one tool of an enabled service through the hub: service, tool name and its arguments (see datailo_tool_schema). Returns the service's own result.
datailo_workflows — Cross-service jobs first (service 'datailo', kind 'job': whole work products that chain several services), then each service's ready-made playbooks, marked enab
datailo_workflow — One playbook's steps from the service itself, each annotated with the exact datailo_invoke call to run it through this connection. service='datailo' with a job
submit_feedback — Send feedback about Datailo to the team that builds it: a bug, a wrong answer, missing data, a missing feature, a workflow idea, or praise. Every item is read b
notifications — Messages from the Datailo team to this person: replies to their feedback, questions about it, service notices and news about the tools they use. action='list' s

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.datailo/datailo

first seen 15 d ago · fetched 20 h agoopen ↗

Field history (6 recent events)

15 d ago · declared · summary → "One MCP connection to tenders (Victano), EU regulation (Rekvira) and law (Avokata). Keyless start."
15 d ago · declared · description → "One MCP connection to tenders (Victano), EU regulation (Rekvira) and law (Avokata). Keyless start."
15 d ago · declared · publisherName → "com.datailo"
15 d ago · declared · homepageUrl → "https://datailo.com"
15 d ago · declared · version → "0.1.0"
15 d ago · declared · protocols → ["mcp"]

Datailo: one MCP connection to tenders, EU regulation and law

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from