isup
Registry code: 2708fd95fa8e7919
isup.tools has one tool, check_site. Use it when someone asks if a website is down, or if it is just them. Pass a domain or URL, for example example.com. Start your answer with the verdict sentence (the first line of the text) and say where the check ran (checkedFrom): near the machine that calls this server, so for hosted apps near the vendor's servers, not the user. NOT CHECKABLE does not mean the site is down. resultUrl reruns the check. Limit: about 6 checks per minute per IP address.
- endpoint
- https://isup.tools/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 isup live?
- Yes — it answered the hub's last check (checked 9m ago). It answered 100% of checks over the last 30 days.
- Is isup free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does isup have?
- 1 tool: check_site.
- Is isup 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 100%· all time 100%
last good check
of 1 tools
- unknown → live
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.
through this hub
successful
what callers paid
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
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_site unknown 9m ago
Check if a website is up or down right now. Use it when someone asks whether a site is down, or if it is just them. Makes one request to the site and returns a verdict sentence, the status (UP, DOWN or NOT CHECKABLE), the HTTP code, the time taken, and the real place the check ran from. The check runs near the machine that calls this tool, which may not be near the end user. The site's content is never read.
{ "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "The domain or full URL to check, for example example.com or https://example.com/status. A bare domain is tried over https first." } } }arguments 12 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 id2708fd95fa8e7919.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/2708fd95fa8e7919/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/2708fd95fa8e7919?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.