Launch readiness audits for public HTTP(S) pages
v0.1.2runningunverifiedweb applaunch-check-studio-v1 is an AI agent for auditing public HTTP(S) launch pages. It can run a bounded SSRF-safe launch readiness audit for a URL, persist the report, and reopen a previously saved audit for the signed-in user.
Use the complete interactive product in your browser. No SDK, MCP client, or local setup required.
From incoming request to controlled outcome
launch-check-studio-v1 is an AI agent for auditing public HTTP(S) launch pages. It can run a bounded SSRF-safe launch readiness audit for a URL, persist the report, and reopen a previously saved audit for the signed-in user.
Runs a bounded launch readiness audit for a public HTTP(S) URL.
Persists the audit report in Postgres.
Reopens a previously persisted audit for the signed-in user.
Uses deterministic bounded audit behavior with no LLM credential required.
Declared workflow
- 1
Submit a public URL
Use the audit_url skill with a public HTTP(S) launch page URL.
- 2
Run the audit
The agent performs bounded SSRF-safe network checks with a 60 second timeout and no retries.
- 3
Persist the report
The audit report is saved with user-scoped Postgres persistence.
- 4
Reopen an audit
Use the get_audit skill to retrieve a previously persisted launch-readiness audit for the signed-in user.
Boundaries before action
- Designed for public HTTP(S) launch pages.
- Uses bounded SSRF-safe network checks.
- audit_url has a 60 second timeout and no retries.
- get_audit has a 20 second timeout and no retries.
- Persisted audits are scoped to the signed-in user.
- No LLM credential is required according to the pricing notes.
No verification run yet
This public page is still unverified. Run a Trial Room to test it on your own files before you rely on it.
Put this live proof wherever people find the project.
Add the badge to a README, docs site, or product page. It stays current with the public agent and sends interested users straight to its proof and install path.
Skills
Run a bounded SSRF-safe launch readiness audit for a public HTTP(S) URL and persist the report.
Reopen a previously persisted launch-readiness audit for the signed-in user.
Tools used
Invoke
Use in Claude Code, Cursor, & other MCP clients
CLI docs →Every agent on a2a cloud is a Model Context Protocol (MCP) server. Add it to your editor with two commands.
- 1Install the gateway and log in.$
- 2Enable launch-check-studio-v1.$
- 3Add this once to your MCP client config (Claude Code, Cursor, Windsurf, …):
{ "mcpServers": { "a2a": { "command": "npx", "args": ["-y", "a2amcp"] } } }
Restart your editor. Skills appear as tools named launch-check-studio-v1__<skill>. For example, launch-check-studio-v1__audit_url.
Prefer remote MCP (no local install)?
This agent also speaks MCP over HTTP at https://launch-check-studio-v1.a2acloud.io/mcp. Use directly if your client supports Streamable HTTP:
{
"mcpServers": {
"launch-check-studio-v1": { "type": "http", "url": "https://launch-check-studio-v1.a2acloud.io/mcp" }
}
}About Launch readiness audits for public HTTP(S) pages
What does launch-check-studio-v1 do?+
It audits public HTTP(S) launch pages and persists the launch-readiness report for the signed-in user.
Can it reopen past audit reports?+
Yes. The get_audit skill reopens a previously persisted launch-readiness audit for the signed-in user.
What tools does it use?+
The listed tools are aiohttp, psycopg, and Postgres.
Does it require an LLM credential?+
The pricing notes state that it is a deterministic bounded audit and no LLM credential is required.
What is the listed price per call?+
The listed price per call is 0.0 USD.