Outcome-verified watchdog for scheduled agents MCP Server

by textforagents Your server? Claim it

answering

Outcome-verified watchdog for scheduled agents is answering right now. Last checked 6 min ago. It exposes 8 tools.

Watchdog that verifies scheduled agents' artifacts itself — never the claim.

Uptime history 70 hours of history

70 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

320 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Outcome-verified watchdog for scheduled agents every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add scheduled-agent-outcome-verification --transport http https://textforagents.com/products/scheduled-agent-outcome-verification/mcp

Settings → Connectors → Add custom connector, then paste this address

https://textforagents.com/products/scheduled-agent-outcome-verification/mcp

~/.codex/config.toml

[mcp_servers.scheduled-agent-outcome-verification]
url = "https://textforagents.com/products/scheduled-agent-outcome-verification/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "scheduled-agent-outcome-verification": {
      "url": "https://textforagents.com/products/scheduled-agent-outcome-verification/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "scheduled-agent-outcome-verification": {
      "type": "http",
      "url": "https://textforagents.com/products/scheduled-agent-outcome-verification/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

checkpoint

checkpoint

Report run progress — the watchdog watches progress checkpoints against the job's own wall-clock budget, never process existence. Args: run_id, note?.

complete

complete_run

Claim completion; the watchdog verifies the declared artifact itself (the claim is never trusted) and issues a signed, hash-chained verdict receipt. Metered check ($0.002 after the one-time 100-check trial / plan rules). Args: run_id, claimed?.

last

last_verified_success

When was this job's last VERIFIED success, and how old is it? Args: job_id.

register_job

Register a scheduled job with an outcome contract (file / URL / record, present + non-empty + fresh, optional hash/marker — or a chain contract whose stages' artifacts are the next stage's required input). Args: job_id, contract, stall_budget_s?, due_in_s?, alert via account webhook.

start

start_run

Start a run for a job. Args: job_id.

verdicts

list_verdicts

List this operator's signed verdict receipts + receipt-chain re-verification result.

verify

verify_now

Spot-verify a job's artifact now (independent fetch/hash/read-back by the watchdog). Metered check ($0.002 after trial / plan rules). Args: job_id.

watchdog

watchdog_tick

Run the watchdog sweep: STALLED for active runs with no progress checkpoint inside the job's wall-clock budget, MISSED once per due window with no verified run. Not metered.

Endpoints

URL	Transport	State	Latency	Checked
https://textforagents.com/products/scheduled-agent-outcome-verification/mcp	streamable-http	answering	316 ms	6 min ago

Alternatives to Outcome-verified watchdog for scheduled agents

same job, measured the same way

Twothumbs

by asselwan

Verifies AI agent work end to end: real artifacts and outcomes checked, not self-reported success.

3 tools answering

Agent News by The Agent Times

by theagenttimes

Verified, sourced, real-time intelligence layer for AI agents.

20 tools answering

AstraNL Crossing

by astranl

Look before work, claim it, check a spend, mark the outcome. For agents sharing tasks. No key.

12 tools answering

Dingdawg Loop

by dingdawg

Safe scheduled AI agents with governance gates. Verified, receipted, fail-closed.

18 installs/wk local only

AFG: agents hire agents (test money)

by afg

Sandbox marketplace where AI agents hire agents for verified outcomes. Test money only.

18 tools answering

Elliot

by emanuelecell4

Independent verifier for AI agents: checks agent claims and doc promises against the code.

local only

Swiss Truth MCP

by swisstruthorg

Verified knowledge base for AI agents — stop hallucinations with certified facts.

16 installs/wk local only

DidWork

by didwork

Verify that an agent's claimed outcome actually happened, using independently gathered evidence

59 installs/wk local only

Outcome-verified watchdog for scheduled agents — questions

Answers built from our own checks of this server.

What can Outcome-verified watchdog for scheduled agents do?

It exposes 8 tools, read directly from the server on our last check. Among them: checkpoint, complete_run, last_verified_success, list_verdicts, register_job, start_run and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Outcome-verified watchdog for scheduled agents working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 320 ms. The bar chart above shows every period we have measured.

How do I connect Outcome-verified watchdog for scheduled agents?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Outcome-verified watchdog for scheduled agents need an API key?

No. Outcome-verified watchdog for scheduled agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Outcome-verified watchdog for scheduled agents?

It answers our handshake in 320 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.