Protocol discovery
Can the endpoint expose a tool catalog using the selected protocol? Limited schema checks surface concrete fixes.
MCP READINESS CHECK / PREVIEW
Check your MCP server.
Find what needs fixing. Then try a real tool call and keep a test you can run again.
Check your server
01 / INSPECTReady when you are.
02 / FINDINGS
What needs attention
Compare with a baseline
Choose an earlier readiness JSON export to see what changed. The file stays in this browser and is never uploaded. Catalog metadata only; runtime behavior remains untested.
Choose a baseline after running a check.
Observed checks and untested behavior
Discovered tools and declared schemas
Network and authentication observations
Profile identity and coverage
Examples, saved plans and local testing
Test a tool
PreviewChoose a saved plan or prepare a staging test. Nothing runs until you ask.
Test inputs
Edit inputs as JSON
For nested objects, arrays or complex schemas. Inputs are validated before a call.
Select a tool to review the target and call count.
Run test sends these inputs using your workspace connection. Use a staging server you have permission to test.
Export this result
More options
Test options
These inputs should satisfy the schema and return MCP isError. Adds one call.
Plan files
Plans stay in this browser and include your test inputs, never connection tokens. Loading or importing only prepares a test.
Try a synthetic example
See the results without connecting a server. These examples run in your browser and make no provider calls.
Run on your computer
For localhost, private servers or complex contracts. Download the standalone tester, then run node agentaction-mcp-tester.mjs with Node 22 or newer. It opens this test editor locally. No npm install.
Open a local or CI report
Opened locally and labeled as imported, unverified evidence.
WHAT THE CHECK TELLS YOU
Agent usability
Do tool descriptions and result contracts give an agent enough information to plan its next step?
Action safety
Which declarations deserve closer review? Permissions, side effects and retry behavior remain untested.
Guidance with a source
Ruleset 2026-09-22.1. Released-spec guidance is separate from recommendations and text heuristics. A clean report is not a conformance or safety certificate. Missing optional metadata is never a protocol failure.
2026-07-28 specification ↗Official conformance suite ↗Published observations expire after 24 hours. A changed catalog needs a new check; unchanged schemas do not prove unchanged backend behavior. Account-specific catalogs can differ.