Atlas entry
disdex.io
5 capabilities over MCP. First atlas observation.
Surfaces
5 protocols checked
| ARD | Not found | No document retrieved |
|---|---|---|
| A2A | Not found | 0 skills |
| MCP | Valid | 2026-07-28 · 5 tools · resources not advertised · prompts not advertised |
| OpenAPI | Not detected | 0 operations |
| WebMCP | Not detected | 0 declarative form tools · experimental |
Exact states and meaning
- ARDabsent
Exact state: not found · No document retrieved
The supported discovery location returned no matching document.
Not found does not prove the service exposes no such interface elsewhere.
Not observed / not fetched
- A2Aabsent
Exact state: not found · 0 skills
The supported discovery location returned no matching document.
Not found does not prove the service exposes no such interface elsewhere.
Not observed / not fetched
- MCPobserved
Exact state: valid · Revision 2026-07-28 · 5 tools · resources not advertised · prompts not advertised
A usable protocol document was retrieved and validated.
Directly observed
- OpenAPIabsent
Exact state: not detected · 0 operations
No endpoint was established from the evidence and scope that InterfaceDelta inspected.
Not detected does not prove that no endpoint exists.
Not observed / not fetched
- WebMCPabsent
Exact state: not detected · 0 declarative form tools · experimental
No named declarative WebMCP form tools were observed in the origin root HTML.
Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.
Not observed / not fetched
Capabilities
5 · inventory complete
Summary of the AI readings · beta
The service lists 5 capabilities, and 5 have AI readings.
5 capabilities are read as read-only, including get_server, check_invite and search_servers.
Rows named: get_server · check_invite · search_servers
Written by code from the AI readings on this page: it groups them and says nothing they do not.
The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.
MCP tools 5
check_inviteinputs
invite(required)AI Reads only 0.80
get_serverinputs
server_id(required)AI Reads only 0.86
get_server_activityinputs
range,server_id(required)AI Reads only 0.90
get_statsAI Reads only 0.88
search_serversinputs
growing_within_days,language,limit,offsetand 3 moreAI Reads only 0.90
Not observed in this Passport: A2A skills, MCP resources, MCP prompts, OpenAPI operations.
Declared and observed
5 tools declare hints; the AI readings agree with all 5 that have a reading.
A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.
Atlas history
1 observation
- 5 capabilities · MCP 2026-07-28 · MCP endpoint validFirst observation
Fingerprint and versions
- Fingerprint
475028e2336f85f86b3b4ef70c5d9e5bb4b021469341341bcf15028ce318fac8- Passport schema
- 0.5.0, passport-semantic-v4
- Consistency
- MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable
Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.
About this entry
io.disdex/discord-serversListedOfficial MCP Registry · first listed 4 Nov 2026 · last listed 4 Nov 2026
Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal
Identity and snapshot
- Target key
sha256:de94becdb2ce3b03c081187b542144a149707878b109901e0c261f536ae2867e- Locator SHA-256
60a042cc2f326cf33b36dc2b76f28e66a00c5f1cc14f172a0d56fe2669c53eb1- Snapshot generated
- 4 Nov 2026, 00:59 UTC
The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.

