Methodology
What this catalog will and will not claim
Every decision-relevant fact here resolves to a source that was retrieved on a date, or it is recorded as unknown with a reason. There is no third state, and there is no ranking.
Three kinds of claim
- Observed fact O
- Something read directly from a source: an application ID that Discord returns, a permissions integer published on an application record, an invite that resolved. Set in the interface's sans and mono faces.
- Vendor claim V
- Something the app's own vendor says about itself, including through Discord. Capability coverage and pricing are mostly of this kind. Recorded and attributed, not verified.
- Editorial judgment E
- Ours: risk banding, summaries, comparison verdicts. Set in the serif face throughout the site, so you can tell which voice you are reading before you read it.
Where the facts come from
Identity, install parameters, privileged intents, policy URLs and verification state are read from Discord's own public application and App Directory endpoints. Discord's robots.txt explicitly allows those paths, which is why they are the only ones this project uses.
Public vendor pages may be read with a browser when a basic HTTP fetch does not work. If a retrievable source does not establish a field, it remains unknown with a reason. Discord requests are paced and respect retry instructions.
Servers are read the same way: Discord publishes a sitemap of discoverable servers and a crawler-facing page for each, and the invite endpoint answers with the counts and flags Discord shows on an invite preview. This catalog stores those readings with their dates, lists nothing Discord marks as age-restricted, holds no member data, and sends join clicks to discord.gg through its own click counter. Removal requests use the address below.
English-language server profiles across categories may also contain an editorial overview and reviewed project context. Overviews summarize the retrieved Discord description, About section and accepted project sources, with source links; the original Discord text remains in About. Audience, activities and access terms are taken from cited community or project introductions. A public invite alone does not establish free membership. Similar communities share a category and reviewed topics; these links do not imply affiliation. Documentation and GitHub links come from primary project sources. Community focus is our editorial reading of the Discord description and, when available, cited project sources. A blockchain named there is a community claim, with its role stated explicitly. External details come from primary project sources and carry their own links and retrieval dates. Before associating a project website, X or Telegram with a server, we check that an official project source links to an invite for that exact Discord server. Project founders are not described as owners of the Discord server. Missing evidence stays unknown, and a topic label or a social link is not an endorsement.
Commands come in two layers and the page keeps them apart. Discord's App Directory record names up to five most-used commands per app, with their options, default permission and the contexts they run in; those are observed facts, dated from the record. A vendor's own documentation may add the full list of names, each with one line of description: that list is read offline from one retrieved page whose address and hash are recorded, extracted by an agent that has no network access, and accepted only when every name and description is found verbatim in the page. It is shown as the vendor's claim, never as an observation, and nothing beyond a name and a line is copied.
Sources by type
- discord official290
- vendor official152
Field claims by kind
- editorial judgment145
- observed fact1185
- vendor claim195
The content gate
A page only enters the sitemap and drops its noindex tag when it has a verified canonical identity, a checked date, at least 3 decision-relevant comparable facts, a distinct recommendation, at least 2 internal alternatives, and provenance for every critical field.
Pages that fail stay online and say why at the top. Thin pages are a real risk in a catalog like this, and hiding the failure would be worse than showing it.
What this catalog does not do
- No ratings, reviews or star scores. None are collected, and none are emitted in structured data.
- No safety verdicts. An invite that resolves is an invite that resolves; risk is reported as unknown.
- No stored Discord member data: no member lists, usernames, member avatars, inviter identities or individual presence.
- No scraping around a block, no CAPTCHA bypass, no user-token automation, and no copied vendor descriptions.
- Outbound clicks are counted per day, per destination host. No IP, no user agent, no identifier.
A dated snapshot of published install permissions
2026-10-08 · permissions-2026-10-08-v1
Of 47 catalogued apps in this snapshot, 14 publish default install parameters that request Administrator, 16 publish a request without that bit, and 17 have an unknown permission request.
This is the catalog’s selected app set, not a representative sample of Discord apps. These are requested default installation permissions. They do not establish actual permissions in a server, minimum requirements, or safety.
We read Discord’s application record: install_params, or the server-install entry in integration_types_config when install_params is absent. Administrator is bit 3 (decimal 8). A missing permission value stays unknown and is excluded from “not requested”.
The fixed downloads contain each value, scopes, source URL, retrieval date and source hash. JSON also preserves the extracted primary field. For a known value, value & 8 determines the Administrator result; count the three states separately. Future catalog checks do not update this snapshot.
To cite this extract, use its dated link and version. DiscordCatalog supplies the normalization and counts; the linked Discord source content remains third-party material.
Source checks: 2026-10-08 00:28:48 to 2026-10-08 00:35:33 (UTC). Profile links lead to current records; the downloads preserve this dated snapshot.
Unknown means the retrieved record does not publish a usable default permission value. It does not mean no permissions are requested. Other authorization links and server settings may differ.
Corrections and takedowns
If a fact here is wrong or out of date, write to [email protected] with the page, the field and a source. Vendors correcting their own record should say so: those claims are stored as owner claims and labelled as such rather than silently replacing an observation.
Facts older than 90 days are flagged as stale on the page rather than removed. An old fact with a source is still more use than a fresh guess.