# whoisbrowsing (remote · whoisbrowsing.com)

Add live visitor cursors to any website, no signup: create a site, get the snippet, check it's live.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `whoisbrowsing.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-whoisbrowsing-mcp/whoisbrowsing.md), [page](https://verifymcp.io/servers/com-whoisbrowsing-mcp/whoisbrowsing)

## Channel facts

- Endpoint: `https://whoisbrowsing.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (67% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-whoisbrowsing-mcp 'https://whoisbrowsing.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-whoisbrowsing-mcp": {
      "url": "https://whoisbrowsing.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-whoisbrowsing-mcp": {
      "type": "http",
      "url": "https://whoisbrowsing.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-whoisbrowsing-mcp]
url = "https://whoisbrowsing.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-whoisbrowsing-mcp": {
      "type": "remote",
      "url": "https://whoisbrowsing.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-whoisbrowsing-mcp --url 'https://whoisbrowsing.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-whoisbrowsing-mcp:
    url: "https://whoisbrowsing.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-whoisbrowsing-mcp": {
      "Transport": "http",
      "Url": "https://whoisbrowsing.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-whoisbrowsing-mcp -t streamable-http -u 'https://whoisbrowsing.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-whoisbrowsing-mcp": {
      "type": "http",
      "url": "https://whoisbrowsing.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 79, +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.

### 2026-11-02 (score 78, +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.

### 2026-10-31 (score 77, +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.

### 2026-10-29 (score 76, +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.

### 2026-10-27 (score 75, 0)

- [security] 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
- [cosmetic] “create_site” reworded the description of “domains”

### 2026-10-26 (score 75, +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.

### 2026-10-23 (score 74, +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.

### 2026-10-22 (score 73, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `create_site` (~189 tokens)

Create a whoisbrowsing site

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.

Input parameters:

- `domains` (array, required): 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.

Output parameters:

- `claimUrl` (string): 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): Where the tag goes for each platform.
- `next` (array): What to do next, in order, in plain words.
- `siteId` (string): The site ID: the data-site value in the snippet. Public, fine to commit.
- `snippet` (string): The script tag to put on every page, unchanged.
- `terms` (string): 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): 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…

### `get_install_instructions` (~122 tokens)

Where the tag goes on a platform

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.

Input parameters:

- `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.

### `check_live` (~147 tokens)

Is the script connected right now?

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.

Input parameters:

- `key` (string, required): The owner key: the part after #wib= in the watch link create_site returned. Never write it into a file.
- `siteId` (string, required): The siteId create_site returned (12 lowercase letters and digits).

Output parameters:

- `connected` (boolean)
- `siteId` (string)
- `visitors` (integer)
- `watching` (array)
- `webs` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-whoisbrowsing-mcp/whoisbrowsing#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73

## Common questions

### 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://whoisbrowsing.com/mcp
- Website: https://whoisbrowsing.com/for-agents
- Changelog RSS feed: https://verifymcp.io/servers/com-whoisbrowsing-mcp/whoisbrowsing.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-whoisbrowsing-mcp/whoisbrowsing.json
- HTML version of this page: https://verifymcp.io/servers/com-whoisbrowsing-mcp/whoisbrowsing