Regent Protocol

org.regentprotocolPublished by regentprotocol.orgOfficial publisherv1.0.0Updated Oct 26, 2026

Spending control for AI agents: approved budgets, a decision before each payment, signed receipts.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint that gives AI agents spending controls: approved budgets, a decision before each payment, and signed receipts.

What you can do
  • The listing names no individual tools, so capabilities come from the description only.
  • It is meant to let an assistant work within approved budgets when it spends money.
  • It provides a decision step before each payment is made.
  • It produces signed receipts for payments, giving an auditable record.
When to use it
Worth considering when an assistant is allowed to make payments or spend money and you want budgets, a pre-payment check and a receipt trail around that spending.
Requirements
A remote streamable HTTP endpoint at the provider's gateway; no local package, environment variables or headers are declared. The manifest declares no authentication, so how access is granted is not stated.
Before you install
It is about payments and spending, so an assistant connected to it may move money; the listing gives no detail on limits, custody or what data is sent to the provider. No authentication is declared, so verify how the endpoint is secured before connecting.

Installation

In SourceWeft

  1. Open Regent Protocol 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/org.regentprotocol%2Fcloud-gateway/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": {
    "regent-protocol": {
      "type": "http",
      "url": "https://gw.regentprotocol.org/gw/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestOct 19, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • 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.