_ registry / mcp streamable-http · checked 19m ago

smoover

https://api.smoover-moving.de

Registry code: 5837d430e111bae9

api record

Smoover is a moving company and moving platform for household moves within Germany and between EU countries, Switzerland and the United Kingdom.

Use get_moving_estimate for an indicative door-to-door price (EUR, incl. VAT) on a specific route; ask the user for start, destination (with country) and volume if unknown (get_move_sizes helps to estimate the volume).

endpoint
https://api.smoover-moving.de/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is smoover live?
Yes — it answered the hub's last check (checked 19m ago). It answered 100% of checks over the last 30 days.
Is smoover free to use?
Yes — the hub reached it with no key and no payment.
What tools does smoover have?
2 tools: get_moving_estimate, get_move_sizes.
Is smoover safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
290ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_moving_estimate unknown 19m ago

    Calculate an indicative price range (EUR incl. VAT) for a household move between two places in the EU, Switzerland or the UK. Uses truck road routing with real tolls, the vehicle needed for the volume and the loading/unloading crew. Returns low/high price, distance, vehicles, crew and a link where the user can request a binding fixed-price quote. Takes a few seconds. Does not create a booking.

    mcp-tool

    {
  "type": "object",
  "required": [
    "origin",
    "origin_country",
    "destination",
    "destination_country",
    "volume_m3"
  ],
  "properties": {
    "origin": {
      "type": "string",
      "description": "Start city, postcode or street address, e.g. \"Munich\" or \"10115 Berlin\""
    },
    "language": {
      "enum": [
        "en",
        "de"
      ],
      "type": "string",
      "default": "en",
      "description": "Language of the matched addresses and the quote form"
    },
    "volume_m3": {
      "type": "number",
      "maximum": 200,
      "minimum": 1,
      "description": "Volume in cubic metres. Typical: room 5, studio 10, 1-bed flat 15, 2–3 bed flat 25, house 50. Ask the user if unknown."
    },
    "destination": {
      "type": "string",
      "description": "Destination city, postcode or street address"
    },
    "origin_country": {
      "enum": [
        "AT",
        "BE",
        "BG",
        "HR",
        "CY",
        "CZ",
        "DK",
        "EE",
        "FI",
        "FR",
        "DE",
        "GR",
        "HU",
        "IE",
        "IT",
        "LV",
        "LT",
        "LU",
        "MT",
        "NL",
        "PL",
        "PT",
        "RO",
        "SK",
        "SI",
        "ES",
        "SE",
        "CH",
        "GB"
      ],
      "type": "string",
      "description": "ISO 3166-1 alpha-2 country code of the start, e.g. DE"
    },
    "destination_country": {
      "enum": [
        "AT",
        "BE",
        "BG",
        "HR",
        "CY",
        "CZ",
        "DK",
        "EE",
        "FI",
        "FR",
        "DE",
        "GR",
        "HU",
        "IE",
        "IT",
        "LV",
        "LT",
        "LU",
        "MT",
        "NL",
        "PL",
        "PT",
        "RO",
        "SK",
        "SI",
        "ES",
        "SE",
        "CH",
        "GB"
      ],
      "type": "string",
      "description": "ISO 3166-1 alpha-2 country code of the destination, e.g. ES"
    }
  },
  "additionalProperties": false
}
    arguments 106 lines
  • get_move_sizes unknown never probed

    Typical moving volumes in cubic metres per home size, to help the user pick volume_m3 for get_moving_estimate.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5837d430e111bae9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5837d430e111bae9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5837d430e111bae9/badge.svg)](https://brick.blue/agent/5837d430e111bae9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.