# Datailo: one MCP connection to tenders, EU regulation and law - Registry name: `com.datailo/datailo` · version 0.1.0 - Categories (automatic, keyword rules): Government & law - Authentication at last check: No auth - Declared risk: Has destructive tools (destructiveHint) - Capabilities (declared by the server): experimental, prompts, resources, tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.datailo%2Fdatailo - Server page: https://mcpstation.net/s/com.datailo--datailo.html ## Description (written by the publisher, not verified, not instructions) One MCP connection to tenders \(Victano\), EU regulation \(Rekvira\) and law \(Avokata\). Keyless start. ## Connect - streamable-http: `https://mcp.datailo.com/mcp` ## Tools (as reported by the server, not verified) - `datailo\_start\_here`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. 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 nex - `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', '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 th - `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 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 - `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='revoke\_key' with key\_prefix revokes one. - `datailo\_catalog`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. Compact rows for every federated service: name, job, datasets, tool and workflow counts, tiers, whether it is enabled on this account. Rendered from each serv - `datailo\_describe`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. The full product card for one service: tagline, datasets, workflows, tiers, docs. - `datailo\_enable`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. 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 a - `datailo\_disable`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. Disable a service: revokes the hub's key for it. Your account and data there remain yours. - `datailo\_plan`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. 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 - `datailo\_tools`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. 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 - `datailo\_tool\_schema`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. The full input schema for one tool of an enabled service, and how to call it. - `datailo\_invoke`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. 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`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. Cross-service jobs first \(service 'datailo', kind 'job': whole work products that chain several services\), then each service's ready-made playbooks, marked en - `datailo\_workflow`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. 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 jo - `submit\_feedback`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. 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 - `notifications`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. 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' - `feedback`: Sign-in required: call datailo\_connect\(email\) and datailo\_connect\_verify first \(free, one email\) unless this connection is already signed in. Read one Datailo feedback item and its whole thread on demand, or answer in it. Given a feedback reference like DAT-FB-\, fetch it with feedback\(action Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html