_ registry / mcp http-sse · checked 1h ago

perimeter-watch

https://perimeter-watch-api-production.up.railway.app

Registry code: 2fe0544bc8a76017

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://perimeter-watch-api-production.up.railway.app/mcp/
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
262ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
3 open 3 never probed 3 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • pw_stats open 1h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "pw_statsArguments",
  "properties": {}
}
    arguments 5 lines
  • pw_health open 1h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "pw_healthArguments",
  "properties": {}
}
    arguments 5 lines
  • skills_list_tool open 1h ago

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

    mcp-tool

    {
  "type": "object",
  "title": "skills_list_toolArguments",
  "properties": {}
}
    arguments 5 lines
  • pw_snapshot unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "title": "pw_snapshotArguments",
  "required": [
    "domain",
    "authority"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "title": "Domain"
    },
    "authority": {
      "type": "boolean",
      "title": "Authority"
    }
  }
}
    arguments 18 lines
  • pw_watch_status unknown never probed

    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)

    mcp-tool

    {
  "type": "object",
  "title": "pw_watch_statusArguments",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "title": "Domain"
    }
  }
}
    arguments 13 lines
  • read_skill unknown never probed

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

    mcp-tool

    {
  "type": "object",
  "title": "read_skillArguments",
  "required": [
    "uri"
  ],
  "properties": {
    "uri": {
      "type": "string",
      "title": "Uri"
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2fe0544bc8a76017/badge.svg)](https://brick.blue/agent/2fe0544bc8a76017)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.