Koskamo

RoundWatch MCP

RoundWatch is a durable payment-monitoring API for one exact future Algorand USDC payment when no transaction ID exists yet. The MCP server exposes read-only discovery and status tools plus preparation tools for the paid create request and the free exact recovery request.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

RoundWatch MCP logo, by Vladyslav-webDevCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by Vladyslav-webDev
MCP endpoint (Streamable HTTP)
https://roundwatch-api.onrender.com/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

4 of 4 have a description · 4 of 4 declare behavior hints · 3 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Detect one exact future Algorand USDC transfer
  • Retrieve verified on-chain evidence for a watched payment
  • Recover lost watch ID after a paid response is lost

Source and maintenance

Community listingRegistry 1.0.0
Maintenance checked

Protocol and capabilities

Server
roundwatch 1.0.0
MCP protocol negotiated in check
2025-11-25
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

RoundWatch monitors one exact future Algorand USDC payment when no transaction ID exists yet.

Tools

4 advertised

roundwatch.service_info — RoundWatch Service Info
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

roundwatch.service_info input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
roundwatch.service_info annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
roundwatch.prepare_watch — Prepare RoundWatch Watch
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

roundwatch.prepare_watch input schema
{
  "type": "object",
  "required": [
    "idempotencyKey",
    "expectedSender",
    "expectedReceiver",
    "atomicAmount"
  ],
  "properties": {
    "invoiceNote": {
      "type": "string",
      "maxLength": 128,
      "minLength": 1,
      "description": "Optional exact UTF-8 Algorand transaction note, maximum 128 UTF-8 bytes."
    },
    "atomicAmount": {
      "type": "string",
      "pattern": "^[1-9]\\d*$",
      "description": "Exact watched USDC amount in atomic units. Algorand USDC uses 6 decimals."
    },
    "expectedSender": {
      "type": "string",
      "maxLength": 58,
      "minLength": 58,
      "description": "Checksum-valid nonzero Algorand address expected to send the future payment. The Algorand zero address is rejected for new watch creation."
    },
    "idempotencyKey": {
      "type": "string",
      "maxLength": 128,
      "minLength": 8,
      "description": "Stable key that identifies this watch request and prevents duplicates."
    },
    "expectedReceiver": {
      "type": "string",
      "maxLength": 58,
      "minLength": 58,
      "description": "Checksum-valid Algorand address expected to receive the future payment."
    }
  },
  "additionalProperties": false
}
roundwatch.prepare_watch annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
roundwatch.prepare_recovery — Prepare RoundWatch Recovery
Advertised by the server during the last successful anonymous check.
Advertised read-only

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.

roundwatch.prepare_recovery input schema
{
  "type": "object",
  "required": [
    "idempotencyKey",
    "expectedSender",
    "expectedReceiver",
    "atomicAmount",
    "servicePayer"
  ],
  "properties": {
    "invoiceNote": {
      "type": "string",
      "maxLength": 128,
      "minLength": 1,
      "description": "The exact original optional invoice note, if one was supplied."
    },
    "atomicAmount": {
      "type": "string",
      "pattern": "^[1-9]\\d*$",
      "description": "The exact original watched USDC amount in atomic units."
    },
    "servicePayer": {
      "type": "string",
      "maxLength": 58,
      "minLength": 58,
      "description": "Public Algorand address that signed the original x402 RoundWatch service payment."
    },
    "expectedSender": {
      "type": "string",
      "maxLength": 58,
      "minLength": 58,
      "description": "The exact original expected future-payment sender."
    },
    "idempotencyKey": {
      "type": "string",
      "maxLength": 128,
      "minLength": 8,
      "description": "The exact original idempotency key from the paid create attempt."
    },
    "expectedReceiver": {
      "type": "string",
      "maxLength": 58,
      "minLength": 58,
      "description": "The exact original expected future-payment receiver."
    }
  },
  "additionalProperties": false
}
roundwatch.prepare_recovery annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}
roundwatch.get_watch — Get RoundWatch Watch
Advertised by the server during the last successful anonymous check.
Advertised read-only

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

roundwatch.get_watch input schema
{
  "type": "object",
  "required": [
    "watchId"
  ],
  "properties": {
    "watchId": {
      "type": "string",
      "minLength": 1,
      "description": "Durable watch ID returned after successful activation."
    }
  },
  "additionalProperties": false
}
roundwatch.get_watch annotations
{
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1116 ms
95th percentile latency
1116 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1116 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http roundwatch-mcp https://roundwatch-api.onrender.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add roundwatch-mcp --url https://roundwatch-api.onrender.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable roundwatch-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "roundwatch-mcp": {
      "url": "https://roundwatch-api.onrender.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "roundwatch-mcp": {
      "type": "streamableHttp",
      "url": "https://roundwatch-api.onrender.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start roundwatch-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "roundwatch-mcp": {
      "type": "http",
      "url": "https://roundwatch-api.onrender.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http roundwatch-mcp https://roundwatch-api.onrender.com/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://roundwatch-api.onrender.com/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "roundwatch-mcp": {
      "serverUrl": "https://roundwatch-api.onrender.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like RoundWatch MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.