RoundWatch MCP server
Durable Algorand USDC payment monitoring for autonomous workflows.
0 stars
Reviews
Write oneNobody has reviewed RoundWatch yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
RoundWatch tools (3)
write = sends, deletes, buys or postsroundwatch.get_watchFreeRead the durable state and any verified on-chain evidence for an existing RoundWatch watch ID. Read-only and free.
roundwatch.prepare_watchFreeValidate 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.
roundwatch.service_infoFreeReturn the live RoundWatch network, x402 service contract, USDC asset, price, limits, and documentation links. Read-only and free.
Public scan report
scanner v0.1.9 · 2026-09-22 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 844ms20/20
- Tool poisoning3 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
What the publisher says
From the RoundWatch repository's README, as published. We do not edit it. Read it on GitHub
RoundWatch
Durable Algorand USDC payment monitoring for autonomous x402 workflows.
Website · Quickstart · Technical guide · Live API · OpenAPI · llms.txt · MCP Registry · Architecture
RoundWatch watches one exact future Algorand MainNet USDC payment when no transaction ID exists yet. A caller defines the expected payment, pays a one-time x402 service fee, receives a durable watch ID, and can exit. RoundWatch persists the obligation and scan progress, then exposes verified on-chain evidence for later retrieval.
Production: Algorand MainNet · Circle USDC · x402 v2 · GoPlausible facilitator · Bazaar cataloged · remote MCP endpoint · durable restart recovery.
What it solves
A short-lived agent, job, or service may need to know whether a particular payment arrives after the caller has stopped running. Keeping that caller alive to poll an Algorand Indexer is unnecessary if a durable observer can own the wait instead.
RoundWatch lets a caller define the expected payment, purchase one watch through x402, and exit. The service persists the obligation, continues scanning Algorand, and records the matching transaction for later retrieval.
A backend that already operates durable Indexer or subscriber infrastructure may reasonably implement this itself. RoundWatch is for callers that do not want to own that operational component.
Lifecycle
- The client submits the exact expected sender, receiver, atomic amount, and optional invoice note.
- x402 returns payment requirements and the client signs the service payment locally.
- GoPlausible verifies and settles the service payment.
- RoundWatch activates the persisted watch only after the exact service-payment transaction is confirmed; that transaction's confirmed round becomes the scan baseline.
- The caller may exit while RoundWatch polls the Algorand Indexer.
- The watch becomes matched when an exact future USDC asset transfer appears.
- The caller reads the durable result with GET /v1/watch/:id.
See Architecture for the normal, recovery, and matching paths.
See Roadmap for the current product direction and prioritization.
Live production service
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Install directly
claude mcp add --transport http roundwatch https://roundwatch-api.onrender.com/mcp
RoundWatch: common questions
- Is RoundWatch MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the RoundWatch safety report
- How do I install RoundWatch?
- It runs remotely at roundwatch-api.onrender.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does RoundWatch need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is RoundWatch maintained?
- The last commit was in the last day (2026-09-22). The latest release is v1.0.0.
- Is RoundWatch up?
- 100% of our last 1 checks got an answer. We check remote servers about four times a day.
- What can I use instead of RoundWatch?
- Servers from other publishers that do the same job: three.ws Agent Payments MCP server, X402 List MCP server and Agent402.Tools: pay-per-call web tools MCP server. Compare all RoundWatch alternatives.
Alternatives to RoundWatch
Same job from other publishers: the closest match first, then the best rated.
- three.ws Agent PaymentsGoverned x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key.not reviewedEstablishedB
- X402 ListFind and vet x402 payment APIs before your agent pays one: uptime, price, on-chain volume.not reviewedEstablishedA
- Agent402.Tools: pay-per-call web toolsAgentic Finance: 500+ agent tools, multi-chain USDC over x402 or MPP, free via PoW or card creditsnot reviewedEstablishedA
- FiatDockMCP marketplace: AI agents buy services from other agents per call in USDC, plus a bank cash-outnot reviewedGrowingB
- PipRailBudget-bound x402 payment wallet for AI agents — pays HTTP 402 URLs, capped locally. No backend.not reviewedGrowingB