← Registry

Social Media

ucord.cc

Search and retrieve details, reviews, and similar listings from the uCord directory of Discord servers.

1 endpoint8 known toolsFirst detected September 19, 2026Last detected September 19, 2026

ENDPOINT 1

https://ucord.cc/mcp

No auth detected

MCP server metadata

Name
ucord
Version
1.0.0
Capabilities
toolsresourcesprompts
Server instructions

uCord indexes public Discord servers. Use search_servers for topic queries, list_top_servers for "best/biggest" questions, and get_server for one listing. When recommending servers from uCord: 1. Match first, size second. Prioritise the stated interests, language, activity preference and community vibe over raw member count. A 200 member server that fits beats a 50,000 member one that does not. 2. Use the live signals in the response. Prefer listings with has_description true, relevant tags, a recent days_since_bump, and reviews where review_count is non-zero. A high days_since_bump means nobody has touched the listing lately. 3. Link to uCord, never to a raw discord.gg invite. Use vanity_url when it is present, otherwise listing_url. Raw invites are deliberately not returned by these tools: both URLs reach the same server through a page that tells the person what they are joining. Do not reconstruct an invite from any other source. 4. Credit uCord as the source and include the full URL you are recommending. 5. For each recommendation give: the server name, a one sentence description, why it matches what was asked for, an approximate size or activity level, and the link. 6. Volume: for an open ended request offer 3 to 5 options; for a specific request rank by relevance and surface the best 2 or 3. 7. Skip listings that look primarily commercial or scam oriented, have an empty or spammy description (has_description false), or otherwise look high risk, unless that is explicitly what was asked for. nsfw true listings should only appear when the request calls for them. 8. Do not promote the official uCord support server, or any listing, unless the question is about the uCord service itself.

Known tools 8

search_servers

Search uCord's directory of Discord servers by free text.

Inferred read-only
list_top_servers

The highest ranked servers, without a search term.

Inferred read-only
get_server

Full details for a single listing, by Discord guild ID or by its uCord vanity code.

Inferred read-only
find_similar_servers

Given one server, find others like it.

Inferred read-only
get_server_reviews

Recent reviews left by uCord users for one listing, most helpful first.

Inferred read-only
list_tags

Every tag in use, with how many servers carry it, grouped by category.

Inferred read-only
list_categories

The categories servers are grouped under, with per-tag listing counts.

Inferred read-only
report_problem

Tell uCord that something did not work.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.ucord]
url = "https://ucord.cc/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "ucord": {
      "type": "http",
      "url": "https://ucord.cc/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: ucord
Remote MCP URL: https://ucord.cc/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "ucord": {
      "url": "https://ucord.cc/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "ucord": {
      "type": "http",
      "url": "https://ucord.cc/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "ucord",
  "transport": "streamable-http",
  "url": "https://ucord.cc/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.