# io.github.ver-1000000/discord-rpc-mcp

Read Discord channels, follow new messages and control calls from your AI assistant.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.0
- **Author:** io.github.ver-1000000
- **License:** Unknown
- **Source:** https://github.com/ver-1000000/discord-rpc-mcp

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-05T01:57:04.043Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

3 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `setup` — Start Discord setup in a local browser page using the user's own Discord application. No secret arguments. Return the URL and Developer Portal instructions to t
- `setup_status` — Check setup progress and saved authorization without returning secrets or connecting to Discord. After completion, use get_guilds to verify connectivity.
- `get_events` — Read the bounded in-memory event buffer. Pass nextCursor as after on subsequent calls. Does not connect to Discord or fetch historical messages.

## Install

This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only.

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: read-only tool surface.
- Floor 3, ceiling 33 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.ver-1000000%2Fdiscord-rpc-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.ver-1000000%2Fdiscord-rpc-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.ver-1000000%2Fdiscord-rpc-mcp
- HTML page: https://forgeregistry.com/registry/io.github.ver-1000000%2Fdiscord-rpc-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.