Dis Servers MCP Server
Provides access to the Dis Servers directory of game community Discord servers, including listings, source evidence, official links, and FAQ.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Dis Servers MCP ServerShow me the directory overview."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Dis Servers MCP Server
Official Game Discord Servers - Verified | Dis Servers
A Model Context Protocol server that exposes the canonical Dis Servers knowledge surface — directory listings, source evidence, and official links, FAQ, official links — to MCP-compatible AI clients such as Claude Desktop, Cursor, Windsurf, and Continue. Read-only, no API keys, no quota, ~50 ms cold start.
Official website: https://disservers.com
🗂️ About Dis Servers
Dis Servers is an evidence-first directory for game community Discord servers. A listing is intended to show a direct invite together with first-party source proof, platform details, the verification time, and an invite health check.
The site publishes static records and does not promise real-time invite availability, member counts, permanent uptime, or Discord endorsement. A community is not treated as official solely because an owner claims it; the decisive evidence is a link controlled by the game's publisher, developer, or another first-party source.
This MCP exposes the directory's verification rules and public entry points as read-only context. Use the live listing and its dated source evidence before joining a server, and re-check the official game site when the record is old.
Related MCP server: MCP Hub Database Server
Tools
get_directory_overview
Return the directory scope and source-verification rules the site publishes. (Dis Servers)
Input: no parameters. Returns: text/markdown.
get_official_links
Return the canonical list of official links for Dis Servers (website, support, docs when available).
Input: no parameters. Returns: text/markdown.
Resources
site://disservers/directory— Public directory scope, listing criteria, and source-verification boundaries.site://disservers/faq— Short FAQ generated from public site metadata.site://disservers/links— Canonical URLs to share with users.
Prompts
tell_me_about_disservers
Summarize what the site is, who it's for, and how it works. — Dis Servers
find_a_listing_disservers
Plan a directory search without treating a static snapshot as live status. — Dis Servers
Installation
Install via Smithery
npx -y @smithery/cli install disservers-mcp --client claude(Replace claude with cursor, windsurf, or continue for those clients.)
Install from source
git clone https://github.com/rocnubie/disservers-mcp.git
cd disservers-mcp
pnpm installThen add to your MCP client config (claude_desktop_config.json for Claude Desktop, mcp.json for Cursor / Windsurf / Continue):
{
"mcpServers": {
"disservers-mcp": {
"command": "node",
"args": [
"/absolute/path/to/disservers-mcp/src/index.mjs"
]
}
}
}Debug with MCP Inspector
npx @modelcontextprotocol/inspector node src/index.mjsOfficial Links
Website: https://disservers.com
Development
pnpm install
pnpm start # run the server over stdioLicense
MIT
Available Tools
2 toolsget_directory_overviewB
Return the directory scope and source-verification rules the site publishes. (Dis Servers)
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, and the description only says 'Return', implying a read operation. It does not disclose any behavioral details like cache freshness, authentication needs, or potential delays.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, but the parenthetical '(Dis Servers)' is ambiguous and may confuse. Every sentence should be clear and earn its place; this one partially succeeds.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, the description is minimal. It explains the resource type but leaves terms like 'directory scope' undefined. The sibling tool helps context slightly, but completeness is mediocre.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, and schema coverage is 100% (since none exist). The description adds no parameter info because none is needed. The baseline for zero-parameter tools is high.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns 'directory scope and source-verification rules', a specific resource. The sibling 'get_official_links' implies a different focus, distinguishing this tool's purpose effectively.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. The sibling tool name gives a hint, but explicit usage context is missing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_official_linksA
Return the canonical list of official links for Dis Servers (website, support, docs when available).
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must fully disclose behaviors. It only states the return purpose, but omits details like idempotency, permissions, or error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, no redundancy, front-loaded with purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Adequate for a simple list-returning tool, but lacks output schema or format details. Could be more complete for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so schema coverage is 100%. The description adds value by clarifying the tool's output, meeting baseline for zero-parameter tools.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool returns the canonical list of official links for Dis Servers, specifying types (website, support, docs). It distinguishes from the sibling 'get_directory_overview' by focusing on links.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool vs alternatives or when not to use it. The description only states what it does, without context or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
v0.1.0- First observed
get_directory_overview - First observed
get_official_links
TDQS
The two tools have completely distinct purposes: one provides directory scope and verification rules, the other provides official links. No overlap or ambiguity.
Both tools follow a consistent 'get_{noun}' pattern, making them predictable and easy to understand.
With only 2 tools, the server is minimal but appears well-scoped for its specific purpose of providing directory and link information. Slightly low, but reasonable for a narrow domain.
The tool set covers the core needs for the server's domain: directory overview and official links. Minor gaps like additional resources could exist, but the surface is complete for what it advertises.
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Curated, trust-first index of vetted MCP servers — scored tiers, monthly re-verified. Read-only.
Live read-only discovery for public s&box packages, servers, and player activity.
Read-only MCP server for The Quiet Protocol's engines, benchmarks, proof, and business data.
Search a nightly-refreshed directory of MCP servers by keyword, category or topic.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables discovery and search of available MCP servers through the official MCP Registry. Supports browsing servers with pagination and filtering to find the right MCP tools for your needs.1504MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables querying and searching the MCP Hub database to discover MCP servers, view server details, find top servers by popularity or recency, and identify top contributors.-
- FlicenseAqualityCmaintenanceRead-only MCP server for finding Discord messages. It enables searching guild messages, locating messages from jump URLs, and reading context around results.71-
- AlicenseBqualityDmaintenanceEnables MCP clients to interact with Discord servers, allowing operations such as sending messages and reading message history through the Discord API.23348MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rocnubie/disservers-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server