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

portugal-internet

https://www.portugalinternet.com

Registry code: cd09b0a0e4c7c0df

api record

Portugal Internet sells a truly unlimited data eSIM for travellers to Portugal (mainland, Madeira and the Azores), priced by trip length. To help a traveller buy one: get_esim_portugal_plans for the tiers, then quote_esim_portugal with their first and last day for the live price and a booking link with the dates chosen; give them the link. You cannot complete payment: the traveller pays at checkout. Quote only prices these tools return.

endpoint
https://www.portugalinternet.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 portugal-internet live?
Yes — it answered the hub's last check (checked 50m ago). It answered 100% of checks over the last 30 days.
Is portugal-internet free to use?
Yes — the hub reached it with no key and no payment.
What tools does portugal-internet have?
2 tools: quote_esim_portugal, get_esim_portugal_plans.
Is portugal-internet 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
215ms

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

_ what it can do 2 tools
1 open 1 never probed 1 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_esim_portugal_plans open 50m ago

    The Portugal Internet eSIM for travellers to Portugal (mainland, Madeira, Azores): truly unlimited data, priced by trip length. Returns the price tiers and what the eSIM includes. quote_esim_portugal gives the exact price for given dates.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • quote_esim_portugal unknown 50m ago

    The live price of the Portugal eSIM for the traveller's dates, and a booking link with those dates already chosen. It does not pay or place an order: the traveller opens the link, continues to checkout, enters their details and pays. Dates are the first and last day the traveller needs data, inclusive (a trip from 2 to 9 November is 8 days). One eSIM per booking.

    mcp-tool

    {
  "type": "object",
  "required": [
    "start_date",
    "end_date"
  ],
  "properties": {
    "end_date": {
      "type": "string",
      "description": "Last day the eSIM is needed, YYYY-MM-DD."
    },
    "start_date": {
      "type": "string",
      "description": "First day the eSIM is needed, YYYY-MM-DD. Today or later."
    }
  },
  "additionalProperties": false
}
    arguments 18 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 cd09b0a0e4c7c0df.

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