Skip to content

Perimeter Watch MCP server

io.github.entradox/perimeter-watch-scannerentradoxstreamable-httpv1.0.0Scanned

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

6 tools: 3 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 3 write, 3 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Perimeter Watch MCP server can do

The Perimeter Watch MCP server is published by the GitHub account entradox. It has 6 tools. It can create or change data (3 tools: pw_health, pw_snapshot and pw_stats), but cannot delete data. 3 tools only read.

1 tool reads private data (read_skill); 1 tool brings in text other people can write (read_skill); 1 tool can send data out of your system (read_skill). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 3Claude Code: ask
  • pw_healthLiveness check for the Perimeter Watch API.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Liveness check for the Perimeter Watch API. Returns ok, service, version. Call first to verify connectivity before pw_snapshot.

    Annotations the server declares

    • title: Perimeter Watch Health
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • pw_snapshotRun a free one-time external-perimeter scan on a domain you control.No findings

    Why it is in this group

    • The name "pw_snapshot" says "snapshot": a word for reading.
    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Run Perimeter Snapshot
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
  • pw_statsService funnel counters: page views, snapshots run, paid registrations.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Service funnel counters: page views, snapshots run, paid registrations. Read-only.

    Annotations the server declares

    • title: Perimeter Watch Stats
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
Only reads 3Show 3 read-only tools
  • pw_watch_statusCheck whether a domain is enrolled on a paid weekly monitoring plan.No findings

    Why it is in this group

    • The name "pw_watch_status" says "status": a word for reading.
    Description, as the server wrote it
    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)

    Annotations the server declares

    • title: Watch Plan Status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • read_skillRead a product skill file by its skill:// URI.Reads private dataReads text others writeCan send data outNo findings

    Why it is in this group

    • The name "read_skill" says "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "file": it reads files.
    • untrusted-inputThe description's first sentence says "read" and "uri": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.uri), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.uri): a request to a URL can carry data to whoever runs it.

    Claude Code: ask, because it is tagged outbound.

    Description, as the server wrote it
    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`.
  • skills_list_toolList this product's skills.No findings

    Why it is in this group

    • The name "skills_list_tool" says "list": a word for reading.
    Description, as the server wrote it
    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`.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__perimeter-watch-scanner__read_skill"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:04 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://perimeter-watch-api-production.up.railway.app/mcp/: tools/list returned 6 tools to an anonymous client, including pw_health (write), pw_snapshot (write), pw_stats (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http perimeter-watch-scanner https://perimeter-watch-api-production.up.railway.app/mcp/
claude mcp add --transport http perimeter-watch-scanner https://perimeter-watch-api-production.up.railway.app/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__perimeter-watch-scanner__pw_watch_status",
      "mcp__perimeter-watch-scanner__skills_list_tool"
    ],
    "ask": [
      "mcp__perimeter-watch-scanner__pw_health",
      "mcp__perimeter-watch-scanner__pw_snapshot",
      "mcp__perimeter-watch-scanner__pw_stats",
      "mcp__perimeter-watch-scanner__read_skill"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as perimeter-watch-scanner. Review it before you use it.

Capability tags behind 1 rule
  • mcp__perimeter-watch-scanner__read_skill private-data, untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.entradox/perimeter-watch-scanner/verify?hash=02bc2dffd40ffb0f04494ba582d978b210c0c3f2cdafa20aa1df142fb0d1ae31" | jq -e '.changed == false'

Pinned hash 02bc2dffd40f, from Nov 19, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.entradox/perimeter-watch-scanner/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.entradox/perimeter-watch-scanner
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.entradox/perimeter-watch-scanner.svg)](https://radar.anlyon.com/servers/io.github.entradox/perimeter-watch-scanner)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:33 UTC.

Perimeter Watch MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Perimeter Watch MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Perimeter Watch MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Perimeter Watch MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Perimeter Watch MCP server have?

6 tools: 3 write, 3 read. pw_health, pw_snapshot, pw_stats, pw_watch_status, skills_list_tool and read_skill.

Does the Perimeter Watch MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Perimeter Watch MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): read_skill.

Has the Perimeter Watch MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.