Skip to main content

paymid-mcp

The middleman gets paid first.

Commission protection for middlemen: the commission is paid first, then the seller is paid.

Paymid is a hosted MCP server that protects a middleman's commission on a deal. The buyer accepts a commission agreement (12-month non-circumvention) and pays the commission; only then does the payment to the seller open. Paymid sequences the two payments and keeps the proof record — it never processes or holds the money itself.

This package is a thin stdio bridge to the hosted server, for MCP clients that can only launch local commands. Clients that accept a remote URL directly should skip it and connect to https://mcp.paymid.com.br/mcp/claude (Streamable HTTP).

Install

{
  "mcpServers": {
    "paymid": {
      "command": "uvx",
      "args": ["paymid-mcp"]
    }
  }
}

Or with pip: pip install paymid-mcp, then run paymid-mcp. No API keys, no environment variables.

Authentication — what you will experience

The Paymid server uses OAuth 2.1 with dynamic client registration and requires an access token. Be precise about what this bridge does and doesn't do:

  • The bridge reaches the server and forwards your client's requests. Without a token, the server answers 401 Unauthorized and the bridge exits with an error — mcp-proxy does not run the interactive browser sign-in.

  • If you already have a Paymid access token, pass it through (arguments are forwarded to mcp-proxy):

    paymid-mcp -H Authorization "Bearer <your-token>"
    

    With a valid token, the full handshake completes and all 6 tools are available (validated live against the production server).

  • For the sign-in itself, use a client with native remote-MCP OAuth — or the npm bridge (npx -y paymid-mcp), which performs the full browser OAuth flow and caches the token. Clients that accept a remote URL directly don't need any shim: connect to https://mcp.paymid.com.br/mcp/claude.

Tools

Tool What it does
create_bridge Create a commission-protected bridge (optionally from an existing agreement's text — Paymid extracts the parties, values and does the math). Returns the payment link to send the buyer.
get_bridge_status Current status: commission paid? seller contact unlocked (blind mode)? service payment confirmed?
list_my_bridges Your bridges, with statuses and amounts.
get_bridge_link The payment link of an existing bridge, to resend to the buyer.
get_bridge_record The proof record: accepted agreement, timestamps, amounts, both payment receipts.
cancel_bridge Cancel a bridge.

Two modes: padrao (default — payment order enforced, parties may already know each other) and blind (the seller's contact stays sealed until the commission is confirmed — for deals where the seller's identity is the secret).

Rails are global and chosen by the middleman: Pix, Zelle, Wise, wire/SWIFT, ACH, SEPA, card, PayPal, Bitcoin, payment link, or a custom rail. Platform fee, owed by the middleman: 1.5% of the commission + 0.1% of the deal value.

License

MIT

Metadata

Release files for paymid-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for paymid-mcp 0.1.0
File Size Uploaded Provenance Actions
paymid_mcp-0.1.0.tar.gz 4.0 kB Without provenance Details for paymid_mcp-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for paymid-mcp 0.1.0
File Interpreter ABI Platform Actions
paymid_mcp-0.1.0-py3-none-any.whl Python 3 none any Details for paymid_mcp-0.1.0-py3-none-any.whl

Total release size: 8.8 kB

Release files / paymid_mcp-0.1.0.tar.gz

Download URL paymid_mcp-0.1.0.tar.gz
Size 4.0 kB
Tags Source
SHA-256 checksum
How to use checksums
173f648169a5577acb327bf4158f3ef6b788b6393cacc8682b0b1695b0efb963
BLAKE2b-256 checksum
How to use checksums
64c491c61bbd316d95ccd55e960f7c5d7290e2b162ddb55cea4cdd256989e291
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Release files / paymid_mcp-0.1.0-py3-none-any.whl

Download URL paymid_mcp-0.1.0-py3-none-any.whl
Size 4.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
342aef3532cac9871661a79772d4983f2483c9381b4411fef328c30d14c695f0
BLAKE2b-256 checksum
How to use checksums
05b9c85cdf1cc01864e4cf8e0dca55b8be850bbc7c39dca8132f6783d8eaf033
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.3

Security for paymid-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page