Micropay Test Suite vs Wraps

A side-by-side look at the Micropay Test Suite and Wraps MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

M
Micropay Test SuiteCloud Platforms
Verify your agent's x402 payment flow for free on Base Sepolia testnet before real money moves.37FairAuth: not declared
Wraps logoWrapsCloud Platforms · Local subprocess (stdio)Search the Wraps docs and estimate AWS SES costs. Public, read-only, no authentication.49FairAuth: not declared

Verdict: choose Micropay Test Suite for cloud platforms work; choose Wraps for cloud platforms as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

M
Choose Micropay Test Suite when

  • You need dedicated capabilities in the Cloud Platforms domain.
Explore Micropay Test Suite

Wraps logoChoose Wraps when

  • You need dedicated capabilities in the Cloud Platforms domain.
  • You prefer a local stdio subprocess transport.
Explore Wraps

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
M
Micropay Test Suite
Wraps logoWraps
CategoryCloud PlatformsCloud Platforms
Quality signal37/100 · Fair49/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—64
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Micropay Test Suite tools

No tool names declared yet. Check the project README from the listing page.

Wraps tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Micropay Test Suite

No confirmed install command for Micropay Test Suite yet — follow the setup steps linked from its listing page rather than a guessed package name.

Wraps

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "wraps": {
      "command": "npx",
      "args": [
        "-y",
        "@wraps.dev/cli"
      ]
    }
  }
}

Frequently asked questions

Micropay Test Suite is categorized under Cloud Platforms and uses an install path we have not confirmed yet. Wraps belongs to Cloud Platforms and uses a local stdio subprocess. Pick Micropay Test Suite for cloud platforms work and Wraps for cloud platforms.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Micropay Test Suite has no confirmed install command yet — follow its own setup instructions.

Micropay Test Suite has no declared pricing — check the project's own site. Wraps has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add micropay-test-suite and wraps as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Micropay Test Suite has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Wraps has 49/100 (Fair) with 1 views, 0 installs and 64 GitHub stars.