# io.github.dankezo/anti-rea-mcp (npm · @dannyphan190/anti-rea-mcp)

antiRea advisory bot-abuse signals as stateful MCP sessions (evaluation and demos).

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@dannyphan190/anti-rea-mcp`: 72/100 (this document), [markdown](https://verifymcp.io/servers/dankezo-anti-rea-mcp/dannyphan190-anti-rea-mcp.md), [page](https://verifymcp.io/servers/dankezo-anti-rea-mcp/dannyphan190-anti-rea-mcp)

## Channel facts

- Registry: `npm`
- Package: `@dannyphan190/anti-rea-mcp`
- Version: `2.8.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 11 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 792 tokens (~132/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 59% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "close_signal" implies "drop" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.dankezo/anti-rea-mcp server?

io.github.dankezo/anti-rea-mcp runs locally as an npm package, launched with npx -y @dannyphan190/anti-rea-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add dankezo-anti-rea-mcp -- npx -y @dannyphan190/anti-rea-mcp
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "dankezo-anti-rea-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@dannyphan190/anti-rea-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dankezo-anti-rea-mcp -- npx -y @dannyphan190/anti-rea-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dankezo-anti-rea-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@dannyphan190/anti-rea-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dankezo-anti-rea-mcp --command npx --arg -y --arg @dannyphan190/anti-rea-mcp
```

### Hermes

```yaml
mcp_servers:
  dankezo-anti-rea-mcp:
    command: "npx"
    args: ["-y", "@dannyphan190/anti-rea-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "dankezo-anti-rea-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@dannyphan190/anti-rea-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dankezo-anti-rea-mcp -t stdio -c npx -a -y @dannyphan190/anti-rea-mcp
```

### Other

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 67, +1)

- [functional] Package version: 2.8.1 → 2.8.2

### 2026-11-09 (score 66, +15)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 2.8.0 → 2.8.1

### 2026-11-08 (score 51)

First indexed and scored.

## MCP tools (6)

### `list_signals` (~43 tokens)

List antiRea signal kinds

Returns the 8 signal kinds this server can open sessions for, the library factory behind each, and the exact event shape observe() expects per kind. No session needed.

### `create_signal` (~159 tokens)

Create a signal session

Creates one antiRea signal instance (from @dannyphan190/anti-rea) and holds it in an in-memory session. kind is one of the 8 from list_signals. options are forwarded verbatim to the library factory - seat-occupancy and room-guard REQUIRE options { capacity: number }; for all other kinds options may be omitted (lab-frozen defaults - do not retune silently). Returns the sessionId to feed with observe.

Input parameters:

- `kind` (string, required)
- `options` (object): Factory options, forwarded verbatim (seat-occupancy and room-guard: { capacity } is required).
- `sessionId` (string): Caller-chosen session id. Omit to have the server generate one.

### `observe` (~276 tokens)

Feed one event into a signal session

Forwards one event to the session instance's observe(). Fill only the fields the session's kind uses (see list_signals): herd-phase / activity-phase / vote-brigading / herd-tightness use { identity, ts } (vote-brigading also takes accountCreatedTs); seat-occupancy and room-guard use { type, identity, ts, accountCreatedTs? }; room-hop uses { identity, room, ts }; reconnect-storm uses { source, kind, ts }. ts is a millisecond timestamp. Returns the library's observation object (e.g. { status, counted }). Feed ONE homogeneous stream per session.

Input parameters:

- `accountCreatedTs` (number): seat-occupancy / room-guard / vote-brigading: account creation time in ms, when known.
- `identity` (string): Authenticated identity (all kinds except reconnect-storm).
- `kind` (string): reconnect-storm only: socket event kind.
- `room` (string): room-hop only: the room joined.
- `sessionId` (string, required)
- `source` (string): reconnect-storm only: session/account key - never an IP address.
- `ts` (number): Millisecond timestamp of the event.
- `type` (string): seat-occupancy / room-guard only: the seat-lifecycle event type.

### `observe_reference` (~80 tokens)

Feed the reference stream (herd-tightness only)

Forwards { identity, ts } to a herd-tightness session's observeReference() - the established, known-legitimate population the cohort is standardised against. Only herd-tightness instances have this method in the library; other kinds return an error.

Input parameters:

- `identity` (string, required)
- `sessionId` (string, required)
- `ts` (number, required)

### `evaluate` (~136 tokens)

Evaluate a signal session

Runs the session instance's evaluate() and returns its JSON result verbatim. args are forwarded as the evaluate options object: { cohortWindowMs } for herd-phase / activity-phase (scoping is part of the law for room streams - use 86400000), { asOfTs } for the other kinds. Omit args to evaluate with defaults. Every result is advisory (enforcement: "none").

Input parameters:

- `args` (object): Evaluate options forwarded verbatim, e.g. { cohortWindowMs: 86400000 } or { asOfTs: 1730000000000 }.
- `sessionId` (string, required)

### `close_signal` (~32 tokens)

Close a signal session

Drops the session and its in-memory signal instance. State is not persisted anywhere.

Input parameters:

- `sessionId` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dankezo-anti-rea-mcp/dannyphan190-anti-rea-mcp#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70
- 2026-11-16: 70
- 2026-11-15: 69
- 2026-11-14: 69
- 2026-11-13: 68
- 2026-11-12: 68
- 2026-11-11: 67
- 2026-11-10: 67
- 2026-11-09: 66
- 2026-11-08: 51

## Common questions

### What is the io.github.dankezo/anti-rea-mcp server?

io.github.dankezo/anti-rea-mcp is listed in the public MCP registry as io.github.dankezo/anti-rea-mcp. antiRea advisory bot-abuse signals as stateful MCP sessions (evaluation and demos). This page covers its npm package (@dannyphan190/anti-rea-mcp).

### Is the io.github.dankezo/anti-rea-mcp server safe to use?

io.github.dankezo/anti-rea-mcp scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.dankezo/anti-rea-mcp server expose?

io.github.dankezo/anti-rea-mcp exposes 6 tools: list_signals, create_signal, observe, observe_reference, evaluate, close_signal. Their descriptions and schemas cost roughly 726 tokens of context every time the server is loaded.

### Is the io.github.dankezo/anti-rea-mcp server still maintained?

io.github.dankezo/anti-rea-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.dankezo/anti-rea-mcp server under?

io.github.dankezo/anti-rea-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.dankezo/anti-rea-mcp server?

VerifyMCP ran 16 checks on io.github.dankezo/anti-rea-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@dannyphan190/anti-rea-mcp
- Socket report: https://socket.dev/npm/package/@dannyphan190/anti-rea-mcp
- Repository: https://github.com/dankezo/antiRea
- Changelog RSS feed: https://verifymcp.io/servers/dankezo-anti-rea-mcp/dannyphan190-anti-rea-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/dankezo-anti-rea-mcp/dannyphan190-anti-rea-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dankezo-anti-rea-mcp/dannyphan190-anti-rea-mcp.json
- HTML version of this page: https://verifymcp.io/servers/dankezo-anti-rea-mcp/dannyphan190-anti-rea-mcp
