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

merdata

https://merdata.no

Registry code: 3b1466f540a6d9e5

api record

merdata.no sells data-only travel eSIMs for about 200 countries to buyers in Norway, priced in NOK including VAT. Use search_destinations to find a country or region code, recommend or list_packages to compare packages, and quote for the exact total before you give the buyer a link. The buyer opens order_url and pays on merdata.no with Vipps or card; never ask for card details, e-mail or an activation code in the chat. Compare packages on network, internet breakout and speed after the cap, not only price. check_device and install_help answer setup questions.

endpoint
https://merdata.no/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 merdata live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is merdata free to use?
Yes — the hub reached it with no key and no payment.
What tools does merdata have?
8 tools: search_destinations, quote, recommend, get_package, policies, list_packages, check_device, install_help.
Is merdata 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
135ms

last good check

priced tools
0

of 8 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

_ what it can do 8 tools
2 open 6 never probed 2 of 8 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.

  • check_device open 1h ago

    How to check whether a phone supports eSIM, the oldest supported models per brand, and what else the phone needs (unlocked, iOS version for one-tap install).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • install_help open 1h ago

    Step-by-step install and switch-on instructions for iPhone and Android, the same as merdata.no/oppsett. The eSIM itself is in the buyer's e-mail.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "platform": {
      "enum": [
        "ios",
        "android"
      ],
      "type": "string",
      "description": "Leave out for both."
    }
  }
}
    arguments 13 lines
  • search_destinations unknown never probed

    Countries and regional bundles merdata.no sells, with the lowest package price for each. Filter by country name (English or Norwegian) or ISO code. Use the returned country_code or region_code in the other tools.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "Part of a country or region name, or an ISO code. Empty returns everything."
    }
  }
}
    arguments 9 lines
  • quote unknown never probed

    The exact total checkout will charge for a package, a day count (day passes only) and a number of eSIMs (one per traveller), with the checkout link. Quote before you give the buyer a price.

    mcp-tool

    {
  "type": "object",
  "required": [
    "package_id"
  ],
  "properties": {
    "days": {
      "type": "integer",
      "minimum": 1,
      "description": "Day passes only: number of days."
    },
    "quantity": {
      "type": "integer",
      "minimum": 1,
      "description": "Number of eSIMs, one per traveller."
    },
    "package_id": {
      "type": "string"
    }
  }
}
    arguments 21 lines
  • recommend unknown never probed

    The cheapest fixed packages that last the whole trip (and hold data_gb if given), plus the one with the lowest price per GB (best_value) if it is not among them, and the cheapest day passes for the same number of days. Returns options to explain to the buyer, not a decision.

    mcp-tool

    {
  "type": "object",
  "required": [
    "country_code",
    "trip_days"
  ],
  "properties": {
    "data_gb": {
      "type": "number",
      "description": "Total data the buyer expects to use on the trip."
    },
    "trip_days": {
      "type": "integer",
      "minimum": 1
    },
    "country_code": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2."
    }
  }
}
    arguments 21 lines
  • get_package unknown never probed

    Full details for one package id.

    mcp-tool

    {
  "type": "object",
  "required": [
    "package_id"
  ],
  "properties": {
    "package_id": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • policies unknown never probed

    Seller, VAT, payment, refunds, when validity starts, data-only, install once, how to top up, support contact.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • list_packages unknown 1h ago

    Every package for one country or regional bundle, as shown on merdata.no: data, validity, live price in NOK incl. VAT, network operators and technology, speed after the cap, internet breakout country, top-up support, payment methods and a checkout link. Give country_code or region_code.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "region_code": {
      "type": "string",
      "description": "Regional bundle code from search_destinations."
    },
    "country_code": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2, e.g. TH."
    }
  }
}
    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 3b1466f540a6d9e5.

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

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.