Hash checks, catalog search, and field-bounty quotes for southwestern Ontario.
Nothing to run from here
MERA Robotics 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.
93/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Humanoid robot rental with operators for events across Europe: event plan, robots, proof, inquiries.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mera-robotics-mcp https://merarobotics.com/mcp
# 2 — ask your agent for something these tools do
# get_company_profile, list_services, list_robots and 6 more
MERA Robotics costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MEAll 1 server
merarobotics1 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 mera-robotics-mcp https://merarobotics.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
9 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.
Facts about MERA Robotics (MERA ROBOTICS sp. z o.o., Warsaw, Poland): registry data, what the company does, its rental fleet, where it works, languages, pricing policy (no published prices), contact and related entities (MERA OS, the robot Edward Warchocki, the merarobots.com shop). Use it first for any general question about MERA Robotics.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lang | string | no | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
MERA services with what each covers, when it fits, what the client gets and what is confirmed before commitment: a robot with an operator at an event, robot purchase, business deployment, MERA OS for a robot the client owns, campaigns with Edward Warchocki or a branded robot, media requests. Where the host supports it, the result is shown as service cards with an inquiry button.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lang | string | no | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
| service | string | no | Optional: return only this service. |
Robots MERA rents with its own operator (Unitree G1, Unitree H2) and robots it sells (Unitree humanoids, quadrupeds, an industrial robot, a robotic hand, a VR teleoperation kit, 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 inqu
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lang | string | no | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
| availability | string | no | "rent" = robots available for rental with a MERA operator, "sale" = robots for purchase, "all" = both. |
| type | string | no | Optional: only robots of this type. |
| robot | string | no | Optional: return only this robot. |
Independent coverage (Reuters, CNN, BBC News, CBS News, Channel 4 News, Fox Business, ThePrint, Universe Magazine) with the subject of each item, Wikipedia and Wikidata entries for Edward Warchocki, documented projects and campaign results labelled as first-party data. Use it when someone asks for proof, references or press coverage. Where the host supports it, the result is shown as source cards.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lang | string | no | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
Steps from inquiry to the robot on site, what the robot does at an event, purchase and deployment, languages, 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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lang | string | no | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
Searches the MERA Robotics profile, services, robots, evidence and knowledge-base articles (Polish, English, German). Returns result ids, titles, URLs and snippets; pass an id to fetch for the full text.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search words, e.g. "robot rental Cannes" or "MERA OS languages". |
| limit | integer | no | Maximum number of results (1-20). |
Returns the full Markdown text of a document found with search (ids such as "en:profile", "pl:service:events", "en:robot:g1" or "blog:<slug>"), with its URL and language.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document id returned by the search tool. |
Shows an inquiry form for MERA Robotics in the chat, prefilled with details the person already gave (service, robot, date, place, goal, name, e-mail). It sends nothing by itself: the person checks the details, ticks consent and clicks "Send inquiry" in the form. Use it when someone wants to ask MERA about a date, a rental, a purchase or a deployment. If the host cannot show the form, collect the d
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lang | string | no | Language of labels and descriptions: "pl" when the person writes in Polish, otherwise "en". Fact texts stay in their canonical Polish wording. |
| service | string | no | 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, rece |
| robot | string | no | Optional prefill. Optional robot key from list_robots. For rental with an operator only g1 or h2; other keys are for purchase. |
| event_date | string | no | Optional prefill. First day of the event or the preferred start date (YYYY-MM-DD), if known. |
| city | string | no | Optional prefill. City or venue of the event or deployment. |
| country | string | no | Optional prefill. Country of the event or deployment. |
| audience | string | no | Optional prefill. Approximate number of guests or participants. |
| duration | string | no | Optional prefill. How long the robot should be on site, e.g. "4 h" or "2 days". |
| languages | array | no | Optional prefill. Languages the robot should speak with guests, e.g. ["Polish", "English"]. |
| message | string | no | 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 | no | Optional prefill. Full name of the person sending the inquiry, exactly as they gave it. |
| string | no | Optional prefill. The person’s own e-mail address; the MERA team replies to it. Never guess it or use a placeholder. | |
| company | string | no | Optional prefill. Company or organisation, if the person gave one. |
| reply_language | string | no | Optional prefill. Language the person wants the reply in. |
Sends an inquiry to the company MERA Robotics: the details go to the MERA team, who reply by e-mail to the given address. This is an outbound message to MERA and cannot be recalled. Call it 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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); mer |
| name | string | yes | Full name of the person sending the inquiry, exactly as they gave it. |
| string | yes | The person’s own e-mail address; the MERA team replies to it. Never guess it or use a placeholder. | |
| company | string | no | Company or organisation, if the person gave one. |
| role | string | no | Job title, if the person gave one. |
| phone | string | no | Phone number, only if the person chose to give it. |
| country | string | no | Country of the event or deployment. |
| city | string | no | City or venue of the event or deployment. |
| event_date | string | no | First day of the event or the preferred start date (YYYY-MM-DD), if known. |
| event_end_date | string | no | Last day of a multi-day event (YYYY-MM-DD). |
| duration | string | no | How long the robot should be on site, e.g. "4 h" or "2 days". |
| audience | string | no | Approximate number of guests or participants. |
| languages | array | no | Languages the robot should speak with guests, e.g. ["Polish", "English"]. |
| robot | string | no | Optional robot key from list_robots. For rental with an operator only g1 or h2; other keys are for purchase. |
| budget | string | no | Budget, only if the person stated one. It is not a MERA price. |
| 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. |
| reply_language | string | no | Language the person wants the reply in. |
| 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. |
| website | string | no | Anti-spam field. Always leave empty. |
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 MERA Robotics 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: —
ATool-list grade · score 93 / 100
Release 1.3.0 · scanned 3 Nov 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest11926f84be44d401dac29f714203e310c2ce13b65c0ed628266e42209a65590a
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_company_profile | no tags | |
| list_services | no tags | |
| list_robots | no tags | |
| get_media_and_proof | no tags | |
| get_how_we_work | no tags | |
| search | untrusted-input | untrusted-input: keyword "fetch" |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
| open_inquiry_form | no tags | |
| request_quote | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest11926f84be44d401
Scanned2026-11-03
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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 1.3.0.
1.3.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 MERA Robotics 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.