_ registry / mcp http-sse · checked 20m ago

pulsewatch-status

https://api.pulsewatch.us

Registry code: 4f27481f678b3c5b

api record

Vendor outage status from PulseWatch. Use list_vendors, validate_vendor and pricing (all free) first, then vendor_status for one vendor. All tools are read-only. Payment is x402 USDC on Base in _meta["x402/payment"]; no API key; untracked vendors, invalid input and upstream failures are not charged.

endpoint
https://api.pulsewatch.us/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 it live, free and safe measured by this hub
Is pulsewatch-status live?
Yes — it answered the hub's last check (checked 20m 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, vendor_status, pricing, 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
367ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
_ usage and payments 30 days

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 14 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
22

distinct

settlements
239

last 2026-11-03

received on chain
44.655 USDC

concentrated, shared-payto

_ what it can do 4 tools
1 open 3 never probed 1 of 4 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.

  • list_vendors open 19m ago

    Free. List or search the vendors PulseWatch tracks (slug, name, category), paged. Use it before paying to confirm a vendor is tracked and to get its exact slug. Read-only; one request to PulseWatch, no payment.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "page": {
          "type": "integer",
          "maximum": 1000,
          "minimum": 1,
          "description": "Page number, starting at 1 (default 1)"
        },
        "search": {
          "type": "string",
          "maxLength": 100,
          "description": "Optional name or slug filter, e.g. 'stripe' or 'aws'"
        }
      }
    }
    arguments 17 lines
  • validate_vendor unknown 19m ago

    Free. Check that a vendor name, slug or domain is well-formed and see how it will be matched. Format only and offline (no network request, no payment); use list_vendors to confirm the vendor is actually tracked.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "vendor"
      ],
      "properties": {
        "vendor": {
          "type": "string",
          "maxLength": 200,
          "description": "Vendor name, slug or domain, e.g. 'Stripe', 'stripe' or stripe.com"
        }
      }
    }
    arguments 14 lines
  • vendor_status unknown 19m ago

    Check whether one SaaS or cloud vendor (e.g. Stripe) is down right now: current status, confidence, active incidents, 30-day uptime and how fresh the data is, read live from PulseWatch. Use it for one vendor. Call list_vendors (free) first if you are not sure the vendor is tracked: unknown vendors return an error and are not charged. Read-only. Costs $0.01 USDC per call via x402 (payment goes in _meta["x402/payment"]); invalid input or an upstream failure is not charged.

    mcp-tool

    {
      "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
  • pricing unknown never probed

    Free. Return the price of every paid tool, the payment network (Base), the receiving address and the data source. No input, no network request, no payment.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 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 4f27481f678b3c5b.

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

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.