← fina.sa

INDIVIDUAL MCP TOOL

list_pages

List every page of the FINA BNPL integration documentation (Direct Merchant and Marketplace): path, title, section, and a one-line description.

fina.sanone authenticationAvailability not checked

LIVE ENDPOINT

https://fina.sa/mcp

No auth detected

Connect to this endpoint to inspect the live schema for list_pages and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

fina.sa

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.fina-docs]
url = "https://fina.sa/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "fina-docs": {
      "type": "http",
      "url": "https://fina.sa/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: fina-docs
Remote MCP URL: https://fina.sa/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": {
    "fina-docs": {
      "url": "https://fina.sa/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "fina-docs": {
      "type": "http",
      "url": "https://fina.sa/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "fina-docs",
  "transport": "streamable-http",
  "url": "https://fina.sa/mcp"
}
MCP Inspector

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

Related tools

  • search_docs — Keyword-search the FINA integration docs (endpoints, fields, error codes, webhook contract, guides).
  • get_page — Fetch one documentation page as markdown by its path (e.g.
  • lookup_error — Explain a FINA numeric error code (the body's error_code, e.g.
  • get_endpoint — Fetch one API endpoint as structured JSON (method, path, request/response field trees with types, required flags, constraints and enum values, error codes, examples) — better than markdown when generating request-building code.
  • find_field — Look up a request/response field by (partial) name — e.g.
  • validate_payload — Check a JSON request body against an endpoint's spec BEFORE calling the API: missing required fields, unknown/misspelled fields, wrong types, invalid enum values, and the order-totals reconciliation rule behind error 400.