disdex: Discord server search
REMOTE · DISDEX.IO
Find public Discord servers by topic, language and size, check invite links, see member growth.
Available components
Last scanned (9 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category News and Social
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 701 tokens (~140/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% 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
- We read all 5 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 current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 73
First indexed and scored.
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 5 Nov 2026 · Probed https://disdex.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=disdex.io | CN=YE2,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 57edd227229832ce8742bea7d12e7750bb2 |
| SANs: disdex.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 secure
Validation of disdex.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| disdex.io. | DS published | 40872 | 13 | Verified |
| disdex.io. | Verified address RRset verified with the apex keys |
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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://disdex.io/mcp | Verified | 200 | |
| http (plaintext) | http://disdex.io/mcp | HTTPS enforced | 308 | https://disdex.io/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 →
check_invite Check a Discord invite ~99
Look up a Discord invite link or code (discord.gg/abc, discord.com/invite/abc, or just abc). Says whether disdex last saw it working (live), confirmed it dead, is still checking it (pending), or has never seen it (unknown), and which server it leads to, including dead invites, together with other working invites for that server when known.
| Name | Type | Req | Description |
|---|---|---|---|
| invite | string | yes | Invite URL or bare invite code. |
No output schema declared.
No examples provided.
get_server Get Discord server details ~68
Full details for one Discord server: description, member/online/boost counts, language, guild tag, Discord features, invite link, and how its member count changed over the last 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| server_id | string | yes | Discord server (guild) id, as returned by search_servers. |
No output schema declared.
No examples provided.
get_server_activity Get server member history ~78
Daily member and online counts for one Discord server over a time window, for questions like "is this server growing?" or "how big was it in March?". Values are daily averages of disdex's scans.
| Name | Type | Req | Description |
|---|---|---|---|
| range | string | – | – |
| server_id | string | yes | Discord server (guild) id, as returned by search_servers. |
No output schema declared.
No examples provided.
get_stats Get disdex index size ~33
How many Discord servers, users, bots, games and invites disdex has indexed, and when those totals were last refreshed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_servers Search Discord servers ~323
Search public Discord servers indexed by disdex. Matches words against the server name, vanity URL, description, profile traits and guild tag. With a query, results are ranked by relevance (servers named for the query first, then matches in traits and descriptions, with bigger and more active servers first among similar matches); without one, by member count. Each result has its member and online counts, language, and a joinable invite link when one is known. If no server matches every word of a longer query, results match all but one word and partial_match is true. NSFW servers are never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| growing_within_days | integer | – | Only servers whose member count was seen going up within this many days. A quick filter for active, growing communities. |
| language | string | – | Only servers whose name and description are in this language: an ISO 639-1 code such as en, es, de, pt, ru, ja. |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | Search words, at least 3 letters or digits (e.g. "minecraft survival", "study group"). Omit to browse everything by the chosen sort. |
| sort | string | – | Defaults to relevance with a query and members without one. members/online/boosts sort largest first; newest/oldest sort by when the server was created on Discord. |
| tag | string | – | Only servers with this Discord guild tag (the short tag members can show next to their name), case-insensitive exact match. |
No output schema declared.
No examples provided.
How do I install the disdex: Discord server search MCP server?
disdex: Discord server search is a hosted endpoint at https://disdex.io/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 · disdex.io
claude mcp add --transport http io-disdex-discord-servers 'https://disdex.io/mcp'
What is the disdex: Discord server search MCP server?
disdex: Discord server search is an MCP server listed in the public MCP registry as io.disdex/discord-servers. Find public Discord servers by topic, language and size, check invite links, see member growth. This page covers its hosted endpoint (https://disdex.io/mcp).
Is the disdex: Discord server search MCP server safe to use?
disdex: Discord server search scores 76 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 disdex: Discord server search MCP server expose?
disdex: Discord server search exposes 5 tools: search_servers, get_server, get_server_activity, check_invite, get_stats. Their descriptions and schemas cost roughly 601 tokens of context every time the server is loaded.
Does the disdex: Discord server search MCP server require authentication?
No. We connected to disdex: Discord server search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the disdex: Discord server search MCP server still maintained?
disdex: Discord server search is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the disdex: Discord server search MCP server?
VerifyMCP ran 13 checks on disdex: Discord server search, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.