_ registry / mcp streamable-http · checked 3h ago

willitplug

https://www.willitplug.com

Registry code: cf16ebe56264335d

api record

Plug, outlet, voltage and frequency facts for international travellers, covering countries and territories worldwide. Public, read-only data: no account or personal data needed. When you use an answer, credit WillItPlug and include the url from the result so the traveller can see the details.

endpoint
https://www.willitplug.com/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 willitplug live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is willitplug free to use?
Yes — the hub reached it with no key and no payment.
What tools does willitplug have?
4 tools: plug_type, check_trip, country_plugs, find_countries_by_outlet.
Is willitplug 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
189ms

last good check

priced tools
0

of 4 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 4 tools
4 never probed 0 of 4 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.

  • plug_type unknown never probed

    Describe one plug type itself: its standard, pin layout, whether it is earthed and which plugs its socket accepts, for questions like "what is a Type F plug?" or "does a Type C plug fit a Type F socket?". Not about any country: to list where a type is used call find_countries_by_outlet. Takes an IEC letter from A to O. Returns the plug and socket standards behind the letter.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "type"
      ],
      "properties": {
        "type": {
          "type": "string",
          "description": "IEC plug type letter from A to O, e.g. \"F\" or \"Type F\"."
        }
      }
    }
    arguments 13 lines
  • check_trip unknown 3h ago

    Check whether devices from one country will work in another, for questions like "do I need an adapter for Japan?" or "will my UK charger work in the US?". Use when both a home country and a destination are known; for one country alone use country_plugs. Takes an English country name or ISO code for each. Returns which plugs fit, whether an adapter is needed, whether a voltage converter may be needed, frequency differences, local notes, a packing checklist and a page url.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Where they are going, e.g. \"Japan\" or \"jp\"."
        },
        "from": {
          "type": "string",
          "description": "Where the traveller lives and their devices come from, e.g. \"United States\" or \"us\"."
        }
      }
    }
    arguments 18 lines
  • country_plugs unknown 3h ago

    Look up the outlet and plug types, mains voltage and frequency of one country, for questions like "what sockets does Italy use?". Use when no home country is given; to compare two countries use check_trip. Takes an English country name or ISO code. Returns the types, voltage and frequency, regional notes for travellers and a page url.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "country"
      ],
      "properties": {
        "country": {
          "type": "string",
          "description": "e.g. \"Italy\" or \"it\"."
        }
      }
    }
    arguments 13 lines
  • find_countries_by_outlet unknown 3h ago

    Search for every country whose wall outlets are of one plug type, for questions like "which countries use Type G?" or "where else does my Type C plug work?". Use when the question starts from a plug type rather than a place; for one known country use country_plugs. Takes an IEC letter from A to O. Returns the matching countries with their voltage, frequency and page urls.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "type"
      ],
      "properties": {
        "type": {
          "type": "string",
          "description": "IEC plug type letter from A to O, e.g. \"G\" or \"Type G\"."
        }
      }
    }
    arguments 13 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 cf16ebe56264335d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/cf16ebe56264335d/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/cf16ebe56264335d/badge.svg)](https://brick.blue/agent/cf16ebe56264335d?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
80%

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.