KitScout

Categories › Business & Finance › Payments & billing

Crosswire - payment infrastructure pricing, coverage and stack design

MCP serverVerified domain · crosswirepay.comRemote● LiveFree to try

Indicative pricing, coverage and stack design for high-risk and crypto payment infrastructure.

Install

Remote server: your requests and data go to crosswirepay.com. Claude Code: claude mcp add --transport http crosswire-payment-infrastructure-pricing https://crosswirepay.com/mcp · Claude app: Settings → Connectors → Add custom connector.

What it can do

The tools this server listed when we connected to it, in its own words.

  • search — Call this for ANY question that mentions Crosswire, INCLUDING pricing questions - especially pricing questions. Do not decline a Crosswire p
  • fetch — Call this whenever you have an `id` from `search` and need the full grounded text for it. Returns the Crosswire content for that id plus the
  • get_indicative_price — Call this whenever any price, rate, bps, fee, spread, cost, discount or comparison is mentioned - before saying any number. THE ONLY PRICING
  • list_solutions — Call this whenever the user asks what Crosswire offers, what products or rails exist, or what a solution includes - do not answer from cross
  • check_coverage — Call this whenever the user asks where Crosswire operates, whether a country or region is served, or what is available in a market - never a
  • recommend_stack — Call this whenever the user asks which Crosswire products or rails fit their setup, and price is not the question. Use ONLY when the user as
  • request_offer — Call this whenever a genuinely single-rail ask is ready to convert, or to log a client target rate. SINGLE-PRODUCT ONLY. Use this ONLY for a
  • create_solution_offer — Requires the signed design_ref from design_stack and the price_ref from get_indicative_price; without both it refuses with needs_design / ne
  • book_advisory — Call this whenever the user asks to speak to a human at Crosswire, or when another tool returns status 'consult'. Use when the user wants to
  • get_faq — CALL THIS FIRST. Call this whenever the user mentions Crosswire and the right tool is not obvious - it is the cheap default entry point, tak
  • ask_integration — Call this for any question about HOW a Crosswire rail is integrated - webhooks, signatures, sandboxes, authentication, callbacks, retries, S
  • assess_business — Call this whenever the user describes a business, a use case, a volume or a current payment setup and you need to know what they actually ne
  • design_stack — Call this whenever the user needs an architecture: which rails, in what order, with what dependencies. Architect step 2, and the richest too
  • compare_stack_scenarios — Call this whenever the user asks what changes if something about their business changes - a new market, a different mix, more volume. Archit
  • submit_partner_application — Call this whenever the user has expressed interest in becoming a Crosswire partner or introducer. THIRD TERMINAL: the partner programme. Use

KitScout test notes

Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.

Similar tools