SCRIPTMASTERLABS — 402Proof

com.scriptmasterlabsPublished by scriptmasterlabs.comv1.0.3Updated Nov 5, 2026

Invoice/verify/score via RLUSD on XRPL. Own settlements proven end-to-end (SELF-PROOF).

The publisher's own server: Proof Holdings

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for creating, verifying and scoring invoices settled with RLUSD on the XRPL ledger, with self-proof of settlements.

What you can do
  • Create invoices that are settled in RLUSD on the XRPL.
  • Verify and score invoices and their settlements.
  • Prove its own settlements end-to-end (self-proof).
  • No individual tools are listed, so the exact operations are not documented in the supplied material.
When to use it
Consider it when an assistant needs to issue or check RLUSD-denominated invoices on XRPL and confirm that a settlement actually happened, for example in a payment or reconciliation workflow.
Requirements
A remote streamable HTTP endpoint; nothing to install locally. No authentication, environment variables or headers are declared, and no XRPL account or key setup is described.
Before you install
It deals with invoices and real-value settlement on XRPL, so treat any resulting payment or verification result as consequential. No authentication is declared, so anyone reaching the endpoint can call it. The tool list and documentation are absent, so what it writes, sends or shares with third parties cannot be confirmed.

Installation

In SourceWeft

  1. Open SCRIPTMASTERLABS — 402Proof in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.scriptmasterlabs%2F402proof/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "scriptmasterlabs-402proof": {
      "type": "http",
      "url": "https://four02proof.onrender.com/mcp?registry=scriptmasterlabs"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

3
  1. v1.0.3LatestNov 5, 2026
  2. v1.0.2Nov 3, 2026
  3. v1.0.0Nov 1, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Proof integrations