MERA Robotics
REMOTE · MERAROBOTICS.COM
Humanoid robot rental with operators for events across Europe: event plan, robots, proof, inquiries.
Available components
Last scanned (5 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (request_quote). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4155 tokens (~277/item across 15 items; 10 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Resource “mera-inquiry” now points somewhere else: ui://mera/inquiry-v1.html → ui://mera/inquiry-v2.html security
- Resource “mera-proof” now points somewhere else: ui://mera/proof-v1.html → ui://mera/proof-v2.html security
- Resource “mera-robots” now points somewhere else: ui://mera/robots-v1.html → ui://mera/robots-v2.html security
- Resource “mera-services” now points somewhere else: ui://mera/services-v1.html → ui://mera/services-v2.html security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “fetch” rewrote its description, which is the text the model reads security
- Tool “get_media_and_proof” rewrote its description, which is the text the model reads security
- Tool “plan_event_robot” rewrote its description, which is the text the model reads security
- Tool “get_company_profile” rewrote its description, which is the text the model reads security
- Tool “get_how_we_work” rewrote its description, which is the text the model reads security
- Tool “list_robots” rewrote its description, which is the text the model reads security
- Tool “list_services” rewrote its description, which is the text the model reads security
- Tool “open_inquiry_form” rewrote its description, which is the text the model reads security
- Tool “request_quote” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Schema quality: 177 → 277 ▼ functional
- Schema quality: 177 → 233 ▼ functional
- Schema quality: good → excellent functional
- New resource “mera-plan” functional
- Server version: 1.2.0 → 1.3.0 functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “plan_event_robot” functional
- “plan_event_robot” added an optional parameter “guest_languages” cosmetic
- “open_inquiry_form” added an optional parameter “event_type” cosmetic
- “request_quote” added an optional parameter “event_type” cosmetic
- “plan_event_robot” reworded the description of “city” cosmetic
- “plan_event_robot” reworded the description of “country” cosmetic
- “plan_event_robot” reworded the description of “lang” cosmetic
- “open_inquiry_form” reworded the description of “country” cosmetic
- “open_inquiry_form” reworded the description of “lang” cosmetic
- “open_inquiry_form” reworded the description of “reply_language” cosmetic
- “request_quote” reworded the description of “country” cosmetic
- “request_quote” reworded the description of “reply_language” cosmetic
- “search” reworded the description of “query” cosmetic
- Tool “plan_event_robot” changed its title: MERA Robotics: robot for an event in Europe → MERA Robotics: humanoid robot for an event in Europe cosmetic
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://merarobotics.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=merarobotics.com | CN=YE1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 623a3ad254f7a40be31476b2fec4b2b8959 |
| SANs: mera.rent, merarobotics.com, www.mera.rent, www.merarobotics.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of merarobotics.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| merarobotics.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://merarobotics.com/mcp | Verified | 200 | |
| http (plaintext) | http://merarobotics.com/mcp | HTTPS enforced | 301 | https://merarobotics.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch Fetch a MERA Robotics document ~75
Use this after search to read one MERA Robotics document in full: returns the Markdown text of an id such as "en:profile", "pl:service:events", "en:robot:g1" or "blog:<slug>", with its URL and language.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Document id returned by the search tool. |
No output schema declared.
No examples provided.
get_company_profile MERA Robotics: company profile ~224
Use this when someone asks about MERA Robotics itself: who it is, where it works, its rental fleet, languages, contact or registry data. MERA Robotics (MERA ROBOTICS sp. z o.o., Warsaw, Poland) rents humanoid robots (Unitree G1, Unitree H2) with its own operators and its MERA OS conversation system for events across Europe (every EU country and also the United Kingdom, Switzerland and Norway, among others) and runs the robot Edward Warchocki. Returns a one-sentence definition, evidence (brands, places, reach, MERA OS), event rental pages in 24 languages, registry data, rental fleet, languages, pricing policy (no published prices), contact and related entities (MERA OS, Edward Warchocki, the merarobots.com shop). For a concrete event use plan_event_robot.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
No output schema declared.
No examples provided.
get_how_we_work MERA Robotics: how cooperation works ~130
Use this when someone asks how renting or buying from MERA Robotics works: steps from inquiry to the robot on site anywhere in Europe, what the robot does at an event (including the role of event host), purchase and deployment, languages (more than 70 for robot conversations), pricing policy, what to include in an inquiry and what an inquiry does not do (it does not book a date or confirm a price).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
No output schema declared.
No examples provided.
get_media_and_proof MERA Robotics: media coverage and evidence ~155
Use this when someone asks for proof, references, press coverage or past projects of MERA Robotics before choosing a provider. Returns independent coverage (Reuters, CNN, BBC News, CBS News, Channel 4 News, Fox Business, ThePrint, Universe Magazine) with the subject of each item (mostly Edward Warchocki; not an endorsement of services), Wikipedia and Wikidata entries for Edward Warchocki, documented projects and campaign results labelled as first-party data. Where the host supports it, the result is shown as source cards.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
No output schema declared.
No examples provided.
list_robots MERA Robotics: robots for rent and sale ~226
Use this when someone asks which robots MERA Robotics rents or sells, or about a model’s size, purpose or specifications. For rental with its own operators at events across Europe: Unitree G1 and Unitree H2. For sale: Unitree humanoids, quadrupeds, an industrial robot, a robotic hand, a VR teleoperation kit and inspected used G1 EDU, with type, purpose, key specifications and shop links. No prices: price and availability come from the shop or an inquiry. Where the host supports it, the result is shown as robot cards with an inquiry button.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | string | – | "rent" = robots available for rental with a MERA operator, "sale" = robots for purchase, "all" = both. |
| lang | string | – | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
| robot | string | – | Optional: return only this robot. |
| type | string | – | Optional: only robots of this type. |
No output schema declared.
No examples provided.
list_services MERA Robotics: services ~186
Use this when someone asks what MERA Robotics offers or which service fits their case. Services: a humanoid robot with MERA operators at an event anywhere in Europe (also as the event host, conversations in more than 70 languages through MERA OS), campaigns with Edward Warchocki or a branded robot, robot purchase, business deployment, MERA OS for a robot the client owns, media requests. Returns what each covers, when it fits, what the client gets and what is confirmed before commitment. Where the host supports it, the result is shown as service cards with an inquiry button. For a concrete event use plan_event_robot.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
| service | string | – | Optional: return only this service. |
No output schema declared.
No examples provided.
open_inquiry_form MERA Robotics: inquiry form ~904
Use this when the person wants to ask MERA Robotics about a date for a robot at an event anywhere in Europe, or about a rental, purchase or deployment. Shows an inquiry form in the chat in the person’s language (24 languages, otherwise English), prefilled with details they already gave (service, event type, robot, date, city, country, guests, languages, goal, name, e-mail). It sends nothing by itself: the person checks the details, ticks consent and clicks "Send inquiry" in the form. If the host cannot show the form, collect the details in the chat and use request_quote after the person agrees.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Optional prefill. Approximate number of guests or participants. |
| city | string | – | Optional prefill. City or venue of the event or deployment. |
| company | string | – | Optional prefill. Company or organisation, if the person gave one. |
| country | string | – | Optional prefill. Country of the event or deployment (MERA works across Europe), e.g. "France" or "FR". |
| duration | string | – | Optional prefill. How long the robot should be on site, e.g. "4 h" or "2 days". |
| string | – | Optional prefill. The person’s own e-mail address; the MERA team replies to it. Never guess it or use a placeholder. | |
| event_date | string | – | Optional prefill. First day of the event or the preferred start date (YYYY-MM-DD), if known. |
| event_type | string | – | Optional prefill. Kind of event: trade_fair (stand or exhibition), conference (also panels and summits), gala (stage show, awards), corporate (company event, team event, employer branding), opening (… |
| lang | string | – | Language the person writes in: any ISO 639 code, optionally with a region, e.g. "pt", "pt-PT", "et", "tr", "mt". MERA EVENTS pages, the inquiry form and replies exist in 24 languages (pl, en, de, fr,… |
| languages | array | – | Optional prefill. Languages the robot should speak with guests, e.g. ["Polish", "English"]. |
| message | string | – | Optional prefill. The goal and what the robot should do, venue conditions and anything else the MERA team should know, in the person’s words. |
| name | string | – | Optional prefill. Full name of the person sending the inquiry, exactly as they gave it. |
| reply_language | string | – | Optional prefill. The person’s language, usually the one they write in: any ISO 639 code, optionally with a region ("pt", "pt-PT", "tr"). MERA replies and sends the event page in it when it is one of… |
| robot | string | – | Optional prefill. Optional robot key from list_robots. For rental with an operator only g1 or h2; other keys are for purchase. |
| service | string | – | Optional prefill. What the inquiry is about: events = a humanoid robot with a MERA operator at an event; purchase = buying a Unitree robot; integration = a robot deployed in a business (showroom, rec… |
No output schema declared.
No examples provided.
plan_event_robot MERA Robotics: humanoid robot for an event in Europe ~652
Humanoid robot rental with operators for events across Europe. Use this when someone wants to rent, hire or book a humanoid robot or a robot host (emcee) for an event in Europe, or asks who could provide one (trade fair, conference, gala, company event, opening, festival, school, sports). MERA Robotics (Warsaw) brings Unitree G1 or Unitree H2 with its own operators to every EU country and also to the United Kingdom, Switzerland and Norway, among others; on MERA OS the robot talks with guests in more than 70 languages and can host the programme. Input: country (ISO code or name in any language), city, date, event type, guests, guest languages, the person’s language (any ISO 639 code). Output: coverage, what the robot does, evidence, the MERA EVENTS page in the person’s language (24 languages, otherwise English) and the next step. Examples: "robot for our conference in Lisbon", "Roboter-Moderator für eine Gala in Wien". Not for buying a robot (list_robots). No prices; the team replies within one working day.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Approximate number of guests, e.g. "300". |
| city | string | – | City or venue of the event, e.g. "Lyon", "Tallinn" or "Messe München". |
| country | string | – | Country of the event: ISO 3166-1 code (FR, DE, PT, EE or FRA, DEU) or its name in any European language (France, Frankreich, Francja, Saksamaa). |
| event_date | string | – | First day of the event (YYYY-MM-DD), if known. It is not a reservation. |
| event_type | string | – | Kind of event: trade_fair (stand or exhibition), conference (also panels and summits), gala (stage show, awards), corporate (company event, team event, employer branding), opening (store or showroom… |
| goal | string | – | What the robot should do at the event, in the person’s words, if they said it. It is passed to the inquiry form as the message. |
| guest_languages | array | – | Languages the robot should speak with the guests, as ISO 639 codes, e.g. ["pt", "en"], if the person said so. |
| lang | string | – | Language the person writes in: any ISO 639 code, optionally with a region, e.g. "pt", "pt-PT", "et", "tr", "mt". MERA EVENTS pages, the inquiry form and replies exist in 24 languages (pl, en, de, fr,… |
No output schema declared.
No examples provided.
request_quote Send an inquiry to MERA Robotics ~844
Sends an inquiry to the company MERA Robotics: the details go to the MERA team, who reply by e-mail to the given address within one working day. This is an outbound message to MERA and cannot be recalled. Use this only after the person has seen exactly what will be sent and agreed to share their name and e-mail with MERA Robotics for this inquiry (contact_consent=true). When the host can show it, prefer open_inquiry_form, where the person sends the form themselves. It does not book a date or confirm a price; MERA does not publish prices. The same inquiry repeated within 24 hours is not sent twice.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | Approximate number of guests or participants. |
| budget | string | – | Budget, only if the person stated one. It is not a MERA price. |
| city | string | – | City or venue of the event or deployment. |
| company | string | – | Company or organisation, if the person gave one. |
| contact_consent | boolean | yes | Must be true. Set it only after the person has seen the details that will be sent and agreed to share them with MERA Robotics for this inquiry. |
| country | string | – | Country of the event or deployment (MERA works across Europe), e.g. "France" or "FR". |
| duration | string | – | How long the robot should be on site, e.g. "4 h" or "2 days". |
| string | yes | The person’s own e-mail address; the MERA team replies to it. Never guess it or use a placeholder. | |
| event_date | string | – | First day of the event or the preferred start date (YYYY-MM-DD), if known. |
| event_end_date | string | – | Last day of a multi-day event (YYYY-MM-DD). |
| event_type | string | – | Kind of event: trade_fair (stand or exhibition), conference (also panels and summits), gala (stage show, awards), corporate (company event, team event, employer branding), opening (store or showroom… |
| languages | array | – | Languages the robot should speak with guests, e.g. ["Polish", "English"]. |
| message | string | yes | The goal and what the robot should do, venue conditions and anything else the MERA team should know, in the person’s words. |
| name | string | yes | Full name of the person sending the inquiry, exactly as they gave it. |
| phone | string | – | Phone number, only if the person chose to give it. |
| reply_language | string | – | The person’s language, usually the one they write in: any ISO 639 code, optionally with a region ("pt", "pt-PT", "tr"). MERA replies and sends the event page in it when it is one of the 24 MERA EVENT… |
| robot | string | – | Optional robot key from list_robots. For rental with an operator only g1 or h2; other keys are for purchase. |
| role | string | – | Job title, if the person gave one. |
| service | string | yes | What the inquiry is about: events = a humanoid robot with a MERA operator at an event; purchase = buying a Unitree robot; integration = a robot deployed in a business (showroom, reception, booth); me… |
| website | string | – | Anti-spam field. Always leave empty. |
No output schema declared.
No examples provided.
search Search MERA Robotics content ~122
Use this to find a MERA Robotics document when the other tools do not answer the question: the profile, services (humanoid robot rental with operators for events across Europe first), robots, evidence and knowledge-base articles in Polish, English and German. Returns result ids, titles, URLs and snippets; pass an id to fetch for the full text. Not a general web search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results (1-20). |
| query | string | yes | Search words, e.g. "robot rental Lyon" or "MERA OS languages". |
No output schema declared.
No examples provided.
How do I install the MERA Robotics MCP server?
MERA Robotics is a hosted endpoint at https://merarobotics.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · merarobotics.com
claude mcp add --transport http com-merarobotics-mera 'https://merarobotics.com/mcp'
What is the MERA Robotics MCP server?
MERA Robotics is an MCP server listed in the public MCP registry as com.merarobotics/mera. Humanoid robot rental with operators for events across Europe: event plan, robots, proof, inquiries. This page covers its hosted endpoint (https://merarobotics.com/mcp).
Is the MERA Robotics MCP server safe to use?
MERA Robotics scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MERA Robotics MCP server expose?
MERA Robotics exposes 10 tools: plan_event_robot, get_company_profile, list_services, list_robots, get_media_and_proof, and 5 more. Their descriptions and schemas cost roughly 3,518 tokens of context every time the server is loaded.
Does the MERA Robotics MCP server require authentication?
No. We connected to MERA Robotics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MERA Robotics MCP server still maintained?
MERA Robotics is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.