Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Datailo: one MCP connection to tenders, EU regulation is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
17
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
One MCP connection to tenders (Victano), EU regulation (Rekvira) and law (Avokata). Keyless start.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http datailo-one-mcp-connection-to-tenders-eu-regulati https://mcp.datailo.com/mcp
# 2 — ask your agent for something these tools do
# datailo_start_here, datailo_connect, datailo_connect_verify and 14 more
Datailo: one MCP connection to tenders, EU regulation costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DAAll 1 server
datailo1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http datailo-one-mcp-connection-to-tenders-eu-regulati https://mcp.datailo.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 next. Call this first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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 the user, in their language, to click Confirm in the email; then IMMEDIATELY call datailo_connect_veri
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | — | |
| language | no | — |
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, pass it as code. On success a durable dat_ key is issued (shown once) and, for clients without a c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
| code | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. | |
| action | no | — | |
| key_prefix | no | — |
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 service's live product card, never hand-written; a service without a card yet shows card: "unavailable".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | no | — | |
| audience | no | — | |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | — |
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 an encrypted key; keyless services are enabled as a trial. Then datailo_tools and datailo_invoke reac
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | — |
| plan | no | — | |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | — |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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 and no checkout link is returned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | — |
| action | string | yes | — |
| tier | no | — | |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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 title first. service narrows to one service; include_available also previews services you could ena
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | no | — | |
| service | no | — | |
| include_available | no | — | |
| limit | no | — | |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | — |
| tool | string | yes | — |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | — |
| tool | string | yes | — |
| args | no | — | |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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 enabled or not. Open one with datailo_workflow.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | no | — | |
| service | no | — | |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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 job name returns the whole job: services to enable, stages with their playbooks, checkpoints and the w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | — |
| name | string | yes | — |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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 by a person. When to offer it: an answer came back empty or wrong; the user corrected you or the re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | yes | One of: bug (something failed or errored), wrong_answer (an answer was returned but it was wrong or misleading), missing_data (a document, record or source the user expected is not covered), missing_f |
| what | no | The task and what went wrong or what is needed (3-50000 characters) | |
| service | no | Hub only: 'datailo' (default) or the service the feedback is about | |
| expected | no | For a wrong answer: what the right answer or result would have been (up to 20000 characters) | |
| got | no | For a wrong answer: what came back instead (up to 20000 characters) | |
| tool | no | The tool the feedback is about, if one (e.g. the tool that answered wrongly); several: comma-separated | |
| query | no | The query or arguments that produced it; only with the user's OK (up to 5000 characters) | |
| severity | no | low | normal | high | blocking (blocking: the user cannot do their work) | |
| contact_email | no | Only if the user wants a reply: the address to reply to | |
| authored_by | no | user (their words) | agent_drafted (you wrote it, they approved) | agent (your own observation) | |
| confirmed | boolean | no | true once the user approved sending this; required for authored_by user or agent_drafted |
| message | no | Older name for what, kept so earlier callers still work; prefer what | |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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' shows the inbox; 'read' with id opens one message and marks it read; 'reply' with id and body answe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | no | list (default) | read | reply | dismiss | snooze | settings |
| id | no | The message id from list (for read, reply, dismiss, snooze) | |
| body | no | For reply: the person's answer, in their words, only after they approved it (up to 50000 characters) | |
| hours | no | For snooze: how long to put the message away (default 24, at most 720) | |
| settings | no | For settings: the switches to change, e.g. {"email_feedback_replies": false}. Omit to read them. email_digest: a periodic email summary of unread messages (off by default); email_feedback_replies: an | |
| confirmed | boolean | no | For reply: true once the person approved sending these words |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
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 with feedback(action='get', ref='DAT-FB-<number>') before answering. action='get' returns the item (what was sent, its s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | no | 'get' (default) reads one item and its thread; 'reply' adds an answer to it |
| ref | no | the reference the item got when it was sent (<PRODUCT>-FB-<number>), as the person quotes it | |
| body | no | action='reply': the person's answer, in their words (plain text) | |
| confirmed | boolean | no | action='reply': true once the person has seen and agreed the text |
| full | boolean | no | action='get': true returns every thread message whole (default: the latest whole, older ones shortened) |
| session | no | The session value datailo_connect_verify returned. Pass it on every Datailo call in this conversation; omit it when the user connected with Sign in (OAuth) or a key. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Datailo: one MCP connection to tenders, EU regulation or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Datailo: one MCP connection to tenders, EU regulation can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.