Deploy to Agents
Audit agent-distribution surfaces and create an evidence-based distribution plan.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http deploy-to-agents 'https://deploytoagents.com/mcp'
{
"mcpServers": {
"deploy-to-agents": {
"type": "http",
"url": "https://deploytoagents.com/mcp"
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
Deploy to Agents SDK
Public JavaScript client and registry metadata for the Deploy to Agents remote MCP server.
The remote server is published in the official MCP Registry as com.deploytoagents/server and is served from https://deploytoagents.com/mcp. The JavaScript client and authenticated agent-first CLI are published as deploytoagents@0.4.1 on npm, with an equivalent deploytoagents==0.1.1 client on PyPI.
Agent-first CLI
npx deploytoagents login
npx deploytoagents whoami
npx deploytoagents portfolio --json
npx deploytoagents discovery --json
npx deploytoagents discovery-record --input observation.json --json
npx deploytoagents audit https://example.com --json
The package installs both deploytoagents and the shorter d2a command. Google login uses Authorization Code with PKCE and a temporary loopback callback. On Windows the refresh credential is encrypted for the current OS user with DPAPI; CI can provide a short-lived identity token through DEPLOYTOAGENTS_TOKEN. Discovery Lab can be read or supplied with a JSON observation file (or stdin via --input -). All command results and errors have stable JSON forms for agent use.
{
"hostname": "example.com",
"surface": "claude",
"model": "model label shown by the surface",
"prompt": "Exact generic, unbranded prompt",
"outcome": "not-mentioned",
"freshSession": true,
"responseExcerpt": "Optional relevant excerpt",
"citations": ["https://example.org/source"]
}
Valid outcomes are recommended, mentioned, not-mentioned, and error. The server verifies that the signed-in organization owns the target hostname.
Deploy to Agents currently audits public agent-facing surfaces, returns unlisted evidence receipts, and creates prioritized technical and external-authority distribution plans. It does not yet claim to publish every customer artifact or guarantee recommendation by any model.
Connect directly through MCP
Use this Streamable HTTP endpoint in any compatible MCP client:
https://deploytoagents.com/mcp
Available tools:
audit_appget_audit_resultcreate_distribution_planget_customer_zero_evidence
JavaScript client
npm install deploytoagents
import { DeployToAgentsClient } from "deploytoagents";
const client = new DeployToAgentsClient();
try {
const queued = await client.auditApp("https://example.com");
console.log(queued.receipt_url);
const result = await client.getAuditResult(queued.audit_id);
if (result.status === "completed") {
console.log(await client.createDistributionPlan(queued.audit_id));
}
} finally {
await client.close();
}
Python client
pip install deploytoagents
from deploytoagents import DeployToAgentsClient
async with DeployToAgentsClient() as client:
queued = await client.audit_app("https://example.com")
print(queued["receipt_url"])
Customer Zero
Deploy to Agents uses its own system as its first customer. The current 100/100 receipt verifies technical surfaces only. Independent, unbranded discovery remains explicitly not-yet-proven.
Development
npm install
npm test
npm run smoke
Evidence policy
This project distinguishes owned evidence, externally verified artifacts, and independent recommendations. It does not create fake testimonials, automated community posts, coordinated votes, or links intended primarily to manipulate rankings.
License
MIT
Frequently asked questions
What is Deploy to Agents?
Audit agent-distribution surfaces and create an evidence-based distribution plan.
How do I install Deploy to Agents?
It runs as a remote server. In Claude Code: claude mcp add --transport http deploy-to-agents 'https://deploytoagents.com/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Deploy to Agents need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Deploy to Agents open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Deploy to Agents?
It is published by saezbaldo. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.