com.textforagents/event-wake-witness
Event-wake witness for agent triggers
Is the Event-wake witness for agent triggers MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Signed receipts + horizon statements proving whether an event-triggered agent actually woke.
needs auth probed 2026-11-15 · unchanged since 2026-10-26 · HTTP 401
Streamable HTTP error: Error POSTing to endpoint: {"error": "unauthorized \u2014 register at POST /register to get a token, then send it as a Bearer token"}- Endpoint
- https://textforagents.com/products/event-wake-witness/mcp (streamable-http)
- Host
- textforagents.com
- Getting access
- The server answers HTTP 401 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://textforagents.com/products/event-wake-witness/
- Registry
- active, updated 2026-10-20 · registry entry
Compare this server with others.
More servers
Other registry entries on textforagents.com, the ones next to this name; all of them.
- Endpoint Tenure Verdict com.textforagents/endpoint-tenure-verdict · alive
- Ephemeral tool forge com.textforagents/ephemeral-tool-forge · needs auth
- Error-actionability translation for MCP tool failures com.textforagents/error-actionability-translation · needs auth
- ETOPS for Agents: Diversion-Reach Dispatch Certification com.textforagents/etops-diversion-reach-dispatch-for-agents · alive
- Evidence-granularity audit com.textforagents/evidence-granularity-audit · alive
- First-Call Witness com.textforagents/first-call-latency-witness · alive
- Fleet spend circuit-breaker com.textforagents/fleet-spend-circuit-breaker · alive
- Fleet succession: dead-man's switch for agent fleets com.textforagents/fleet-succession-dead-mans-switch · needs auth
Servers that mention witness.
- Supreme Mind ai.suprememind/expert-witness-simulation · needs auth
- com.clauxel.toolcallwitness/toolcallwitness-mcp · no DNS
- SettlementWitness com.defaultverifier/settlement-witness · alive
- KHOTEM com.khotem/khotem-witness · no DNS
- StackWitness com.stackwitness/mcp · needs auth
- Vigil — an outside witness for AI agents com.vigilnotary/vigil · alive
- ViewportWitness by Apex Labs io.github.Baffles78/viewport-witness · alive
- io.github.MarkovianProtocol/provenance · no DNS
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.