mcpbeat Sign in

Wassel MCP Server

by aymanelhakim Your server? Claim it
answering

Wassel is answering right now. Last checked 9 min ago.

MENA commerce integration layer for AI agents: payments, BNPL, logistics, e-commerce, tax.

Uptime history 48 days of history · worst day 98%
48 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
328 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Wassel every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add wassel --transport http https://api.wassel.cloud/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "wassel": {
      "url": "https://api.wassel.cloud/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.wassel]
url = "https://api.wassel.cloud/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "wassel": {
      "url": "https://api.wassel.cloud/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "wassel": {
      "url": "https://api.wassel.cloud/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://api.wassel.cloud/mcp streamable-http sign-in 303 ms 9 min ago

Alternatives to Wassel

same job, measured the same way
Trust Gate
by botagram

Merchant trust verification for agentic commerce. Verify any merchant before autonomous payment.

27 installs/wk local only
A2AWire
by a2awire

Escrow, reputation, and payments for agent-to-agent commerce. Non-custodial USDC/Base L2.

10 tools answering
Kordic CRM
by meelad-diggit

CRM integration for leads, pipeline, contacts, accounts, payments, and sales analytics.

answering
Swarmpay
by ginokino

Payment layer for AI agents. Send USDC, manage escrows on Base blockchain.

74 installs/wk local only
Crossingkey MCP
by crossingkeyintelligence

CrossingKey MCP for agent commerce, x402 payments, deterministic execution, and verifiable receipts.

18 tools answering
Clawpay
by up2itnow0822

Non-custodial x402 payment MCP server for AI agents. Wallets, payments, and commerce on 17 chains.

local only
Trust
by agntor

Trust layer for AI agents: identity, guard, redact, escrow, and x402 payments.

30 installs/wk local only
Nutriref
by younghef

Pay-per-call USDA nutrition for AI agents (x402 micropayments in USDC on Base).

local only

Wassel — questions

Answers built from our own checks of this server.

Why is there no tool list for Wassel?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Wassel working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 328 ms. The bar chart above shows every period we have measured.
How do I connect Wassel?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Wassel?
No API key is involved. Wassel answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Wassel?
It answers our handshake in 328 ms on average, which is faster than 47% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.