Release-readiness verdict, delivered per API call as an atom service on Conduit Atoms.
Connect Remote server
claude mcp add --transport http atom-release-readiness-verdict https://atoms.pipavia.com/mcp/release-readiness-verdict --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"atom-release-readiness-verdict": {
"url": "https://atoms.pipavia.com/mcp/release-readiness-verdict",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"atom-release-readiness-verdict": {
"type": "http",
"url": "https://atoms.pipavia.com/mcp/release-readiness-verdict",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://atoms.pipavia.com/mcp/release-readiness-verdict
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
The tool list was not available in our last check.
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Your Conduit Atoms gateway key, as 'Bearer <key>'. One gateway key works across atoms; it must hold this atom's scope (release_readiness_verdict). Sign up at https://atoms.pipavia.com, open this atom, and issue your key. |
Details
| Endpoint | https://atoms.pipavia.com/mcp/release-readiness-verdict (Streamable HTTP) |
| First published | 15 Nov 2026 |
| Last updated | 15 Nov 2026 |
| Registry name | org.aimlds/atom-release-readiness-verdict |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
