Bahrain Payments (Tap Payments — Benefit)

app.wishpoolPublished by wishpool.appOfficial publisherv0.1.0Updated Oct 24, 2026

Bahrain payments for AI agents — Benefit via Tap Payments. Never holds funds.

The publisher's own server: Algeria Payments (Chargily Pay — EDAHABIA / CIB)

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant handle Bahrain payments through Tap Payments and the Benefit network, without the server holding funds.

What you can do
A remote MCP endpoint for Bahrain payments, described as covering Benefit via Tap Payments. The registry description states it never holds funds, so it appears to act as an interface to a payment provider rather than a custodian. No tools are listed in the manifest, so the exact operations it exposes are not documented here.
When to use it
Consider it when an assistant needs to work with Bahrain payment flows through Tap Payments and the Benefit network. Because the tool list is not published, verify the available operations before relying on it.
Requirements
Runs as a remote streamable HTTP endpoint at mcp-bh.wishpool.app; no package, environment variable, or header is declared. The manifest declares no authentication, but a payment service would normally require provider credentials, so confirm what is actually needed.
Before you install
This is a payments service, so actions may move money or create charges. The manifest declares no authentication and no credentials, which is unusual for payments and should be verified before use. Confirm what data is sent to Tap Payments and Benefit, and test with small amounts first.

Installation

In SourceWeft

  1. Open Bahrain Payments (Tap Payments — Benefit) 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/app.wishpool%2Fbahrain-payments-mcp/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": {
    "bahrain-payments-tap-payments-benefit": {
      "type": "http",
      "url": "https://mcp-bh.wishpool.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

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

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Wishpool integrations