Crosswire - payment infrastructure pricing, coverage and stack design
com.crosswirepay/crosswireIndicative pricing, coverage and stack design for high-risk and crypto payment infrastructure.
Score: 100/100
Handshake verified by our own probe.
Tools · 15
Call this for ANY question that mentions Crosswire, INCLUDING pricing questions - especially pricing questions. Do not decline a Crosswire pricing question without calling this first: the pricing resu…
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 domain tool that owns the subject. Do NOT browse crosswirep…
Call this whenever any price, rate, bps, fee, spread, cost, discount or comparison is mentioned - before saying any number. THE ONLY PRICING TOOL. No Crosswire rate, band or fee may be stated, estimat…
Call this whenever the user asks what Crosswire offers, what products or rails exist, or what a solution includes - do not answer from crosswirepay.com or prior knowledge. Use when the user asks what …
Call this whenever the user asks where Crosswire operates, whether a country or region is served, or what is available in a market - never answer coverage from the website or prior knowledge. Use when…
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 asks which Crosswire products/rails fit their setup - not pric…
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 genuinely single-rail ask - one product, no architecture de…
Requires the signed design_ref from design_stack and the price_ref from get_indicative_price; without both it refuses with needs_design / needs_price and names the next call. NEVER call this before a …
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 talk to a human at Crosswire - a 30-minute advisory call. R…
CALL THIS FIRST. Call this whenever the user mentions Crosswire and the right tool is not obvious - it is the cheap default entry point, takes no required input, and returns grounded answers plus a `r…
Call this for any question about HOW a Crosswire rail is integrated - webhooks, signatures, sandboxes, authentication, callbacks, retries, SDKs, API shape, testing, go-live steps. Every answer is read…
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 need - the first substantive tool of the journey. Architect st…
Call this whenever the user needs an architecture: which rails, in what order, with what dependencies. Architect step 2, and the richest tool on this server. Takes the same business profile as assess_…
Call this whenever the user asks what changes if something about their business changes - a new market, a different mix, more volume. Architect step 3. Takes a base business profile plus up to four la…
Call this whenever the user has expressed interest in becoming a Crosswire partner or introducer. THIRD TERMINAL: the partner programme. Use ONLY after the client has responded with interest in the pa…
How to use
Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://crosswirepay.com/mcp
Cursor or Cline: add to your MCP config:
{
"mcpServers": {
"crosswire_-_payment_infrastructure_pricing,_coverage_and_stack_design": {
"url": "https://crosswirepay.com/mcp",
"transport": "streamable-http"
}
}
}