Perimeter Watch
REMOTE · PERIMETER-WATCH-API-PRODUCTION.UP.RAILWAY.APP
Passive domain-perimeter checks — cert expiry, subdomain takeover, lookalikes — as agent tools
Available components
Last scanned (8 hours ago)
Scores higher than 76% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Security
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 4 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 15 Sept 26 0
- Authorization: partial → unverified ▼ security
- 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” functional
- 8 Sept 26 0
- 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 security
- Schema quality: 41 → 73 ▼ functional
- Schema quality: good → excellent functional
- Server version: 1.29.1 → 1.30.0 functional
- 5 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Sept 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://perimeter-watch-api-production.up.railway.app/mcp/
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of perimeter-watch-api-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://perimeter-watch-api-production.up.railway.app/mcp/ | Unreachable | ||
| http (plaintext) | http://perimeter-watch-api-production.up.railway.app/mcp/ | HTTPS enforced |
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 →
pw_health ~34
Liveness check for the Perimeter Watch API. Returns ok, service, version. Call first to verify connectivity before pw_snapshot.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pw_snapshot ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| authority | boolean | yes | – |
| domain | string | yes | – |
No output schema declared.
No examples provided.
pw_stats ~24
Service funnel counters: page views, snapshots run, paid registrations. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pw_watch_status ~67
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)
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
No output schema declared.
No examples provided.
read_skill ~57
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| uri | string | yes | – |
No output schema declared.
No examples provided.
skills_list_tool ~51
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`.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · perimeter-watch-api-production.up.railway.app
claude mcp add --transport http entradox-perimeter-watch-scanner 'https://perimeter-watch-api-production.up.railway.app/mcp/'
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 78 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?
Its publisher declares no required credentials for Perimeter Watch. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Perimeter Watch MCP server still maintained?
Perimeter Watch is still listed in the MCP registry, though our most recent checks did not reach this channel. 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.