Event-wake witness for agent triggers MCP Server

by textforagents Your server? Claim it

answering

Event-wake witness for agent triggers is answering right now. Last checked 7 min ago.

Signed receipts + horizon statements proving whether an event-triggered agent actually woke.

Uptime history 5 days of history · worst day 97%

5 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

343 ms

Response time

average over 24h

authentication required

Access

streamable-http

Event-wake witness for agent triggers does not always answer

Over the last week it answered 99.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add event-wake-witness --transport http https://textforagents.com/products/event-wake-witness/mcp

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

https://textforagents.com/products/event-wake-witness/mcp

~/.codex/config.toml

[mcp_servers.event-wake-witness]
url = "https://textforagents.com/products/event-wake-witness/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "event-wake-witness": {
      "url": "https://textforagents.com/products/event-wake-witness/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "event-wake-witness": {
      "type": "http",
      "url": "https://textforagents.com/products/event-wake-witness/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://textforagents.com/products/event-wake-witness/mcp	streamable-http	needs auth	344 ms	7 min ago

Alternatives to Event-wake witness for agent triggers

same job, measured the same way

Agent Receipts MCP

by dhanushs1912-svg

EU AI Act-ready audit trail: signed, tamper-evident receipts proving what your AI agents did.

26 installs/wk local only

Proof Layer

by world-999-labs

Signed, hash-chained provenance receipts for AI agent actions.

17 installs/wk local only

Landed

by wirt

Read-after-write receipts for agents: did your write actually land? Free, signed, re-checkable.

3 tools answering

Vigil — an outside witness for AI agents

by vigilnotary

Agent leases, signed receipts, watchdogs, and optional paid source-verification evidence.

26 tools answering

Tersign Evidence

by tersignhq

The record layer for the machine age: counter-signed receipts and agent action records.

371 installs/wk local only

Intent Cloak: query-intent privacy for agents

by textforagents

Query-intent privacy for agents: threshold cloaking with signed exposure receipts.

3 tools answering

Agent Receipts

by dropwatchhq

Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.

3 tools answering

Principal Reputation for Agents

by textforagents

Standing minted only from signed settlement receipts, never reviews. Verdicts: ACCEPT to DECLINE.

6 tools answering

Event-wake witness for agent triggers — questions

Answers built from our own checks of this server.

Why is there no tool list for Event-wake witness for agent triggers?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Event-wake witness for agent triggers 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 343 ms. The bar chart above shows every period we have measured.

How do I connect Event-wake witness for agent triggers?

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. You will need your own credentials: it refuses anonymous clients.

Does Event-wake witness for agent triggers need an API key?

Yes. Every time we knock, Event-wake witness for agent triggers answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Event-wake witness for agent triggers?

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