Agent Purchase Verification

io.github.RFrost19Published by GitHub account RFrost19v1.0.0Updated Oct 24, 2026

Check if an ecommerce purchase meets buyer rules before payment. Returns PASS, FAIL, or REVIEW.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint that checks whether an ecommerce purchase meets buyer rules before payment, returning PASS, FAIL or REVIEW.

What you can do
Evaluate a proposed ecommerce purchase against buyer rules before payment is made, and return a verdict of PASS, FAIL or REVIEW. The manifest lists no individual tools, so the exact inputs and outputs are not documented in the supplied material.
When to use it
Useful when an assistant is helping with online shopping and you want a rule-based check on a purchase before committing to payment, for example to flag orders that should be blocked or reviewed by a person.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared, and no authentication is declared. Network access to the hosted endpoint is required.
Before you install
The server is hosted by a third party, so purchase details submitted for checking leave your machine. No authentication is declared, so anyone with the endpoint can call it. It only returns a verdict; it does not appear to make payments itself, but confirm what data it receives before sending order details.

Installation

In SourceWeft

  1. Open Agent Purchase Verification 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/io.github.RFrost19%2Fagent-purchase-verification/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": {
    "agent-purchase-verification": {
      "type": "http",
      "url": "https://web-production-855eb4.up.railway.app/mcp/"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 24, 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.