Mnemopay Sdk MCP Server

Production payment infrastructure for AI agents — real Stripe/Paystack/Lightning rails, autonomous shopping with escrow, Agent Credit Score

Remote serverstreamable-httpPython

What is the Mnemopay Sdk MCP server?

Mnemopay Sdk MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Production payment infrastructure for AI agents — real Stripe/Paystack/Lightning rails, autonomous shopping with escrow, Agent Credit Score (300-850), Ed25519 identity, behavioral finance, Merkle integrity, anomaly detection.

What you get

MnemoPay sits above the rail (Stripe, Paystack, Lightning, Stripe MPP, x402, Google AP2) and below the agent runtime (LangChain, CrewAI, Claude Agent SDK, your own loop). The rail moves money. The runtime decides. MnemoPay declares the rules, enforces the budget, and produces the evidence.

What the assistant can call

Once Mnemopay Sdk is connected, these are the calls the assistant has available:

  • first-success — returns the output of the first ok:true task; perfect for race patterns where any answer is fine
  • majority-vote — returns the most-common output across ok:true tasks; perfect for fact-extraction where consensus matters
  • merge-json — deep-merges every ok:true object output with sorted keys (deterministic across runs)
  • concat — joins string outputs with \n in spawn order
  • Sub — cent payments** via Lightning rail (impossible on Stripe/Paystack due to fees)
  • Per — tool metering** with agent.charge(amount, toolName) — two lines of code
  • Consolidation — auto-prunes weak memories, keeps what matters
  • Double — entry bookkeeping** — every debit has a credit, always balances to zero
  • Volume — tiered fees** — 1.9% / 1.5% / 1.0% based on cumulative volume
  • Cent — precise integer math** — stress-tested with 200,000 transactions across 50 concurrent agents, zero drift
  • Rail — What it is
  • Feature — MnemoPay

Configuration and credentials

You will need one environment variable: DATABASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Mnemopay Sdk's toolset — first-success, majority-vote, merge-json and 11 more — is a fair guide to whether it matches your workflow. It is maintained by mnemopay; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Mnemopay Sdk's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Mnemopay Sdk.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the mnemopay sdk mcp server does with a few real requests.

Available tools

ToolWhat it does
first-successreturns the output of the first ok:true task; perfect for race patterns where any answer is fine.
majority-votereturns the most-common output across ok:true tasks; perfect for fact-extraction where consensus matters.
merge-jsondeep-merges every ok:true object output with sorted keys (deterministic across runs).
concatjoins string outputs with \n in spawn order.
Subcent payments** via Lightning rail (impossible on Stripe/Paystack due to fees)
Pertool metering** with agent.charge(amount, toolName) — two lines of code
Consolidationauto-prunes weak memories, keeps what matters
Doubleentry bookkeeping** — every debit has a credit, always balances to zero
Volumetiered fees** — 1.9% / 1.5% / 1.0% based on cumulative volume
Centprecise integer math** — stress-tested with 200,000 transactions across 50 concurrent agents, zero drift
RailWhat it is
FeatureMnemoPay
Score**10/10**
ComponentWeight

How to install the Mnemopay Sdk MCP server

{
  "mcpServers": {
    "mnemopay-sdk": {
      "command": "npx",
      "args": ["-y", "@mnemopay/swarm"],
      "env": {
        "DATABASE_URL": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
DATABASE_URLEndpoint or connection string the server talks to.Yes

Example prompts to try

  • Use Mnemopay Sdk to first-success.
  • Use Mnemopay Sdk to majority-vote.
  • Use Mnemopay Sdk to merge-json.

Frequently asked questions

It connects Mnemopay Sdk to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (first-success, majority-vote, merge-json, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Mnemopay Sdk directly.