RoundWatch
REMOTE · ROUNDWATCH-API.ONRENDER.COM
Durable Algorand USDC payment monitoring for autonomous workflows.
Available components
Last scanned (11 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 531 tokens (~132/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 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
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 29 Sept 26 0
- “roundwatch.prepare_watch” reworded the description of “expectedSender” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 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
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 21 Nov 2026 · Probed https://roundwatch-api.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 19 Nov 2026 | 17 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 8d72a13c2c41648513b9d014eb5e0339 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of roundwatch-api.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| onrender.com. | No DS | 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://roundwatch-api.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://roundwatch-api.onrender.com/mcp | HTTPS enforced | 301 | https://roundwatch-api.onrender.com/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 →
roundwatch.get_watch Get RoundWatch Watch ~48
Read the durable state and any verified on-chain evidence for an existing RoundWatch watch ID. Read-only and free.
| Name | Type | Req | Description |
|---|---|---|---|
| watchId | string | yes | Durable watch ID returned after successful activation. |
No output schema declared.
No examples provided.
roundwatch.prepare_recovery Prepare RoundWatch Recovery ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| atomicAmount | string | yes | The exact original watched USDC amount in atomic units. |
| expectedReceiver | string | yes | The exact original expected future-payment receiver. |
| expectedSender | string | yes | The exact original expected future-payment sender. |
| idempotencyKey | string | yes | The exact original idempotency key from the paid create attempt. |
| invoiceNote | string | – | The exact original optional invoice note, if one was supplied. |
| servicePayer | string | yes | Public Algorand address that signed the original x402 RoundWatch service payment. |
No output schema declared.
No examples provided.
roundwatch.prepare_watch Prepare RoundWatch Watch ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| atomicAmount | string | yes | Exact watched USDC amount in atomic units. Algorand USDC uses 6 decimals. |
| expectedReceiver | string | yes | Checksum-valid Algorand address expected to receive the future payment. |
| expectedSender | string | yes | Checksum-valid nonzero Algorand address expected to send the future payment. The Algorand zero address is rejected for new watch creation. |
| idempotencyKey | string | yes | Stable key that identifies this watch request and prevents duplicates. |
| invoiceNote | string | – | Optional exact UTF-8 Algorand transaction note, maximum 128 UTF-8 bytes. |
No output schema declared.
No examples provided.
roundwatch.service_info RoundWatch Service Info ~39
Return the live RoundWatch network, x402 service contract, USDC asset, price, limits, and documentation links. Read-only and free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · roundwatch-api.onrender.com
claude mcp add --transport http vladyslav-webdev-roundwatch 'https://roundwatch-api.onrender.com/mcp'
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 86 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 457 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the RoundWatch MCP server?
VerifyMCP ran 13 checks on RoundWatch, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.