# RevRule by Payload (mcpb · revrule.mcpb)

RevRule by Payload: read entitlement graphs, review payout evidence, dry-run revenue events.

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

## Components

- mcpb · `revrule.mcpb`: 52/100 (this document), [markdown](https://verifymcp.io/servers/payload-tools-revrule-mcp/revrule.md), [page](https://verifymcp.io/servers/payload-tools-revrule-mcp/revrule)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Payloadhq/revrule-mcp/releases/download/v1.1.0/revrule.mcpb`
- Version: `1.1.0`
- Transport: `stdio`
- SHA-256: `37ba172465056c1b32297aef70a73f918260053d66d981f758c9d1d777afaa2b`

## 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-05.

- **Supply Chain Security**: 13/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - No install/post-install scripts declared.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 45/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 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 256 tokens (~85/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the RevRule by Payload MCP server?

RevRule by Payload ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 37ba172465056c1b32297aef70a73f918260053d66d981f758c9d1d777afaa2b; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Payloadhq/revrule-mcp/releases/download/v1.1.0/revrule.mcpb`
- SHA-256: `37ba172465056c1b32297aef70a73f918260053d66d981f758c9d1d777afaa2b`

### Verify on macOS / Linux

```bash
echo "37ba172465056c1b32297aef70a73f918260053d66d981f758c9d1d777afaa2b  revrule.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\revrule.mcpb).Hash -eq "37ba172465056c1b32297aef70a73f918260053d66d981f758c9d1d777afaa2b"
```

## 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-04 (score 52, +1)

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

### 2026-11-02 (score 51, +1)

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

### 2026-10-31 (score 50, +1)

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

### 2026-10-28 (score 49, +1)

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

### 2026-10-26 (score 48, +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-10-24 (score 47, +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-10-22 (score 46, +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-10-20 (score 45, +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.

## MCP tools (3)

### `revrule_get_graph` (~63 tokens)

Fetch one of your RevRule revenue entitlement graphs by id: its participants, rules, and ledger wiring. Read-only. (Rail route: GET /v1/graphs/{graph_id}.)

Input parameters:

- `graph_id` (string, required): The RevRule graph id.

### `revrule_list_payout_evidence` (~81 tokens)

List payout evidence recorded for a graph: verified payouts linked back to the original entitlement ledger entries (transaction hash, log index, block data, authorizing signature). Read-only. (Rail route: GET /v1/graphs/{graph_id}/payout-evidence.)

Input parameters:

- `graph_id` (string, required): The RevRule graph id.

### `revrule_simulate_event` (~112 tokens)

Dry-run a revenue event against a graph's rules and see what the rules would produce, with ZERO side effects: nothing is recorded, no payout is prepared or submitted. The event payload is wrapped in {event} for the existing rail REST API. (Rail route: POST /v1/graphs/{graph_id}/simulate.)

Input parameters:

- `event` (object, required): The revenue event payload to simulate, passed through to the rail as-is.
- `graph_id` (string, required): The RevRule graph id.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/payload-tools-revrule-mcp/revrule#diagnostics

## Score history

- 2026-11-05: 52
- 2026-11-04: 52
- 2026-11-03: 51
- 2026-11-02: 51
- 2026-11-01: 50
- 2026-10-31: 50
- 2026-10-30: 49
- 2026-10-29: 49
- 2026-10-28: 49
- 2026-10-27: 48
- 2026-10-26: 48
- 2026-10-25: 47
- 2026-10-24: 47
- 2026-10-23: 46
- 2026-10-22: 46
- 2026-10-21: 45
- 2026-10-20: 45
- 2026-10-19: 44
- 2026-10-18: 44
- 2026-10-17: 43
- 2026-10-16: 43
- 2026-10-15: 42
- 2026-10-14: 42
- 2026-10-13: 13

## Common questions

### What is the RevRule by Payload MCP server?

RevRule by Payload is an MCP server listed in the public MCP registry as io.github.payload-tools/revrule-mcp. RevRule by Payload: read entitlement graphs, review payout evidence, dry-run revenue events. This page covers its MCPB bundle (https://github.com/Payloadhq/revrule-mcp/releases/download/v1.1.0/revrule.mcpb).

### Is the RevRule by Payload MCP server safe to use?

RevRule by Payload scores 52 out of 100 on VerifyMCP. 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 RevRule by Payload MCP server expose?

RevRule by Payload exposes 3 tools: revrule_get_graph, revrule_list_payout_evidence, revrule_simulate_event. Their descriptions and schemas cost roughly 256 tokens of context every time the server is loaded.

### What licence is the RevRule by Payload MCP server under?

RevRule by Payload declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/Payloadhq/revrule-mcp
- Website: https://payloadhq.github.io/revrule.html
- Changelog RSS feed: https://verifymcp.io/servers/payload-tools-revrule-mcp/revrule.xml
- Changelog JSON feed: https://verifymcp.io/servers/payload-tools-revrule-mcp/revrule.json
- HTML version of this page: https://verifymcp.io/servers/payload-tools-revrule-mcp/revrule