io.github.dankezo/anti-rea-mcp
NPM · @DANNYPHAN190/ANTI-REA-MCP
antiRea advisory bot-abuse signals as stateful MCP sessions (evaluation and demos).
Available components
Last scanned (19 hours ago)
Scores higher than 44% of npm servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 26 +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.
- 12 Nov 26 +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.
- 10 Nov 26 +1
- Package version: 2.8.1 → 2.8.2 functional
- 9 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 2.8.0 → 2.8.1 functional
- 8 Nov 26 51
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@dannyphan190/anti-rea-mcp@2.8.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
close_signal Close a signal session ~32
Drops the session and its in-memory signal instance. State is not persisted anywhere.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | string | yes | – |
No output schema declared.
No examples provided.
create_signal Create a signal session ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| 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. |
No output schema declared.
No examples provided.
evaluate Evaluate a signal session ~136
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").
| Name | Type | Req | Description |
|---|---|---|---|
| args | object | – | Evaluate options forwarded verbatim, e.g. { cohortWindowMs: 86400000 } or { asOfTs: 1730000000000 }. |
| sessionId | string | yes | – |
No output schema declared.
No examples provided.
list_signals List antiRea signal kinds ~43
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
observe Feed one event into a signal session ~276
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| 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. |
No output schema declared.
No examples provided.
observe_reference Feed the reference stream (herd-tightness only) ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| identity | string | yes | – |
| sessionId | string | yes | – |
| ts | number | yes | – |
No output schema declared.
No examples provided.
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.
npm · @dannyphan190/anti-rea-mcp
claude mcp add dankezo-anti-rea-mcp -- npx -y @dannyphan190/anti-rea-mcp
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.