# RoundWatch (remote · roundwatch-api.onrender.com)

Durable Algorand USDC payment monitoring for autonomous workflows.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `roundwatch-api.onrender.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/vladyslav-webdev-roundwatch/roundwatch-api.md), [page](https://verifymcp.io/servers/vladyslav-webdev-roundwatch/roundwatch-api)

## Channel facts

- Endpoint: `https://roundwatch-api.onrender.com/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-26.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 82/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 516 tokens (~129/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the RoundWatch MCP server?

RoundWatch is a hosted endpoint at https://roundwatch-api.onrender.com/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 vladyslav-webdev-roundwatch 'https://roundwatch-api.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "vladyslav-webdev-roundwatch": {
      "url": "https://roundwatch-api.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vladyslav-webdev-roundwatch": {
      "type": "http",
      "url": "https://roundwatch-api.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.vladyslav-webdev-roundwatch]
url = "https://roundwatch-api.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vladyslav-webdev-roundwatch": {
      "type": "remote",
      "url": "https://roundwatch-api.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vladyslav-webdev-roundwatch --url 'https://roundwatch-api.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vladyslav-webdev-roundwatch:
    url: "https://roundwatch-api.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "vladyslav-webdev-roundwatch": {
      "Transport": "http",
      "Url": "https://roundwatch-api.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vladyslav-webdev-roundwatch -t streamable-http -u 'https://roundwatch-api.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "vladyslav-webdev-roundwatch": {
      "type": "http",
      "url": "https://roundwatch-api.onrender.com/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-26 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional] New tool “roundwatch.prepare_recovery”

### 2026-09-25 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-22 (score 72)

First indexed and scored.

## MCP tools (4)

### `roundwatch.service_info` (~39 tokens)

RoundWatch Service Info

Return the live RoundWatch network, x402 service contract, USDC asset, price, limits, and documentation links. Read-only and free.

### `roundwatch.prepare_watch` (~168 tokens)

Prepare RoundWatch Watch

Validate one expected future Algorand USDC payment and return the exact RoundWatch HTTP/x402 request to create a durable watch. This tool does not settle the x402 payment and does not create the watch by itself.

Input parameters:

- `atomicAmount` (string, required): Exact watched USDC amount in atomic units. Algorand USDC uses 6 decimals.
- `expectedReceiver` (string, required): Checksum-valid Algorand address expected to receive the future payment.
- `expectedSender` (string, required): Checksum-valid Algorand address expected to send the future payment.
- `idempotencyKey` (string, required): Stable key that identifies this watch request and prevents duplicates.
- `invoiceNote` (string): Optional exact UTF-8 Algorand transaction note, maximum 128 UTF-8 bytes.

### `roundwatch.prepare_recovery` (~187 tokens)

Prepare RoundWatch Recovery

Validate and return the exact free HTTP request used to recover an existing watch after a paid create may have succeeded but the caller lost the returned watchId. Confirmed-settlement watches remain recoverable even after terminal expiry or post-activation indeterminate completion. This tool never signs, pays, or retries the paid create.

Input parameters:

- `atomicAmount` (string, required): The exact original watched USDC amount in atomic units.
- `expectedReceiver` (string, required): The exact original expected future-payment receiver.
- `expectedSender` (string, required): The exact original expected future-payment sender.
- `idempotencyKey` (string, required): The exact original idempotency key from the paid create attempt.
- `invoiceNote` (string): The exact original optional invoice note, if one was supplied.
- `servicePayer` (string, required): Public Algorand address that signed the original x402 RoundWatch service payment.

### `roundwatch.get_watch` (~48 tokens)

Get RoundWatch Watch

Read the durable state and any verified on-chain evidence for an existing RoundWatch watch ID. Read-only and free.

Input parameters:

- `watchId` (string, required): Durable watch ID returned after successful activation.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vladyslav-webdev-roundwatch/roundwatch-api#diagnostics

## Score history

- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 72

## Common questions

### What is the RoundWatch MCP server?

RoundWatch is an MCP server listed in the public MCP registry as io.github.Vladyslav-webDev/roundwatch. Durable Algorand USDC payment monitoring for autonomous workflows. This page covers its hosted endpoint (https://roundwatch-api.onrender.com/mcp).

### Is the RoundWatch MCP server safe to use?

RoundWatch scores 74 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 RoundWatch MCP server expose?

RoundWatch exposes 4 tools: roundwatch.service_info, roundwatch.prepare_watch, roundwatch.prepare_recovery, roundwatch.get_watch. Their descriptions and schemas cost roughly 442 tokens of context every time the server is loaded.

### Does the RoundWatch MCP server require authentication?

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

### Is the RoundWatch MCP server still maintained?

RoundWatch is still listed as active in the MCP registry. We last reached this channel on 26 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://roundwatch-api.onrender.com/mcp
- Repository: https://github.com/Vladyslav-webDev/RoundWatch
- Website: https://roundwatch.observer/
- Changelog RSS feed: https://verifymcp.io/servers/vladyslav-webdev-roundwatch/roundwatch-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/vladyslav-webdev-roundwatch/roundwatch-api.json
- HTML version of this page: https://verifymcp.io/servers/vladyslav-webdev-roundwatch/roundwatch-api