Connect to
the evidence.

From account to connection.

Store credentials in your client’s secret controls or environment. This guide never asks you to paste a token into the website. Never include a token in a prompt, URL, screenshot or committed configuration.

Eligible Pro access is currently US$29/month or US$250/year. Confirm your account’s API capability and current plan terms. Report generation and optional provider usage have separate access and cost conditions.

Make the first read.

Use your MCP client’s connection flow. For a raw HTTP client, initialize with protocol version 2024-11-05, send notifications/initialized, and retrieve tools/list. Keep the authorization header on authenticated requests.

curl https://watchtower.technology/agent/mcp \
  -H "Authorization: Bearer $WATCHTOWER_MCP_TOKEN" \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"your-client","version":"1.0"}}}'

Next, discover a relevant route. These are request examples, not observations or current-event claims.

{
  "jsonrpc": "2.0", "id": 2, "method": "tools/call",
  "params": {
    "name": "watchtower.list_data_routes",
    "arguments": {"category": "weather-hazards", "query": "earthquakes"}
  }
}

Use a path returned by discovery, then request a bounded page:

{
  "jsonrpc": "2.0", "id": 3, "method": "tools/call",
  "params": {
    "name": "watchtower.read_data_route",
    "arguments": {"path": "/agent/api/earthquakes", "limit": 20}
  }
}

The reader returns dataset metadata, JSON Pointer/value records, a snapshot identity and pagination fields. Tool results may be wrapped in MCP content blocks; inspect the returned content and error flags before using it.

Keep the snapshot. Follow the pages.

1. Discover a route with watchtower.list_data_routes. Follow its page.nextOffset when listing more routes.
2. Read the selected path. Preserve its snapshot, capturedAt, snapshotExpiresAt, source dates and coverage fields.
3. If page.hasMore is true, repeat the same path, query and selector with the returned snapshot and offset: page.nextOffset.
4. For long-string continuations, use the returned text continuation pointer/offset fields with the current tool schema. A selector can focus on a JSON subtree.
5. If the snapshot expires, start a new read. Do not silently combine pages from different snapshots.

{
  "name": "watchtower.read_data_route",
  "arguments": {
    "path": "/agent/api/earthquakes",
    "snapshot": "COPY_THE_RETURNED_SNAPSHOT",
    "offset": 20,
    "limit": 20
  }
}

Use the actual returned offset rather than assuming it is 20. Dataset pagination may be separate from reader pagination: finishing a JSON snapshot does not establish complete upstream coverage. Respect source scope, stale/degraded flags and missing values.

Discover, read, investigate.

Checked 9 October 2026: public MCP metadata advertised 12 tools; the authenticated reviewed catalogue reported 178 routes for the checking account. Counts and entitlements can change. The live schemas are authoritative.

Use the evidence within its scope.

The reviewed dataset reader is read-only. It excludes account records, credentials, API connections, billing, admin operations, raw tokens, private workspaces and portfolios, private reports/settings, streams and mutation routes. Optional report generation is a separate tool, not a dataset-reader capability.

• Use only the access authorized for your current user and task.
• Choose discovered paths; do not supply arbitrary URLs, owner selectors or force/cache-busting arguments.
• Cite source links and observation dates. Separate observations, calculated assessments and your own interpretation.
• Keep missing values missing. A cached response or a populated field does not establish that a source is current.
• Follow source attribution/licensing requirements; API access is not blanket redistribution permission.

When a request needs attention.