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

whoisbrowsing

https://whoisbrowsing.com

Registry code: 9bc26f210b53b66b

api record

whoisbrowsing shows who is on a website right now: every current visitor's cursor drawn live on the owner's real page. To add it to a project: 1) create_site with the dev server's host and port (and the production domain if there is one); 2) put the returned snippet on every page, in the file all pages share (get_install_instructions says where for each platform); 3) give the human the watch link and the claim link right away, and never write either into a file, commit or log; 4) after a page with the tag is open, check_live with the siteId and the owner key (the part after #wib= in the watch…

endpoint
https://whoisbrowsing.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
0 · newcomer
_ is it live, free and safe measured by this hub
Is whoisbrowsing live?
Yes — it answered the hub's last check (checked 40m ago). It answered 100% of checks over the last 30 days.
Is whoisbrowsing free to use?
Yes — the hub reached it with no key and no payment.
What tools does whoisbrowsing have?
3 tools: create_site, check_live, get_install_instructions.
Is whoisbrowsing 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
293ms

last good check

priced tools
0

of 3 tools

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

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

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

  • get_install_instructions open 40m ago

    Returns the install guide (Markdown) for one platform: where the script tag goes, a Content-Security-Policy note and how to verify. Call it without a platform, or with an unknown one, to get the list of platforms.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "platform": {
          "type": "string",
          "maxLength": 40,
          "description": "The platform's slug: react, angular, astro, framer, ghost, nextjs, nuxt, html, remix, squarespace, svelte, vue, webflow, wix, ai-agent, wordpress, shopify. Common names such as \"Next.js\" work too."
        }
      }
    }
    arguments 11 lines
  • create_site unknown never probed

    Creates a whoisbrowsing site with no sign-up and returns its script tag (snippet), one watch link per website, a one-time claim link and the next steps. Call it once per project; one site can hold several domains. Never write the watch or claim link into a file, commit or log.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "domains"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 100,
          "description": "A label for the site. Defaults to the first domain."
        },
        "domains": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 253
          },
          "maxItems": 20,
          "minItems": 1,
          "description": "The websites the tag will run on: host[:port] (e.g. localhost:3000, example.com), or *.host for every subdomain (e.g. *.vercel.app). A scheme or path is stripped; a host is letters, digits, hyphens and dots (a non-ASCII domain in its xn-- form); www. is the same website as the bare domain; each website is watched separately."
        }
      }
    }
    arguments 24 lines
  • check_live unknown 40m ago

    Asks the live server whether the site's script is connected right now: the websites with a visitor, how many visitors, and which websites the owner is watching. Needs the site's owner key, the part after #wib= in the watch link create_site returned. Load a page that has the tag (a private window counts as a visitor) before calling it.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "siteId",
        "key"
      ],
      "properties": {
        "key": {
          "type": "string",
          "maxLength": 4096,
          "description": "The owner key: the part after #wib= in the watch link create_site returned. Never write it into a file."
        },
        "siteId": {
          "type": "string",
          "maxLength": 64,
          "description": "The siteId create_site returned (12 lowercase letters and digits)."
        }
      }
    }
    arguments 20 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 9bc26f210b53b66b.

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

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.