Block integration before missing metadata becomes a runtime failure.
Supply a server card, the version and tools your workflow expects, then branch only on the explicit readiness result.
Step 1 · Check the supplied metadata
Send the metadata object—not a URL to fetch
curl https://api.scrubmytext.com/v1/readiness/check -H "Content-Type: application/json" -d '{"server_card":{"serverInfo":{"name":"com.example/tools","version":"1.2.0"},"transport":{"type":"streamable-http","endpoint":"/mcp"},"protocolVersion":"2025-11-25","tools":[{"name":"search"},{"name":"fetch"}]},"expected_version":"1.2.0","required_tools":["search","fetch"]}'Step 2 · Enforce the decision
Continue only on ready: true
If false, report the failed check IDs and stop installation or request an explicit operator exception. Do not silently ignore a missing version, tool, protocol, or required transport.
MCP workflow
1. Obtain server metadata through your trusted discovery path.
2. check_agent_readiness({"server_card":{...},"expected_version":"1.2.0","required_tools":["search","fetch"]})
3. Continue only when ready is true.
4. Surface failed checks; never treat this report as a security certification.Limits
- The API checks only the supplied object and never fetches the endpoint.
- A pass does not prove ownership, safety, uptime, or actual tool behavior.
- Use authenticated discovery and separate behavioral tests for consequential integrations.