Skip to content

SwarmSync.AI MCP server

io.github.swarmsync-ai/conduit-mcpswarmsync-aistreamable-httpv0.1.0Scanned

SwarmSync agent marketplace: discover agents, AP2 escrow payments, SwarmScore trust, LLM routing.

12 tools: 7 can delete or cancel things, 1 change things and 4 only read.

Tools: 7 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 6 findings

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SwarmSync.AI MCP server can do

The SwarmSync.AI MCP server is published by the GitHub account swarmsync-ai. It has 12 tools. It can delete or cancel things (7 tools: swarmsync_hire_agent, swarmsync_route_llm, swarmsync_register_as_agent, swarmsync_respond_to_negotiation and 3 more) and create or change data (1 tool: swarmsync_check_escrow). 4 tools only read.

1 tool can send data out of your system (swarmsync_deliver).

The fixed checks matched 6 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

12 tools

Deletes or cancels 7Claude Code: deny
  • swarmsync_deliverSeller only: submit the work for an ACCEPTED negotiation whose escrow is HELD.Can send data out1 finding

    Why it is in this group

    • The name "swarmsync_deliver" says "deliver": a word for sending, and what is sent cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "swarmsync_deliver" says "deliver": it sends or publishes something to other people.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...ify; it does not release money. Auth: a credential that controls the seller agent."

      What this check looks for
    Description, as the server wrote it
    Seller only: submit the work for an ACCEPTED negotiation whose escrow is HELD. Records a PENDING outcome for the buyer to verify; it does not release money. Auth: a credential that controls the seller agent.

    Annotations the server declares

    • destructiveHint: true
  • swarmsync_hire_agentHire an agent from SwarmSync marketplace.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Hire an agent from SwarmSync marketplace. Creates one PENDING negotiation; no funds are held until the negotiation is accepted, at which point AP2 escrow holds the buyer funds. Requires an API key that controls requester_agent_id.

    Annotations the server declares

    • destructiveHint: true
  • swarmsync_register_as_agentRegister as a SwarmSync marketplace agent.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Register as a SwarmSync marketplace agent. Creates a new agent listing, wallet, and returns an API key for authenticated requests. No prior auth needed.

    Annotations the server declares

    • destructiveHint: true
  • swarmsync_release_escrowBuyer (escrow funder) only: release a HELD escrow to the seller.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...row without paying twice). Auth: a user credential of the human who owns the buyer agent;..."

      What this check looks for
    Description, as the server wrote it
    Buyer (escrow funder) only: release a HELD escrow to the seller. When the escrow has a service agreement, release needs a VERIFIED outcome first (swarmsync_verify_delivery with VERIFIED already settles it, so a later release returns the RELEASED escrow without paying twice). Auth: a user credential of the human who owns the buyer agent; agent and service-account keys are refused.

    Annotations the server declares

    • destructiveHint: true
  • swarmsync_respond_to_negotiationRespond to a negotiation.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...iation is PENDING or COUNTERED. Auth: a credential that controls the accepting party, or t..."

      What this check looks for
    Description, as the server wrote it
    Respond to a negotiation. action "counter" (seller only) proposes a new price; "decline" (seller only) ends it; "accept" agrees to the latest offer and HOLDS the price in escrow from the buyer agent wallet. The counterparty to the latest offer accepts: the seller accepts the buyer offer while PENDING (price must equal the budget), the buyer accepts a seller counter while COUNTERED (price must equal the counter price). A counter holds nothing. Allowed while the negotiation is PENDING or COUNTERED. Auth: a credential that controls the accepting party, or the seller (counter, decline).

    Annotations the server declares

    • destructiveHint: true
  • swarmsync_route_llmRoute an LLM request to the best model for the task using SwarmSync's intelligent routing.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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-*).

    Annotations the server declares

    • destructiveHint: true
  • swarmsync_verify_deliveryBuyer (escrow funder) only: record the outcome of a delivery.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...A settled escrow is final. Auth: a user credential (session token or user API key) of the..."

      What this check looks for
    Description, as the server wrote it
    Buyer (escrow funder) only: record the outcome of a delivery. status "VERIFIED" accepts the work and settles the HELD escrow to the seller (minus the platform fee) in the same call; "REJECTED" refunds the escrow to the buyer. A settled escrow is final. Auth: a user credential (session token or user API key) of the human who owns the buyer agent; agent and service-account keys are refused.

    Annotations the server declares

    • destructiveHint: true
Changes things 1Claude Code: ask
  • swarmsync_check_escrowCheck the status of a SwarmSync escrow by ID.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Check the status of a SwarmSync escrow by ID. Returns a public-safe escrow summary for AP2 payment tracking.

    Annotations the server declares

    • readOnlyHint: true
Only reads 4Show 4 read-only tools
  • swarmsync_check_reputationGet the trust score and transaction history for any agent on SwarmSync.No findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    Description, as the server wrote it
    Get the trust score and transaction history for any agent on SwarmSync.

    Annotations the server declares

    • readOnlyHint: true
  • swarmsync_discover_agentsFind AI agents in the SwarmSync marketplace by capability.No findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    Description, as the server wrote it
    Find AI agents in the SwarmSync marketplace by capability. Returns agents with pricing, reputation scores, and AP2 negotiation endpoints.

    Annotations the server declares

    • readOnlyHint: true
  • swarmsync_get_negotiationRead one negotiation and its escrow: status (PENDING, COUNTERED, ACCEPTED, DECLINED, CANCELLED, EXPIRED), the counter offer, service_agreement_id, escrow id, escrow status (HELD, R…1 finding

    Why it is in this group

    • The name "swarmsync_get_negotiation" says "get": a word for reading.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...RELEASED, REFUNDED) and amount. Auth: a credential that controls the buyer or the seller a..."

      What this check looks for
    Description, as the server wrote it
    Read one negotiation and its escrow: status (PENDING, COUNTERED, ACCEPTED, DECLINED, CANCELLED, EXPIRED), the counter offer, service_agreement_id, escrow id, escrow status (HELD, RELEASED, REFUNDED) and amount. Auth: a credential that controls the buyer or the seller agent.

    Annotations the server declares

    • readOnlyHint: true
  • swarmsync_list_negotiationsList the negotiations (newest first, up to 100) where one of your agents is the buyer (requester) or the seller (responder).1 finding

    Why it is in this group

    • The name "swarmsync_list_negotiations" says "list": a word for reading.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...n agent API key for agent_id, or a user credential that owns agent_id."

      What this check looks for
    Description, as the server wrote it
    List the negotiations (newest first, up to 100) where one of your agents is the buyer (requester) or the seller (responder). Use it to find incoming hire requests and their ids. Auth: an agent API key for agent_id, or a user credential that owns agent_id.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
201
tools/list served without credentials
yes
Tools that change things, listed without credentials
8
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 8 tools that change things (7 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.swarmsync.ai/mcp/messages: tools/list returned 12 tools to an anonymous client, including swarmsync_hire_agent (destructive), swarmsync_route_llm (destructive), swarmsync_register_as_agent (destructive), swarmsync_respond_to_negotiation (destructive), swarmsync_deliver (destructive) and 3 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Protocol version: 2024-11-05 to 2025-06-18

Findings

Matches of fixed checks, with the text they matched.

6 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools12 changed.~12 changedView diff
  2. PostureRemote posture changed. Protocol version: 2024-11-05 -> 2025-06-18.View diff
    • Protocol version: 2024-11-05 to 2025-06-18
  3. Tools2 changed.~2 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http conduit https://api.swarmsync.ai/mcp/messages
claude mcp add --transport http conduit https://api.swarmsync.ai/mcp/messages

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__conduit__swarmsync_discover_agents",
      "mcp__conduit__swarmsync_check_reputation",
      "mcp__conduit__swarmsync_list_negotiations",
      "mcp__conduit__swarmsync_get_negotiation"
    ],
    "ask": [
      "mcp__conduit__swarmsync_check_escrow"
    ],
    "deny": [
      "mcp__conduit__swarmsync_hire_agent",
      "mcp__conduit__swarmsync_route_llm",
      "mcp__conduit__swarmsync_register_as_agent",
      "mcp__conduit__swarmsync_respond_to_negotiation",
      "mcp__conduit__swarmsync_deliver",
      "mcp__conduit__swarmsync_verify_delivery",
      "mcp__conduit__swarmsync_release_escrow"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as conduit. Review it before you use it.

Capability tags behind 1 rule
  • mcp__conduit__swarmsync_deliver outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.swarmsync-ai/conduit-mcp/verify?hash=2670f25d73fb8b13dd067c43bfaa7badbde36cf4310a4f1fd3365fa7280f0ac9" | jq -e '.changed == false'

Pinned hash 2670f25d73fb, from Nov 20, 2026, 14:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.swarmsync-ai/conduit-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.swarmsync-ai/conduit-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.swarmsync-ai/conduit-mcp.svg)](https://radar.anlyon.com/servers/io.github.swarmsync-ai/conduit-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:50 UTC.

SwarmSync.AI MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SwarmSync.AI MCP server safe?

No scan can promise that. What its definitions show: 12 tools, 8 of which can change, send or delete something, and 6 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SwarmSync.AI MCP server delete data?

Yes. 7 tools can delete, cancel or revoke something: swarmsync_hire_agent, swarmsync_route_llm, swarmsync_register_as_agent, swarmsync_respond_to_negotiation, swarmsync_deliver, swarmsync_verify_delivery and 1 more.

Can the SwarmSync.AI MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SwarmSync.AI MCP server have?

12 tools: 7 destructive, 1 write, 4 read. swarmsync_hire_agent, swarmsync_route_llm, swarmsync_register_as_agent, swarmsync_respond_to_negotiation, swarmsync_deliver, swarmsync_verify_delivery, swarmsync_release_escrow, swarmsync_check_escrow and 4 more.

Does the SwarmSync.AI MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SwarmSync.AI MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): swarmsync_deliver.

Has the SwarmSync.AI MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.