whoisbrowsing
REMOTE · WHOISBROWSING.COM
Add live visitor cursors to any website, no signup: create a site, get the snippet, check it's live.
Available components
Last scanned (1 day ago)
Scores higher than 79% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Browser Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 657 tokens (~219/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “check_live” rewrote its description, which is the text the model reads security
- Tool “create_site” rewrote its description, which is the text the model reads security
- “create_site” reworded the description of “domains” cosmetic
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://whoisbrowsing.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=whoisbrowsing.com | CN=YR2,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | RSA 2048 | SHA256-RSA | 5f10236d86676ebedd739e32b7ff22aada4 |
| SANs: whoisbrowsing.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of whoisbrowsing.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| whoisbrowsing.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://whoisbrowsing.com/mcp | Verified | 200 | |
| http (plaintext) | http://whoisbrowsing.com/mcp | HTTPS enforced | 308 | https://whoisbrowsing.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_live Is the script connected right now? ~147
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 before calling it: a tab other than the owner view (it shows up as "you, testing"), or a fresh browser context.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The owner key: the part after #wib= in the watch link create_site returned. Never write it into a file. |
| siteId | string | yes | The siteId create_site returned (12 lowercase letters and digits). |
| Name | Type | Req | Description |
|---|---|---|---|
| connected | boolean | yes | – |
| siteId | string | yes | – |
| visitors | integer | yes | – |
| watching | array | yes | – |
| webs | array | yes | – |
No examples provided.
create_site Create a whoisbrowsing site ~189
Creates a whoisbrowsing site with no sign-up and returns its script tag (snippet), one watch link per website, a one-time claim link, a terms sentence for the human 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.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | The websites the tag will run on: host[:port] (e.g. localhost:3000, example.com), or *.host for every subdomain (e.g. *.example.com). A scheme or path is stripped; a host is letters, digits, hyphens… |
| name | string | – | A label for the site. Defaults to the first domain. |
| Name | Type | Req | Description |
|---|---|---|---|
| claimUrl | string | yes | The one-time link that keeps the site in the human's account after signing in with Google. Expires after 30 days. Give it to the human right away; never write it into a file, commit or log. |
| installDocs | string | yes | Where the tag goes for each platform. |
| next | array | yes | What to do next, in order, in plain words. |
| siteId | string | yes | The site ID: the data-site value in the snippet. Public, fine to commit. |
| snippet | string | yes | The script tag to put on every page, unchanged. |
| terms | string | yes | A sentence for the human, in the same reply as the two links: opening the watch link or keeping the script is agreeing to the Terms, and confirming they've read the Privacy page. |
| watchUrls | object | yes | One watch link per website: the human's own site, opened with a private owner key in the #fragment. Give it to the human right away; never write it into a file, commit or log. Treat it like a passwor… |
No examples provided.
get_install_instructions Where the tag goes on a platform ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | 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. |
No output schema declared.
No examples provided.
How do I install the whoisbrowsing MCP server?
whoisbrowsing is a hosted endpoint at https://whoisbrowsing.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · whoisbrowsing.com
claude mcp add --transport http com-whoisbrowsing-mcp 'https://whoisbrowsing.com/mcp'
What is the whoisbrowsing MCP server?
whoisbrowsing is an MCP server listed in the public MCP registry as com.whoisbrowsing/mcp. Add live visitor cursors to any website, no signup: create a site, get the snippet, check it's live. This page covers its hosted endpoint (https://whoisbrowsing.com/mcp).
Is the whoisbrowsing MCP server safe to use?
whoisbrowsing scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the whoisbrowsing MCP server expose?
whoisbrowsing exposes 3 tools: create_site, get_install_instructions, check_live. Their descriptions and schemas cost roughly 458 tokens of context every time the server is loaded.
Does the whoisbrowsing MCP server require authentication?
No. We connected to whoisbrowsing without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the whoisbrowsing MCP server still maintained?
whoisbrowsing is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.