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

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "datailo-one-mcp-connection-to-tenders-eu-regulation-and-law": {
      "type": "http",
      "url": "https://mcp.datailo.com/mcp"
    }
  }
}

17 tools

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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…

• 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-<number>, fetch it…

Security scan

Recent checks