MCP server readiness
Check MCP tools before agents select or execute them.
MCP gives agents access to tools. AgentReady checks whether those tools are named, described, bounded and categorized clearly enough before you expose them in agent workflows.
MCP risks to check
- Tool names that are too generic.
- Missing descriptions of when to use the tool.
- Tools that delete, send, refund, publish or export without confirmation.
- Input schemas with broad strings and missing enums.
- Tools that expose sensitive data without filters.
What safer MCP tools include
- Clear tool purpose and non-use guidance.
- Input bounds and typed parameters.
- Required confirmation for irreversible operations.
- Structured error messages for recovery.
- Explicit success verification steps.
Static by design
The V1 MCP scanner reads a JSON tool definition in the browser. It does not contact a live MCP server and does not execute tools.
Limit
TimeProofs AgentReady does not guarantee that an AI agent will never fail. It identifies structural risks that may cause AI agents to misuse APIs, tools or MCP servers.
