FinHubDeveloper Portal

Integrate IHS Loan Applications

The FinSys loan-application platform exposes a direct REST API for lender and borrower engineering teams — distinct from the finsys_* MCP tools. Build a native integration for:

• IHS (Income History Statement) loan-application submission
• Document upload & download
• Consent management
• Webhooks & status polling

Authenticate with a clientId + clientSecret API key issued from the FinHub portal, exchange it for a JWT, then call the API directly.

Request API Access

Ready to integrate? Reach out to the FinHero team to provision API credentials for your lender or borrower platform.

Request API access →

FinHub MCP Server

FinHub exposes a single MCP server at POST /api/v1/mcp over Streamable HTTP (JSON-RPC 2.0). This is the sole MCP surface — the finsys-api MCP endpoints are retired.

Tool families: billing/forms • e-mandate • finsys (loan applications)

Auth: OAuth 2.1 + PKCE, scope mcp:tools

Register client: POST /oauth/register (RFC 7591 dynamic registration)

Discovery: /.well-known/mcp.json

FinSys tools require an explicit environment: "staging" | "production" parameter and a configured service key on this deployment. Tool visibility follows the user's FinHub permissions.

Claude Desktop / Cursor

Add this to your MCP client configuration. OAuth login will open in your browser automatically.

          {
  "mcpServers": {
    "finhub": {
      "url": "https://finhub.finhero.asia/api/v1/mcp"
    }
  }
}
        

Claude Code

Add to your ~/.claude.jsonor project .mcp.json:

          {
  "mcpServers": {
    "finhub": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "mcp-remote",
        "https://finhub.finhero.asia/api/v1/mcp"]
    }
  }
}
        

MCP Authentication

MCP clients use OAuth 2.1 Authorization Code + PKCE. When you connect, your MCP client opens a browser where you log in with your FinHub credentials. Tokens refresh automatically.

Access tokens: 8 hours • Refresh tokens: 30 days

REST API Authentication

For direct REST API access, POST to /api/v1/loginwith your email and password to get a JWT bearer token (24h expiry).

          curl -X POST /api/v1/login \
  -H "Content-Type: application/json" \
  -d '{"email":"...","password":"..."}'