Is an AI tool, agent or MCP server alive, and since when? Checks from the outside, with proof.
Scored across 3 tools
The three tools map to cleanly separate verbs over the same domain: check_url performs a live one-off check of any address, lookup_tool reads AgentViva's already-known state for a watched tool, and report_problem submits a user report that may trigger a re-check. Descriptions explicitly cross-reference each other (e.g. 'for a tool AgentViva does not watch, use check_url'), so an agent can pick the right one without guessing.
All three follow the same snake_case verb_noun pattern: check_url, lookup_tool, report_problem. No mixed casing or stylistic deviations, and the verb choice accurately signals the action (check vs. lookup vs. report).
Three tools is a deliberately narrow surface that matches a focused status-checking service, and each tool covers a distinct interaction (live check, known state, feedback). It sits at the low end of the ideal range, so there is little room to grow without adding capabilities, but nothing is redundant.
The core lifecycle is covered: on-demand checking, looking up confirmed watches and history, and reporting a problem, with clear fallback guidance between them. The main gap is discoverability — there is no way to list or browse the tools AgentViva watches, so an agent must already know a name or address.
Check any public website or hosted MCP server once, right now, and get what AgentViva saw: works, partly works, does not work, or blocked (the site refused the check or asks bots not to open it, which does not mean it is down), with the evidence (HTTP status, where the redirects ended, the page title, or the MCP tools it lists). No API key needed. One check is a snapshot, not a verdict over time: for a tool AgentViva watches every day, lookup_tool gives its confirmed state and history. The same address is answered from a 5-minute copy. Private and local addresses are refused.
Inputs: url (required), type.
Look up an AI tool AgentViva already watches publicly, by name ("Notion") or address ("notion.so"), and get its state (up, degraded, down, blocked or unknown), since when, and its public status page. No API key needed. It reads what AgentViva already knows; it does not check the address now.
Inputs: query (required).
Tell AgentViva that a tool it watches publicly does not work for you or your user, by name ("Notion") or address ("notion.so"), with an optional short note of what happened. AgentViva checks it again right away (at most once an hour per tool) and answers with what that check saw. A report never changes the tool's state by itself: only AgentViva's own checks do, and several must agree. One report per network, tool and day is counted. No API key needed. For a tool AgentViva does not watch, use check_url instead.
Inputs: query (required), note.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Live index of AI agents, MCP servers and tools with observed liveness and capability search.
Checks whether a web page is ready for AI agents and whether an MCP server meets directory rules
Network, domain and website diagnostics for AI clients via MCP.
Look up AI agents, MCP servers and x402 APIs: whether they answer, how they ask to be paid.
Add one secure layer between your agents and this server.
