pulsewatch-status
https://pulsewatch-status-api.dario-9fa.workers.dev
Registry code: 07b7564201376bb2
PulseWatch Status API: Current outage status for a vendor (PulseWatch). Current status, active-incident summary, last-checked time and source URL for one vendor, read live from PulseWatch. Includes data_source, checked_at and freshness fields. Unknown vendors return 404 and are not charged.
from a public catalogue that lists it, not from the operator
- endpoint
- https://pulsewatch-status-api.dario-9fa.workers.dev/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
- 0 · newcomer
- Is pulsewatch-status live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is pulsewatch-status free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does pulsewatch-status have?
- 4 tools: validate_vendor, pricing, vendor_status, list_vendors.
- Is pulsewatch-status 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 4 tools
- unknown → live
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 also stands behind 8 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-10-10
counted from three payers (thin, concentrated, shared-payto)
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.
list_vendors open 1h ago
FREE. List/search the vendors PulseWatch tracks (slug, name, category). Use before paying to confirm a vendor is tracked.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "page": { "type": "integer", "maximum": 1000, "minimum": 1 }, "search": { "type": "string", "maxLength": 100 } } }arguments 15 linesvalidate_vendor unknown never probed
FREE. Check a vendor name/domain format before paying. Format only; use list_vendors to confirm it is tracked.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "vendor" ], "properties": { "vendor": { "type": "string", "maxLength": 200 } } }arguments 13 linespricing unknown never probed
FREE. Prices, network and payment address for the paid tools.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesvendor_status unknown 1h ago
Is this vendor down? Current status, confidence, active incidents, 30-day uptime and freshness for one SaaS/cloud vendor, read live from PulseWatch. Unknown vendors return an error and are not charged.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "vendor" ], "properties": { "vendor": { "type": "string", "maxLength": 200, "minLength": 1, "description": "Vendor name, slug or domain, e.g. 'Stripe', 'stripe' or stripe.com" } } }arguments 15 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 id07b7564201376bb2.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/07b7564201376bb2/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/07b7564201376bb2?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.