Perimeter Watch
REMOTE · PERIMETER-WATCH-API-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 20
Passive domain-perimeter checks — cert expiry, subdomain takeover, lookalikes — as agent tools
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 472 tokens (~67/item across 7 items; 6 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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/'
{
"mcpServers": {
"entradox-perimeter-watch-scanner": {
"url": "https://perimeter-watch-api-production.up.railway.app/mcp/"
}
}
} {
"servers": {
"entradox-perimeter-watch-scanner": {
"type": "http",
"url": "https://perimeter-watch-api-production.up.railway.app/mcp/"
}
}
} [mcp_servers.entradox-perimeter-watch-scanner] url = "https://perimeter-watch-api-production.up.railway.app/mcp/"
{
"$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 mcp add entradox-perimeter-watch-scanner --url 'https://perimeter-watch-api-production.up.railway.app/mcp/' --transport streamable-http
mcp_servers:
entradox-perimeter-watch-scanner:
url: "https://perimeter-watch-api-production.up.railway.app/mcp/" {
"McpServers": {
"entradox-perimeter-watch-scanner": {
"Transport": "http",
"Url": "https://perimeter-watch-api-production.up.railway.app/mcp/"
}
}
} assistant mcp add entradox-perimeter-watch-scanner -t streamable-http -u 'https://perimeter-watch-api-production.up.railway.app/mcp/'
{
"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.
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.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 −5
- 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
- 14 Sept 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.
- 12 Sept 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.
- 9 Sept 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.
- 8 Sept 26 +9
- 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
- 6 Sept 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.
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 20 Sept 2026 · Probed https://perimeter-watch-api-production.up.railway.app/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
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 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 |
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/ | Verified | 200 | |
| http (plaintext) | http://perimeter-watch-api-production.up.railway.app/mcp/ | HTTPS enforced | 301 | https://perimeter-watch-api-production.up.railway.app/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 →
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.
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 71 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.