@dannyphan190/anti-rea-mcp

This is an MCP server - a Model Context Protocol (MCP) server for the antiRea library (@dannyphan190/anti-rea).

• Protocol: Model Context Protocol (MCP) - https://modelcontextprotocol.io

• Transport: stdio - the server reads JSON-RPC from stdin and writes to stdout; startup logs go to stderr

• Built with: the official @modelcontextprotocol/sdk for TypeScript

• Version: 2.8.0, wrapping @dannyphan190/anti-rea 2.8.0

• Exposes: 6 MCP tools - list_signals, create_signal, observe, observe_reference, evaluate, close_signal - that run antiRea's eight advisory signal kinds as stateful sessions

antiRea is a server-side TypeScript library that meters dataset access per identity and flags coordinated bot abuse - bulk extraction crews, scheduler-driven herds, seat squatting - for web apps and SaaS. This MCP server exposes the library's coordinated-cohort signal family - herd phase, herd tightness, seat occupancy, room guard, activity phase, vote brigading, room hopping and reconnect storms - as stateful sessions an MCP client can drive with tool calls. The library's core - per-identity dataset metering against bulk extraction and cloning - stays in-process by design and is not part of this server; only the signal family is exposed here, because signals are what an agent can exercise through tool calls.

It exists so an AI agent (or a developer driving one) can open a signal, feed it a synthetic or replayed event stream, and read the signal's verdict - for trying antiRea out, running the integration checklist shapes from the library's AGENT-GUIDE.md, and demoing what each signal does, without writing any host code first.

Run it

Requires Node.js >= 20.

Run it directly:

npx -y @dannyphan190/anti-rea-mcp

Or install globally:

npm install -g @dannyphan190/anti-rea-mcp
anti-rea-mcp

Client configuration

Standard mcpServers config for MCP clients (Claude Code, Cursor, and other stdio clients use this shape):

{
  "mcpServers": {
    "anti-rea": {
      "command": "npx",
      "args": ["-y", "@dannyphan190/anti-rea-mcp"]
    }
  }
}

Related MCP server: machine-mcp

Honest caveat - read this first

This wrapper is a registry-presence, evaluation and demo channel. It is not a production enforcement path.

antiRea's signals are designed to live inside the host application's process, fed by its real event streams (room joins, seat lifecycles, socket connect/disconnect hooks). Every signal output is advisory - each result carries enforcement: "none" - because antiRea measures and reports; the host application decides what to do. A signal session held in this MCP server's memory sees only what a tool caller feeds it, dies when the server process exits, and is separated from your serving path by an agent round-trip. Production integrations should import @dannyphan190/anti-rea in-process and follow its AGENT-GUIDE.md. The strongest legitimate reaction to any signal remains a step-up challenge for new actions, wired host-side through createVerificationGrace - never a ban, kick or block driven by this wrapper's output.

Tools

The eight kinds and their event shapes

ts is always a millisecond timestamp. Feed one homogeneous stream per session (joins OR chats OR retries - never mixed), and keep the lab-frozen default options unless you have your own measurements: thresholds in these modules were fixed before the lab ran.

A first session

1. list_signals - pick a kind.

2. create_signal { "kind": "herd-phase" } - keep the returned sessionId.

3. observe { "sessionId": "...", "identity": "acct-1", "ts": 1730000000000 } - repeat per event.

4. evaluate { "sessionId": "...", "args": { "cohortWindowMs": 86400000 } } - read the advisory result.

5. close_signal { "sessionId": "..." } when done.

Development

npm install
npm run build   # tsc -> dist/index.js
npm run smoke   # scripted JSON-RPC smoke test over stdio (scripts/smoke.mjs)
npm start       # node dist/index.js

The smoke test mirrors the library's own verification checklist: a synthetic shared-grid herd (12 identities x 12 events, 900 s grid, ~+/-30 s jitter) confirms in herd-phase and names exactly its members; a herd-tightness cohort fed against a spread reference scores tight; 16 fresh silent joins flag a 30-seat room in seat-occupancy after the 600 s sustain; missing capacity and use-after-close return clean tool errors.

Scope notes

• Sessions are in-memory only and unbounded in count; this is a deliberate thin-wrapper trade-off for evaluation use, not a serving component.

• seat-occupancy and room-guard sessions require options: { capacity } at create time - the wrapper forwards options verbatim and invents nothing on top of the published dist/index.d.ts surface.

• All lab numbers quoted by the library (and echoed in its result notice fields) are seeded-simulation numbers, not real-traffic performance.

License

MIT. The wrapped library @dannyphan190/anti-rea is also MIT.