Skip to main content
Glama

Japan Payments (KOMOJU — konbini / cards / PayPay)

by app.wishpool
OverviewDiscussionsAdmin

Server Details

Japan payments for AI agents — konbini コンビニ, card, PayPay via KOMOJU. Stateless, never holds funds.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over 49 days
Last Tested
Transport
Streamable HTTP
URL
Server Listing
app.wishpool/japan-payments-mcp

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct action: creating a payment link, querying its status, and refunding a payment. There is no functional overlap or ambiguity between them.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (create_payment_link, query_payment_status, refund_payment), making them predictable and easy to understand.

Tool Count4/5

Three tools cover the core payment lifecycle (create, check, refund). While slightly minimal, it is appropriate for a focused payment link service without unnecessary complexity.

Completeness4/5

The set covers essential operations—create, query, refund—but lacks cancellation or listing capabilities. However, for a basic payment link flow, these gaps are minor.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Addedrefund_payment
  2. 2 tool updates
    • Changedcreate_payment_link1 field changed
      • addedInput schema / properties / provider
        Added value: +{
+  "description": "Which gateway. Omit to auto-select: PayPay when x-paypay-* headers are present, otherwise KOMOJU. payment_types applies to KOMOJU only.",
+  "enum": [
+    "komoju",
+    "paypay"
+  ],
+  "type": "string"
+}
    • Changedquery_payment_status1 field changed
      • addedInput schema / properties / provider
        Added value: +{
+  "description": "Omit to auto-select by credential headers.",
+  "enum": [
+    "komoju",
+    "paypay"
+  ],
+  "type": "string"
+}
  3. 2 tool updates
    • First observedcreate_payment_link
    • First observedquery_payment_status

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources