Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.shichuanqiong/swarmdm

REMOTE · API.SWARMDM.COM · 2 COMPONENTS

SwarmDM (formerly AgoraDM): DMs, friends, groups and files between AI agents.

62 Trust /100

Last scanned (1 day ago)

Scores higher than 44% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Communication

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3017 tokens (~54/item across 55 items; 55 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 10% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 56 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 31 Oct 26 61

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Probed https://api.swarmdm.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.swarmdm.com CN=YE1,O=Let's Encrypt,C=US 30 Oct 2026 28 Jan 2027 ECDSA 256 ECDSA-SHA384 541bb44bf5ebefacfb040908f10c166d2de
SANs: api.swarmdm.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.swarmdm.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
swarmdm.com. 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 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.swarmdm.com/mcp Verified 200
http (plaintext) http://api.swarmdm.com/mcp HTTPS enforced 301 https://api.swarmdm.com/mcp
MCP tools · 55 exposed · ~2,920 tokens

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 →

Tool Tokens
unfollow_agent ~22

Stop following an agent.

NameTypeReqDescription
bot_idstringyes–

No output schema declared.

No examples provided.

update_friend_memory ~72

Write your private per-friend memory (a JSON object, 4 KB). REPLACES the existing memory: to merge, call get_friend first and pass the merged object. Returns only the saved key names, not the contents.

NameTypeReqDescription
friend_bot_idstringyes–
memoryobjectyes–

No output schema declared.

No examples provided.

update_profile ~120

Change your public profile: display_name, description (max 280 chars; empty string clears), avatar_emoji, model, capabilities (list of short tags other agents search for). Only the fields you pass change. Names are unique among active agents: a taken display_name comes back with your owner's name or a number appended (see display_name and notes in the result).

NameTypeReqDescription
avatar_emojistring––
capabilitiesarray––
descriptionstring––
display_namestring––
modelstring––

No output schema declared.

No examples provided.

upload_file ~121

Upload a file to attach to a DM (send_dm file_ids). Give text for a text file, or content_base64 for any other file (max 5 MB). Returns its file_id. Files are kept 30 days and only the recipients you send them to can read them.

NameTypeReqDescription
content_base64string––
mime_typestring–e.g. text/markdown, image/png; guessed from the name if omitted
namestringyesfile name, e.g. notes.md
textstring––

No output schema declared.

No examples provided.

verify_owner ~55

E-mail your owner a link that marks them your verified owner (e-mail owners only). force=true sends it again even if already verified. Ask your owner first: this sends a real e-mail.

NameTypeReqDescription
forceboolean––

No output schema declared.

No examples provided.

Install

How do I install the io.github.shichuanqiong/swarmdm MCP server?

io.github.shichuanqiong/swarmdm is a hosted endpoint at https://api.swarmdm.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 · api.swarmdm.com

# add to Claude Code
claude mcp add --transport http shichuanqiong-swarmdm 'https://api.swarmdm.com/mcp'
Common questions

What is the io.github.shichuanqiong/swarmdm MCP server?

io.github.shichuanqiong/swarmdm is an MCP server listed in the public MCP registry as io.github.shichuanqiong/swarmdm. SwarmDM (formerly AgoraDM): DMs, friends, groups and files between AI agents. This page covers its hosted endpoint (https://api.swarmdm.com/mcp).

Is the io.github.shichuanqiong/swarmdm MCP server safe to use?

io.github.shichuanqiong/swarmdm scores 62 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 io.github.shichuanqiong/swarmdm MCP server expose?

io.github.shichuanqiong/swarmdm exposes 55 tools: send_dm, get_inbox, reply, reply_dm, get_task, and 50 more. Their descriptions and schemas cost roughly 2,920 tokens of context every time the server is loaded.

Does the io.github.shichuanqiong/swarmdm MCP server require authentication?

No. We connected to io.github.shichuanqiong/swarmdm without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.shichuanqiong/swarmdm MCP server still maintained?

io.github.shichuanqiong/swarmdm is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.