Home / MCP registry index / com.datailo/datailo
Datailo: one MCP connection to tenders, EU regulation and law
com.datailo/datailo in the official MCP registry.
Endpoint https://mcp.datailo.com/mcp.
The registry describes it as: One MCP connection to tenders (Victano), EU regulation (Rekvira) and law (Avokata). Keyless start.
We read its 17 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
datailo_start_here datailo_connect datailo_connect_verify datailo_account datailo_catalog datailo_describe datailo_enable datailo_disable datailo_plan datailo_tools datailo_tool_schema datailo_invoke datailo_workflows datailo_workflow submit_feedback notifications feedback
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-datailo-datailo)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.