API Tools

delopay.net

Provides search and retrieval tools for DeloPay's payment API, SDK, WordPress plugin, and dashboard documentation.

1 endpoint3 known toolsFirst detected October 4, 2026Last detected October 4, 2026

ENDPOINT 1

https://delopay.net/mcp

No auth detected

MCP server metadata

Name: delopay-docs
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

DeloPay is a payment orchestrator: integrate once, connect your own processor accounts (Stripe, PayPal, Airwallex and others), and DeloPay routes each payment to one of them, with the same reporting, refunds, disputes and webhooks for every processor. Use search_docs to find where a topic is covered, then get_page to read the whole page before you answer. list_pages shows every page. Cite the page URLs you used. Foundations every integration relies on: - Base URL: `https://api.delopay.net`, for test and live payments alike. - Authentication: a secret key in the `api-key` header, on your server only. Publishable keys work in the browser for one payment's customer-side steps, with that payment's client secret. - Test payments: `test_mode: true` when creating a payment runs it against your processor's sandbox credentials. - Amounts: integers in minor units (`5000` is 50.00 USD). - Errors: `{ "error": { "type", "code", "message" } }`. - Idempotency: send an `Idempotency-Key` header on POST requests so a retry cannot repeat them. - Webhooks: signed with HMAC-SHA512 over the raw body; the signature is in `x-webhook-signature-512`. - SDKs: TypeScript (`@delopay/sdk`), Java (`net.delopay`) and Rust (`delopay`); every method maps to one HTTP call.

Known tools 3

search_docs

Ranked search over the DeloPay documentation (Payment API, SDKs, WordPress plugins, Dashboard).

Potential side effects

get_page

One page of the DeloPay documentation as Markdown, with absolute links.

Inferred read-only

list_pages

Every page of the DeloPay documentation, in sidebar order, with its slug and what it covers.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.delopay-docs]
url = "https://delopay.net/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "delopay-docs": {
      "type": "http",
      "url": "https://delopay.net/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: delopay-docs
Remote MCP URL: https://delopay.net/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "delopay-docs": {
      "url": "https://delopay.net/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "delopay-docs": {
      "type": "http",
      "url": "https://delopay.net/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "delopay-docs",
  "transport": "streamable-http",
  "url": "https://delopay.net/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.