globalrules
https://globalrules-api.onrender.com
Registry code: 4530f8b8e08a5adc
The complete GlobalRules dataset in one call: all 82 countries x 53 verified topics (VAT/GST, government-verified 2026-2027 public holidays, tipping, plugs, visas, minimum wages, business etiquette and more) with source URLs and verification dates. For agents that cache, analyze or embed the full corpus. Cheaper than 15 single calls.
from a public catalogue that lists it, not from the operator
- endpoint
- https://globalrules-api.onrender.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 10 · newcomer
- Is globalrules live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is globalrules free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does globalrules have?
- 3 tools: get_country_overview, get_paid_api_info, list_countries.
- Is globalrules 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.
90 days 99%· all time 97.4%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- get vat rates for a country
- look up public holidays by country
- check tipping and visa rules
- list covered countries
- takes → gives
- text → text, data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 100 doors on this origin, so the chain figures are the operator's. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-04
no flags
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_paid_api_info reads open 5h ago
FREE. How to get structured JSON with sources: pay-per-call x402 API endpoints, prices, and 2-minute wallet setup.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 lineslist_countries reads open 5h ago
FREE. List all 195 countries covered by GlobalRules (58+ verified topics each: VAT, public holidays, tipping, visas, minimum wage...).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_country_overview reads unknown 5h ago
FREE. Human-readable Markdown overview for one country (same content as the public globalrules.org page). For structured JSON with source URLs, use the paid x402 API (see get_paid_api_info).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "code" ], "properties": { "code": { "type": "string", "maxLength": 2, "minLength": 2, "description": "ISO 3166-1 alpha-2 country code, e.g. JP, US, DE" } }, "additionalProperties": false }arguments 16 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id4530f8b8e08a5adc.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4530f8b8e08a5adc/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4530f8b8e08a5adc?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.