Deploy to Agents
REMOTE · DEPLOYTOAGENTS.COM · SCANNED SEP 20
Audit agent-distribution surfaces and create an evidence-based distribution plan.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 228 tokens (~45/item across 5 items; 4 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Deploy to Agents MCP server?
Deploy to Agents is a hosted endpoint at https://deploytoagents.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · deploytoagents.com
claude mcp add --transport http com-deploytoagents-server 'https://deploytoagents.com/mcp'
{
"mcpServers": {
"com-deploytoagents-server": {
"url": "https://deploytoagents.com/mcp"
}
}
} {
"servers": {
"com-deploytoagents-server": {
"type": "http",
"url": "https://deploytoagents.com/mcp"
}
}
} [mcp_servers.com-deploytoagents-server] url = "https://deploytoagents.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-deploytoagents-server": {
"type": "remote",
"url": "https://deploytoagents.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-deploytoagents-server --url 'https://deploytoagents.com/mcp' --transport streamable-http
mcp_servers:
com-deploytoagents-server:
url: "https://deploytoagents.com/mcp" {
"McpServers": {
"com-deploytoagents-server": {
"Transport": "http",
"Url": "https://deploytoagents.com/mcp"
}
}
} assistant mcp add com-deploytoagents-server -t streamable-http -u 'https://deploytoagents.com/mcp'
{
"mcpServers": {
"com-deploytoagents-server": {
"type": "http",
"url": "https://deploytoagents.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 1 Aug 26 0
- HSTS header: fail → pass ▲ security
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://deploytoagents.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=deploytoagents.com | CN=WR3,O=Google Trust Services,C=US | 14 Sept 2026 | 13 Dec 2026 | RSA 2048 | SHA256-RSA | 4131248d9c388c3309849cc312cea7ac |
| SANs: deploytoagents.com, www.deploytoagents.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of deploytoagents.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| deploytoagents.com. | present | 28151 | 8 | Verified |
| deploytoagents.com. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://deploytoagents.com/mcp | Verified | 200 | |
| http (plaintext) | http://deploytoagents.com/mcp | HTTPS enforced | 301 | https://deploytoagents.com:443/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_app Audit an app for agent distribution ~51
Queue a bounded audit of a public HTTP or HTTPS app and return an unlisted receipt URL. Reuse get_audit_result until processing completes.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public website or application URL to audit |
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
| hostname | string | yes | – |
| privacy | string | yes | – |
| receipt_url | string | yes | – |
| status | string | yes | – |
No examples provided.
create_distribution_plan Create an evidence-based distribution plan ~47
Turn a completed technical audit into prioritized remediation plus official-registry, public-repository, customer-evidence, and independent-discovery actions.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | Completed audit UUID |
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
| hostname | string | yes | – |
| limitation | string | yes | – |
| plan | array | yes | – |
| score | – | yes | – |
No examples provided.
get_audit_result Get an audit result ~44
Retrieve the current status, score, findings, privacy state, and evidence URL for an audit UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | Audit UUID returned by audit_app |
| Name | Type | Req | Description |
|---|---|---|---|
| audit_id | string | yes | – |
| completed_at | – | yes | – |
| findings | array | yes | – |
| hostname | string | yes | – |
| receipt_url | string | yes | – |
| requested_at | string | yes | – |
| score | – | yes | – |
| status | string | yes | – |
| visibility | string | yes | – |
No examples provided.
get_customer_zero_evidence Get Deploy to Agents Customer Zero evidence ~29
Return the public self-audit evidence and the explicit boundary between technical readiness and independent discovery.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | – |
| customer_zero | boolean | yes | – |
| externally_verified | array | yes | – |
| independent_discovery_status | string | yes | – |
| next_proof | string | yes | – |
| receipt_url | string | yes | – |
| technical_audit_score | – | yes | – |
No examples provided.
What is the Deploy to Agents MCP server?
Deploy to Agents is an MCP server listed in the public MCP registry as com.deploytoagents/server. Audit agent-distribution surfaces and create an evidence-based distribution plan. This page covers its hosted endpoint (https://deploytoagents.com/mcp).
Is the Deploy to Agents MCP server safe to use?
Deploy to Agents scores 94 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Deploy to Agents MCP server expose?
Deploy to Agents exposes 4 tools: audit_app, get_audit_result, create_distribution_plan, get_customer_zero_evidence. Their descriptions and schemas cost roughly 171 tokens of context every time the server is loaded.
Does the Deploy to Agents MCP server require authentication?
Yes. Deploy to Agents asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Deploy to Agents MCP server still maintained?
Deploy to Agents is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.