Browserspendguard MCP

What browserspendguard-mcp does

The browserspendguard-mcp MCP server provides an MCP interface for AI browser purchase approval workflows. It is designed to assess proposed purchases, capture approval decisions, surface budget alerts, and produce purchase receipts for later review.

The hosted service focuses on purchase controls rather than browser automation itself. Its documented workflow includes spend thresholds, merchant evidence, risk notes, approval receipts, and audit records. This makes it relevant when an agent can initiate or recommend browser purchases and another system needs to evaluate or document those actions.

How it works

The service is available as a remote MCP endpoint at https://browserspendguard.clauxel.com/mcp. An MCP client sends JSON-RPC requests to that endpoint using Streamable HTTP. Production requests must include a bearer token in the Authorization header:

Authorization: Bearer <token>

The token is issued through the product website after choosing a plan and creating or requesting API access. The repository does not provide a local implementation of the production service; it serves as public documentation and a directory-submission reference.

Setup and configuration

To connect an agent:

1. Open the BrowserSpend Guard website and select a plan.
2. Create or request an API token.
3. Configure an MCP client that supports remote Streamable HTTP servers with the published endpoint.
4. Send JSON-RPC requests with the bearer token.

The README does not document local installation, package commands, configuration files, or environment variable names. It also does not identify a specific MCP client configuration format. Unauthenticated browser requests to the endpoint return a JSON error rather than internal service details.

Tools and capabilities

The documented tools are:

• evaluate_purchase — evaluates a proposed browser purchase.
• record_approval — records an approval decision.
• list_budget_alerts — retrieves budget-related alerts.
• export_purchase_receipt — exports a purchase receipt for audit or record-keeping.

The available material does not specify the request and response schemas for these tools. It also does not state whether evaluations automatically block purchases, whether alerts are pushed or polled, or which receipt formats are supported.

Limitations and notes

The browserspendguard-mcp MCP server is a paid hosted remote service, so use depends on an active plan and a product-issued bearer token. The supplied documentation does not describe a self-hosted option or expose the private production source code.

The repository names Streamable HTTP as the required remote transport, but it does not list specific compatible clients. Confirm that the client you choose supports remote Streamable HTTP MCP servers and bearer-token authentication before configuring it. The product page, pricing page, server card, and MCP endpoint are provided as the primary service links.