Datailo: one MCP connection to tenders, EU regulation and law
One MCP connection to tenders (Victano), EU regulation (Rekvira) and law (Avokata). Keyless start.
Should I use this
Quality & Safety
Findings (1)
- LOWTool 'datailo_feedback' description lacks action verbin datailo_feedback
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"datailo": {
"url": "https://mcp.datailo.com/mcp"
}
}
}Remote endpoints
https://mcp.datailo.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (15)
🟢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. Call this first.
Input Schema
{
"type": "object",
"properties": {},
"title": "datailo_start_hereArguments"
}🟡datailo_connect(email, language)
Optional sign-in, inside the chat. 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 or read you the code; then call datailo_connect_verify. The account is created on first confirmation. Nothing is charged and no card is needed.
Input Schema
{
"type": "object",
"properties": {
"email": {
"title": "Email",
"type": "string"
},
"language": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Language"
}
},
"required": [
"email"
],
"title": "datailo_connectArguments"
}⚪datailo_connect_verify(request_id, code)
Finish signing in with the request_id from datailo_connect and EITHER the six-digit code the user gives you OR no code at all once the user says they clicked Confirm in the email. On success this conversation is signed in for 30 days and a durable dat_ key is issued (shown once).
Input Schema
{
"type": "object",
"properties": {
"request_id": {
"title": "Request Id",
"type": "string"
},
"code": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Code"
}
},
"required": [
"request_id"
],
"title": "datailo_connect_verifyArguments"
}🟢datailo_account
The connected account's email, service links, and plan states.
Input Schema
{
"type": "object",
"properties": {},
"title": "datailo_accountArguments"
}🟢datailo_catalog(q, audience)
Compact 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".
Input Schema
{
"type": "object",
"properties": {
"q": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Q"
},
"audience": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Audience"
}
},
"title": "datailo_catalogArguments"
}🟢datailo_describe(service)
The full product card for one service: tagline, datasets, workflows, tiers, docs.
Input Schema
{
"type": "object",
"properties": {
"service": {
"title": "Service",
"type": "string"
}
},
"required": [
"service"
],
"title": "datailo_describeArguments"
}⚪datailo_enable(service, plan)
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 encrypted key; keyless services are enabled as a trial. Then datailo_tools and datailo_invoke reach it through this one connection.
Input Schema
{
"type": "object",
"properties": {
"service": {
"title": "Service",
"type": "string"
},
"plan": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Plan"
}
},
"required": [
"service"
],
"title": "datailo_enableArguments"
}🔴datailo_disable(service)
Disable a service: revokes the hub's key for it. Your account and data there remain yours.
Input Schema
{
"type": "object",
"properties": {
"service": {
"title": "Service",
"type": "string"
}
},
"required": [
"service"
],
"title": "datailo_disableArguments"
}🟡datailo_plan(service, action, tier)
See a service's plans or record that you want to enroll, change or discontinue one (action: status | enroll | change | discontinue). Payments are not enabled yet: a choice is recorded as an intent, nothing is charged and no checkout link is returned.
Input Schema
{
"type": "object",
"properties": {
"service": {
"title": "Service",
"type": "string"
},
"action": {
"title": "Action",
"type": "string"
},
"tier": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Tier"
}
},
"required": [
"service",
"action"
],
"title": "datailo_planArguments"
}🟢datailo_tools(q, service, include_available, limit)
Search the tools of your enabled services (read live from each service). include_available also previews services you could enable.
Input Schema
{
"type": "object",
"properties": {
"q": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Q"
},
"service": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Service"
},
"include_available": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "null"
}
],
"default": null,
"title": "Include Available"
},
"limit": {
"anyOf": [
{
"type": "integer"
},
{
"type": "null"
}
],
"default": null,
"title": "Limit"
}
},
"title": "datailo_toolsArguments"
}🟢datailo_tool_schema(service, tool)
The full input schema for one tool of an enabled service, and how to call it.
Input Schema
{
"type": "object",
"properties": {
"service": {
"title": "Service",
"type": "string"
},
"tool": {
"title": "Tool",
"type": "string"
}
},
"required": [
"service",
"tool"
],
"title": "datailo_tool_schemaArguments"
}⚪datailo_invoke(service, tool, args)
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.
Input Schema
{
"type": "object",
"properties": {
"service": {
"title": "Service",
"type": "string"
},
"tool": {
"title": "Tool",
"type": "string"
},
"args": {
"anyOf": [
{
"additionalProperties": true,
"type": "object"
},
{
"type": "null"
}
],
"default": null,
"title": "Args"
}
},
"required": [
"service",
"tool"
],
"title": "datailo_invokeArguments"
}🟢datailo_workflows(q, service)
Ready-made playbooks across the services (from each service's live card), marked enabled or not. Open one with datailo_workflow.
Input Schema
{
"type": "object",
"properties": {
"q": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Q"
},
"service": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Service"
}
},
"title": "datailo_workflowsArguments"
}🟢datailo_workflow(service, name)
One playbook's steps from the service itself, each annotated with the exact datailo_invoke call to run it through this connection.
Input Schema
{
"type": "object",
"properties": {
"service": {
"title": "Service",
"type": "string"
},
"name": {
"title": "Name",
"type": "string"
}
},
"required": [
"service",
"name"
],
"title": "datailo_workflowArguments"
}⚪datailo_feedback(message, service, context)
Tell us what worked or did not. Kept by Datailo; also passed to the named service when it accepts feedback. Never include confidential documents.
Input Schema
{
"type": "object",
"properties": {
"message": {
"title": "Message",
"type": "string"
},
"service": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Service"
},
"context": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Context"
}
},
"required": [
"message"
],
"title": "datailo_feedbackArguments"
}Community
Evidence