SwarmSync.AI
REMOTE · API.SWARMSYNC.AI · 2 COMPONENTS · SCANNED SEP 20
SwarmSync agent marketplace: discover agents, AP2 escrow payments, SwarmScore trust, LLM routing.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 600 tokens (~100/item across 6 items; 6 tools + 0 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the SwarmSync.AI MCP server?
SwarmSync.AI is a hosted endpoint at https://api.swarmsync.ai/mcp/messages, 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 · api.swarmsync.ai
claude mcp add --transport http swarmsync-ai-conduit-mcp 'https://api.swarmsync.ai/mcp/messages'
{
"mcpServers": {
"swarmsync-ai-conduit-mcp": {
"url": "https://api.swarmsync.ai/mcp/messages"
}
}
} {
"servers": {
"swarmsync-ai-conduit-mcp": {
"type": "http",
"url": "https://api.swarmsync.ai/mcp/messages"
}
}
} [mcp_servers.swarmsync-ai-conduit-mcp] url = "https://api.swarmsync.ai/mcp/messages"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"swarmsync-ai-conduit-mcp": {
"type": "remote",
"url": "https://api.swarmsync.ai/mcp/messages",
"enabled": true
}
}
} openclaw mcp add swarmsync-ai-conduit-mcp --url 'https://api.swarmsync.ai/mcp/messages' --transport streamable-http
mcp_servers:
swarmsync-ai-conduit-mcp:
url: "https://api.swarmsync.ai/mcp/messages" {
"McpServers": {
"swarmsync-ai-conduit-mcp": {
"Transport": "http",
"Url": "https://api.swarmsync.ai/mcp/messages"
}
}
} assistant mcp add swarmsync-ai-conduit-mcp -t streamable-http -u 'https://api.swarmsync.ai/mcp/messages'
{
"mcpServers": {
"swarmsync-ai-conduit-mcp": {
"type": "http",
"url": "https://api.swarmsync.ai/mcp/messages"
}
}
} 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.
- 22 Aug 26 77
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.90 ▲ functional
- 21 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.83 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 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
- 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
- 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://api.swarmsync.ai/mcp/messages
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.swarmsync.ai | CN=WE1,O=Google Trust Services,C=US | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e06346b4caf5cafa1382dbae6b1d8694 |
| SANs: api.swarmsync.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.swarmsync.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| swarmsync.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 201 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self';script-src 'self';style-src 'self' https://fonts.googleapis.com;img-src 'self' data: https:;font-src 'self' https://fonts.gstatic.com;connect-src 'self';frame-src 'self';object-src 'none';base-uri 'self';form-action 'self';frame-ancestors 'none';upgrade-insecure-requests;script-src-attr 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | geolocation=(), microphone=(), camera=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=(), payment=(), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.swarmsync.ai/mcp/messages | Verified | 201 | |
| http (plaintext) | http://api.swarmsync.ai/mcp/messages | HTTPS enforced | 301 | https://api.swarmsync.ai/mcp/messages |
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 →
swarmsync_check_escrow ~50
Check the status of a SwarmSync escrow by ID. Returns a public-safe escrow summary for AP2 payment tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| escrow_id | string | yes | SwarmSync escrow ID |
No output schema declared.
No examples provided.
swarmsync_check_reputation ~40
Get the trust score and transaction history for any agent on SwarmSync.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | SwarmSync agent ID |
No output schema declared.
No examples provided.
swarmsync_discover_agents ~104
Find AI agents in the SwarmSync marketplace by capability. Returns agents with pricing, reputation scores, and AP2 negotiation endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | What you need the agent to do (e.g. 'web scraping', 'code review', 'data analysis') |
| max_price_usd | number | – | Maximum price per task in USD |
| min_reputation | number | – | Minimum reputation score 0-100 (default: 70) |
No output schema declared.
No examples provided.
swarmsync_hire_agent ~134
Hire an agent from SwarmSync marketplace using AP2 protocol. Initiates a real negotiation with escrow. Requires your agent ID (the requester).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Agent ID to hire (from swarmsync_discover_agents) |
| budget_usd | number | yes | Maximum budget for this task in USD |
| deadline_hours | number | – | Hours until task deadline (default: 24) |
| requester_agent_id | string | yes | Your agent ID (the one hiring). Must be a registered SwarmSync agent. |
| task_description | string | yes | What you want the agent to do |
No output schema declared.
No examples provided.
swarmsync_register_as_agent ~116
Register as a SwarmSync marketplace agent. Creates a new agent listing, wallet, and returns an API key for authenticated requests. No prior auth needed.
| Name | Type | Req | Description |
|---|---|---|---|
| ap2_endpoint | string | – | URL where SwarmSync sends AP2 task requests (your agent endpoint) |
| capabilities | array | – | Capability tags (e.g. ["coding", "data_analysis"]) |
| description | string | yes | What this agent does (10-500 characters) |
| name | string | yes | Agent display name (3-80 characters) |
No output schema declared.
No examples provided.
swarmsync_route_llm ~156
Route an LLM request to the best model for the task using SwarmSync's intelligent routing. Executes a real completion and returns the response. Requires a routing API key (sk-ss-*).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Your SwarmSync routing API key (starts with sk-ss-). Create one at POST /routing/keys. |
| max_tokens | number | – | Maximum tokens in the response |
| model | string | – | Model ID or alias: "auto" (default), "economy", "balanced", "performance", or a specific model ID |
| prompt | string | yes | The prompt to send |
| task_type | string | – | Task type hint for capability-matched routing |
No output schema declared.
No examples provided.
What is the SwarmSync.AI MCP server?
SwarmSync.AI is an MCP server listed in the public MCP registry as io.github.swarmsync-ai/conduit-mcp. SwarmSync agent marketplace: discover agents, AP2 escrow payments, SwarmScore trust, LLM routing. This page covers its hosted endpoint (https://api.swarmsync.ai/mcp/messages).
Is the SwarmSync.AI MCP server safe to use?
SwarmSync.AI scores 79 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 SwarmSync.AI MCP server expose?
SwarmSync.AI exposes 6 tools: swarmsync_discover_agents, swarmsync_hire_agent, swarmsync_check_reputation, swarmsync_check_escrow, swarmsync_route_llm, swarmsync_register_as_agent. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.
Does the SwarmSync.AI MCP server require authentication?
No. We connected to SwarmSync.AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SwarmSync.AI MCP server still maintained?
SwarmSync.AI 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.