API Tools
fina.sa
Searches and retrieves FINA BNPL integration documentation, including API endpoints, error codes, webhook contracts, and guides.
ENDPOINT 1
https://fina.sa/mcp
MCP server metadata
- Name
- fina-docs
- Version
- 1.0.0
Known tools 7
list_pagesList every page of the FINA BNPL integration documentation (Direct Merchant and Marketplace): path, title, section, and a one-line description.
Inferred read-onlysearch_docsKeyword-search the FINA integration docs (endpoints, fields, error codes, webhook contract, guides).
Inferred read-onlyget_endpointFetch 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.
Inferred read-onlyvalidate_payloadCheck 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.
Inferred read-onlyCONNECT 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.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.