steadysite
Registry code: b27721cf8ca39978
SteadySite (steadysite.dev) monitors website uptime, SSL certificate expiry and domain expiry for freelancers and agencies, with a branded monthly report per client. Use check_ssl_domain_expiry for one-off lookups, get_plans for pricing, and start_monitoring to give the person a sign-up link for ongoing alerts.
- endpoint
- https://steadysite.dev/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 steadysite live?
- Yes — it answered the hub's last check (checked 12h ago). It answered 100% of checks over the last 30 days.
- Is steadysite free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does steadysite have?
- 3 tools: check_ssl_domain_expiry, start_monitoring, get_plans.
- Is steadysite 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 3 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
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_plans open 12h ago
Return SteadySite plans (Free, Pro, Agency): monthly price in USD, monitors, check interval, client groups with their own branded reports and status pages, white-label, and whether paid checkout is open. Use when someone asks what SteadySite costs or which plan fits.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linescheck_ssl_domain_expiry unknown 12h ago
Look up a website's SSL certificate expiry (date, days left, issuer), domain registration expiry (date, days left, registrar) and current HTTP status. Use when someone asks when a site's certificate or domain expires, who issued it, or whether the site is up. "warn" means expiring within 30 days, "bad" means expired or down. Results are cached for 15 minutes; fresh lookups are limited to 15 per 10 minutes.
{ "type": "object", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 300, "description": "Hostname or URL, e.g. example.com or https://www.example.com/page" } }, "additionalProperties": false }arguments 14 linesstart_monitoring unknown 12h ago
Return a sign-up link that starts SteadySite monitoring (uptime, SSL expiry and domain expiry email alerts, monthly client report) for a domain. The person opens the link, signs in with their email (free plan, no credit card) and the domain is pre-filled. Nothing is created until they confirm.
{ "type": "object", "required": [ "domain" ], "properties": { "domain": { "type": "string", "maxLength": 300, "description": "Hostname or URL, e.g. example.com or https://www.example.com/page" } }, "additionalProperties": false }arguments 14 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 idb27721cf8ca39978.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b27721cf8ca39978/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b27721cf8ca39978?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.