Deploy to Agents

Deploy to Agents is agent distribution infrastructure for making existing software discoverable, verifiable, and invocable by AI agents.

CommunityOnlineNo sign-inGlobalFreeCan modify data

What it can do

  • Audit App: Queue a bounded audit of a public HTTP or HTTPS app and return an unlisted receipt URL. Reuse get_audit_result until processing completes.
  • Get Audit Result: Retrieve the current status, score, findings, privacy state, and evidence URL for an audit UUID.
  • Create Distribution Plan: Turn a completed technical audit into prioritized remediation plus official-registry, public-repository, customer-evidence, and independent-discovery actions.

What data it sees

Do you need an account

No: the server works without sign-in

Deploy to Agents is agent distribution infrastructure for making existing software discoverable, verifiable, and invocable by AI agents. Audit an app’s public agent-facing surfaces, retrieve persisted scores, findings, and evidence URLs, and create prioritized plans covering technical gaps, official registries, public repositories, customer evidence, and independent discovery. Its public remote MCP server exposes typed tools for audits, results, planning, and Customer Zero evidence.

How to connect

How to connect Deploy to Agents to Claude

The server address to paste into Claude settings:

https://deploy-to-agents--saezbaldo.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Deploy to Agents to ChatGPT

The server address to paste into ChatGPT settings:

https://deploy-to-agents--saezbaldo.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Deploy to Agents to Cursor

The server address to paste into Cursor settings:

https://deploy-to-agents--saezbaldo.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (4)

Raw names from tools/list. Only developers need these.

audit_appQueue a bounded audit of a public HTTP or HTTPS app and return an unlisted receipt URL. Reuse get_audit_result until processing completes.
get_audit_resultRetrieve the current status, score, findings, privacy state, and evidence URL for an audit UUID.
create_distribution_planTurn a completed technical audit into prioritized remediation plus official-registry, public-repository, customer-evidence, and independent-discovery actions.
get_customer_zero_evidenceReturn the public self-audit evidence and the explicit boundary between technical readiness and independent discovery.