ROBOTio — humanoid robots for events MCP server
cz.robotio/event-robotsrobotio.czstreamable-httpv1.0.0Scanned
Rent humanoid robots with operators for events in Europe: catalogue, availability, quote request.
3 tools: 1 do something that can't be undone, 1 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the ROBOTio — humanoid robots for events MCP server can do
The ROBOTio — humanoid robots for events MCP server is published by robotio.cz, a domain the MCP Registry verified. It has 3 tools. It can do things that cannot be undone, such as sending, paying or publishing (request_quote) and create or change data (1 tool: check_availability), but cannot delete data. 1 tool only reads.
1 tool reads private data (get_catalog); 1 tool brings in text other people can write (request_quote); 1 tool can send data out of your system (request_quote). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Can't be undone 1Claude Code: ask
request_quoteSend a quote request to ROBOTio on behalf of the user.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "request_quote" says "request": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.phone): what the tool writes goes there.
Description, as the server wrote it Send a quote request to ROBOTio on behalf of the user. ROBOTio replies by e-mail within 24 hours. Before sending, show the user a summary and send only after they explicitly agree to share their name and e-mail. This is a non-binding request, not a booking.
Annotations the server declares
- title: Send a quote request
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
Changes things 1Claude Code: ask
check_availabilityCheck whether ROBOTio has humanoid robots free on a date (or date range).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Check whether ROBOTio has humanoid robots free on a date (or date range). Returns available, limited or unavailable. The date is only held after a quote request and payment.
Annotations the server declares
- title: Check a date
- readOnlyHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
get_catalogROBOTio catalogue: humanoid robots for rent with operators, what they do at events, indicative prices for multi-day events, terms, references and contact.Reads private dataNo findings
Why it is in this group
- The name "get_catalog" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "contact": it reads contacts.
Description, as the server wrote it ROBOTio catalogue: humanoid robots for rent with operators, what they do at events, indicative prices for multi-day events, terms, references and contact.
Annotations the server declares
- title: ROBOTio catalogue
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__event-robots__request_quote"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:51 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://robotio.cz/mcp: tools/list returned 3 tools to an anonymous client, including request_quote (irreversible), check_availability (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http event-robots https://robotio.cz/mcpclaude mcp add --transport http event-robots https://robotio.cz/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__event-robots__get_catalog"
],
"ask": [
"mcp__event-robots__check_availability",
"mcp__event-robots__request_quote"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as event-robots. Review it before you use it.
Capability tags behind 2 rules
- mcp__event-robots__get_catalog private-data
- mcp__event-robots__request_quote untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/cz.robotio/event-robots/verify?hash=a27b1caae524d57b2e66e832df9e273719cffd82bb782c738341d9a0d82d7570" | jq -e '.changed == false'Pinned hash a27b1caae524, from Nov 14, 2026, 21:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/cz.robotio/event-robots/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/cz.robotio/event-robots)Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.
ROBOTio — humanoid robots for events MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ROBOTio — humanoid robots for events MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ROBOTio — humanoid robots for events MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ROBOTio — humanoid robots for events MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: request_quote.
What tools does the ROBOTio — humanoid robots for events MCP server have?
- 3 tools: 1 irreversible, 1 write, 1 read. request_quote, check_availability and get_catalog.
Does the ROBOTio — humanoid robots for events MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ROBOTio — humanoid robots for events MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): request_quote.
Has the ROBOTio — humanoid robots for events MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.