RevRule by Payload MCP server
RevRule by Payload: read entitlement graphs, review payout evidence, dry-run revenue events.
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed RevRule by Payload yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
RevRule by Payload tools
No tool declarations could be read from the package source. They show once the server is installed.
How RevRule by Payload compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 57% of 48,255 servers
Release history: 3 versions in the registry since 2026-10-13, latest 2026-10-16, typically one every 3 days.
Install RevRule by Payload in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the RevRule by Payload repository's README, as published. We do not edit it. Read it on GitHub
<!-- mcp-name: io.github.payload-tools/revrule-mcp -->
RevRule by Payload — MCP Server
An MCP server (stdio transport, Node.js standard library only, zero dependencies) that exposes RevRule, Payload's revenue-entitlement engine, to AI agents.
RevRule turns revenue sharing into declarative entitlement rules on the Payload rail: define who gets paid what, and every payout carries evidence linked back to the original entitlement ledger entry and its on-chain settlement. This server is a read + dry-run surface: there are deliberately no write/submit tools in v1. Every call goes to the live Payload rail (https://payload-rail.fly.dev) authenticated with your own rail API key (RevRule entitlement required).
Tools
Install
Via Smithery
Listed on Smithery as kyler-simmons-partners/revrule, or install the MCPB bundle from this repo (revrule.mcpb) in any MCPB-compatible client.
From source
git clone https://github.com/Payloadhq/revrule-mcp
cd revrule-mcp
node mcp/index.jsOr run it straight from GitHub with npx:
npx -y github:Payloadhq/revrule-mcpMCP client configuration (stdio):
{
"mcpServers": {
"revrule": {
"command": "node",
"args": ["/path/to/revrule-mcp/mcp/index.js"],
"env": {
"PAYLOAD_RAIL_API_KEY": "your-rail-api-key"
}
}
}
}Configuration
Fail-closed: with no API key configured, the server still starts and lists its tools, and every tool call returns a clear API key not configured error. The key never leaves your machine except as the Authorization header to the rail.
License
MIT — see LICENSE.
RevRule is a product of Payload, separate from Veyline (Payload's authorization layer) and from callx402 by Payload, the MCP client layer for x402-priced actions.
Nothing above is checked by us. What we check is on the safety report.
RevRule by Payload: common questions
- Is RevRule by Payload MCP server safe?
- Mostly: it is graded B (78/100). Read the RevRule by Payload safety report
- Does RevRule by Payload need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is RevRule by Payload maintained?
- The last commit was 22 days ago (2026-10-13). The latest release is v1.1.0.
- What can I use instead of RevRule by Payload?
- Servers from other publishers that do the same job: llmwiki MCP server and Trace MCP server.
Alternatives to RevRule by Payload
Same job from other publishers: the closest match first, then the best rated.
