What payment methods are supported?
The server uses Tap Payments’s hosted checkout, so it supports whatever methods are enabled on your Tap account — typically cards and Apple Pay.
@junter1989k-ai
基本情報
概要はまだありません
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"jordan-payments": {
"type": "http",
"url": "https://mcp-jo.wishpool.app/mcp"
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。
A remote MCP server that lets AI agents (Claude, ChatGPT, Cursor, etc.) accept payments in Jordan via Tap Payments’s hosted checkout. It acts as a stateless translation layer between the AI agent and Tap Payments — funds flow directly from buyer to merchant, and no credentials or transaction data are stored.
Configure your MCP client with the endpoint https://mcp-jo.wishpool.app/mcp and add the HTTP header x-tap-secret-key with your Tap Payments secret key (free test keys from businesses.tap.company). Then invoke the create_payment_link tool to generate a JOD hosted-checkout link, or use query_payment_status to check whether a payment has been completed.
create_payment_link and query_payment_status.The server uses Tap Payments’s hosted checkout, so it supports whatever methods are enabled on your Tap account — typically cards and Apple Pay.
No. This is a stateless translation layer. Funds flow directly from the buyer to Tap Payments to the merchant; the server never touches or stores any credentials or money.
Node.js version 18 or higher is needed. There are zero runtime dependencies, and the server is licensed under MIT.
Sign up at `businesses.tap.company` to get free test keys (`sk_test_...`) for development. Production keys (`sk_live_...`) are available after going live.
Two tools: `create_payment_link` (generates a JOD hosted‑checkout link) and `query_payment_status` (checks if a payment has been marked as paid).
Open-source Node.js FHIR MCP server with SMART Backend Services, metadata-aware search/CRUD tools, compact responses, FHIRPath filtering, safe pagination, audit events, and terminology lookup.

Agent-Native Terminal

Session replay, built for agents. Subtext is agentic session review: it captures production sessions of your app and connects them to your coding agent — Claude Code, Cursor, Codex, Devin, your own harness — so it can

AI agents start every session with amnesia — you re-explain the project, repeat your preferences, and correct the same mistakes over and over. PLUR gives them a memory that persists. Your agent's corrections, preference

Serve your docs to AI agents over SSH and MCP. Agents use ls, cat, grep, find, and pipes against a virtual filesystem backed by your documentation. Identity-scoped access, governed writing with human approval, and portab
コメント