Dregs MCP server

Dregs MCP

Dregs scores a site's users for fraud and abuse: fake signups, bots, duplicate accounts, referral fraud, and account takeover, each explained by the observations behind the score. Its built-in Model Context Protocol (MCP) server lets AI agents like Claude, ChatGPT, Codex, Cursor, and VS Code investigate identities, review escalations, and tune rules in your Dregs account.

This repository is the public home for connecting to that server: setup snippets for each client, the Claude Code plugin, and the metadata behind Dregs's listings in MCP directories. The server itself is hosted by Dregs at https://dregs.com/mcp, and its source is not published here.

The maintained, full-length guide is the AI Agents chapter of the Dregs manual. This README is the short version.

The Dregs MCP endpoint

OAuth is the easiest way to connect. Clients that support MCP OAuth send you to Dregs to approve the connection in your browser. If you belong to more than one team, you choose the team on the approval page, and you can review or revoke connected agents under Settings → AI Agents in the Dregs dashboard.

MCP tokens are for clients that can't do OAuth, and for scripted agents. Create one in the Dregs dashboard under Settings → AI Agents, copy it right away (it's only shown once), and send it as Authorization: Bearer YOUR_TOKEN. A token acts as you within the team where you created it, so treat it like a password.

Connecting Claude Code to Dregs

The quickest way is the plugin from this repository, which adds the Dregs MCP server plus skills for integrating Dregs into your application and for working with the data afterwards:

/plugin marketplace add dregs-sdk/dregs-mcp
/plugin install dregs@dregs

Then run /mcp, pick dregs, and approve the OAuth connection in your browser. Ask Claude something like "Summarize my Dregs account" to confirm it can reach your team.

Without the plugin, add the server directly and Claude Code will walk you through OAuth:

claude mcp add --transport http dregs https://dregs.com/mcp

Or with an MCP token, for headless use:

claude mcp add --transport http dregs https://dregs.com/mcp --header "Authorization: Bearer YOUR_TOKEN"

The equivalent project-level .mcp.json:

{
  "mcpServers": {
    "dregs": {
      "type": "http",
      "url": "https://dregs.com/mcp"
    }
  }
}

Plugin skills

The plugin's skills are workflows, not tool schemas; each reads the relevant manual chapter through get_documentation before it acts, proposes changes for you to review, and confirms before anything is written.

Shortened. The full README is on GitHub.