# Perimeter Watch (remote · perimeter-watch-api-production.up.railway.app)

Passive domain-perimeter checks — cert expiry, subdomain takeover, lookalikes — as agent tools

- Trust score: 72/100 (medium)
- Change this week: −2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `perimeter-watch-api-production.up.railway.app`: 72/100 (this document), [markdown](https://verifymcp.io/servers/entradox-perimeter-watch-scanner/perimeter-watch-api-production.md), [page](https://verifymcp.io/servers/entradox-perimeter-watch-scanner/perimeter-watch-api-production)

## Channel facts

- Endpoint: `https://perimeter-watch-api-production.up.railway.app/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-09-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 472 tokens (~67/item across 7 items; 6 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Perimeter Watch MCP server?

Perimeter Watch is a hosted endpoint at https://perimeter-watch-api-production.up.railway.app/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 entradox-perimeter-watch-scanner 'https://perimeter-watch-api-production.up.railway.app/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "entradox-perimeter-watch-scanner": {
      "url": "https://perimeter-watch-api-production.up.railway.app/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "entradox-perimeter-watch-scanner": {
      "type": "http",
      "url": "https://perimeter-watch-api-production.up.railway.app/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.entradox-perimeter-watch-scanner]
url = "https://perimeter-watch-api-production.up.railway.app/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "entradox-perimeter-watch-scanner": {
      "type": "remote",
      "url": "https://perimeter-watch-api-production.up.railway.app/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add entradox-perimeter-watch-scanner --url 'https://perimeter-watch-api-production.up.railway.app/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  entradox-perimeter-watch-scanner:
    url: "https://perimeter-watch-api-production.up.railway.app/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "entradox-perimeter-watch-scanner": {
      "Transport": "http",
      "Url": "https://perimeter-watch-api-production.up.railway.app/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add entradox-perimeter-watch-scanner -t streamable-http -u 'https://perimeter-watch-api-production.up.railway.app/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "entradox-perimeter-watch-scanner": {
      "type": "http",
      "url": "https://perimeter-watch-api-production.up.railway.app/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-09-21 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 69, −5)

- [security regression] Authorization: partial → unverified
- [functional regression] Schema quality: 294 → 472
- [functional] First check of Schema quality: 100
- [functional] New resource “perimeter-watch”
- [functional] New tool “read_skill”
- [functional] New tool “skills_list_tool”

### 2026-09-14 (score 74, +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-09-12 (score 73, +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-09-09 (score 72, +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-09-08 (score 71, +9)

- [security improvement] Authorization: unverified → partial
- [security] Tool “pw_health” rewrote its description, which is the text the model reads
- [security] Tool “pw_snapshot” rewrote its description, which is the text the model reads
- [security] Tool “pw_stats” rewrote its description, which is the text the model reads
- [security] Tool “pw_watch_status” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 41 → 73
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.29.1 → 1.30.0

## MCP tools (6)

### `pw_health` (~34 tokens)

Liveness check for the Perimeter Watch API. Returns ok, service, version. Call first to verify connectivity before pw_snapshot.

### `pw_snapshot` (~169 tokens)

Run a free one-time external-perimeter scan on a domain you control.

Checks TLS certificate expiry, domain renewal status, dangling CNAME
takeover risk, and CT-log lookalike domains. Returns a rating plus
per-check detail. NOT idempotent (each call consumes rate limit);
takes 20-60s; rate-limited to 3 scans per IP per 24h.

Args:
    domain: the domain to scan (e.g. example.com)
    authority: MUST be true — attests you or your principal own/manage
        this domain. Scanning third-party domains without authority is
        prohibited. Scan takes 20-60s. Rate limit: 3/IP/24h.

Input parameters:

- `authority` (boolean, required)
- `domain` (string, required)

### `pw_watch_status` (~67 tokens)

Check whether a domain is enrolled on a paid weekly monitoring plan.

Returns enrollment status. Paid plans add weekly re-scans with email
briefs. Read-only lookup.

Args:
    domain: the domain to look up (e.g. example.com)

Input parameters:

- `domain` (string, required)

### `pw_stats` (~24 tokens)

Service funnel counters: page views, snapshots run, paid registrations. Read-only.

### `skills_list_tool` (~51 tokens)

List this product's skills. Each entry carries the SKILL.md URI,
its name and description, verbatim frontmatter, and a per-file
sha256 manifest. Read a body with `read_skill`.

### `read_skill` (~57 tokens)

Read a product skill file by its skill:// URI.

Args:
    uri: e.g. skill://<product>/<skill-name>/SKILL.md
         Get valid URIs from `skills_list_tool`.

Input parameters:

- `uri` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/entradox-perimeter-watch-scanner/perimeter-watch-api-production#diagnostics

## Score history

- 2026-09-21: 72
- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 72
- 2026-09-08: 71
- 2026-09-07: 62
- 2026-09-06: 62
- 2026-09-05: 61
- 2026-09-04: 61

## Common questions

### What is the Perimeter Watch MCP server?

Perimeter Watch is an MCP server listed in the public MCP registry as io.github.entradox/perimeter-watch-scanner. Passive domain-perimeter checks, cert expiry, subdomain takeover, lookalikes, as agent tools. This page covers its hosted endpoint (https://perimeter-watch-api-production.up.railway.app/mcp/).

### Is the Perimeter Watch MCP server safe to use?

Perimeter Watch scores 72 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 Perimeter Watch MCP server expose?

Perimeter Watch exposes 6 tools: pw_health, pw_snapshot, pw_watch_status, pw_stats, skills_list_tool, read_skill. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.

### Does the Perimeter Watch MCP server require authentication?

No. We connected to Perimeter Watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Perimeter Watch MCP server still maintained?

Perimeter Watch is still listed as active in the MCP registry. We last reached this channel on 21 September 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://perimeter-watch-api-production.up.railway.app/mcp/
- Repository: https://github.com/entradox/perimeter-watch-scanner
- Website: https://entradox.github.io/perimeter-watch-site/
- Changelog RSS feed: https://verifymcp.io/servers/entradox-perimeter-watch-scanner/perimeter-watch-api-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/entradox-perimeter-watch-scanner/perimeter-watch-api-production.json
- HTML version of this page: https://verifymcp.io/servers/entradox-perimeter-watch-scanner/perimeter-watch-api-production