blia

MCP SUPPORT

Connected, but something is off? Start here.

Read this page after you read the MCP Guide, when something does not work as expected. Does the client not find the server? Does a value come back empty? Do you want to confirm the connection works? This page does not repeat the guide's tool reference. It covers what to do when a client hits a real problem.

CONNECT & VERIFY

Confirm it works

The same endpoint works for three common clients. If your client is not listed, point it at the URL below. Any client that uses streamable-HTTP MCP works the same way.

https://mcp.bliahub.com LIVE
  1. Add the server

    CONFIG — CLAUDE DESKTOP · claude_desktop_config.json

    {
      "mcpServers": {
        "blia-catalogue": {
          "url": "https://mcp.bliahub.com"
        }
      }
    }

    CONFIG — CLAUDE CODE · .mcp.json (project) or CLI

    claude mcp add --transport http blia-catalogue https://mcp.bliahub.com

    CONFIG — CURSOR · .cursor/mcp.json

    {
      "mcpServers": {
        "blia-catalogue": { "url": "https://mcp.bliahub.com" }
      }
    }
  2. Restart or reload the client

    Most clients read MCP config once, at startup. If you added the server while the app was open, restart the client, or use its "reload MCP servers" action, before the tools appear.

  3. Ask a question only the tool can answer

    "What's the monthly fee on BMO's everyday chequing account, and how is it waived?" A correct response names a real dollar figure and a waiver condition — not a guess, and not a refusal.

  4. Know what success looks like

    Your client lists five available tools: list_bank_products, get_product_terms, compare_products, list_offers and list_benefits. A query about BMO, Scotiabank, or CIBC chequing returns a sourced value or an explicit not_published — never silence, and never a made-up number.

TROUBLESHOOTING

The failure modes that actually happen

BLIA's MCP server is deliberately simple: no login, no key, five read-only tools. Almost everything that goes wrong traces back to one of these five things.

SYMPTOMLIKELY CAUSEFIX
Client does not reach the server, or times outWrong URL, or the client only supports local (stdio) servers, not remote onesConfirm the endpoint is exactly https://mcp.bliahub.com, with no trailing path. Confirm your client supports a remote, streamable-HTTP MCP server
Server connects, but no tools show upMost clients read MCP config once at startupRestart the client, or use its "reload MCP servers" action
get_product_terms returns not_publishedThis is a real answer, not an error. BLIA does not yet publish this attribute for this productTreat it as "not confirmed," never as "no fee." Call list_bank_products to see what is covered before you ask
Requests start failing after a burst of activityBLIA rate-limits the free tier by IP address: 600 requests per minute, 5,000 per daySlow down and retry after a short wait. The limit resets automatically. No key is available to raise it today
"Bank not found" or an empty product listCoverage today is BMO, Scotiabank, CIBC, RBC and TD chequing accounts — the full Big FiveCall list_bank_products first to see live scope. Check the roadmap for what is next
A returned value looks wrong or out of datePossible drift between the bank's current page and BLIA's dated snapshotVerify directly with the institution, then report it to office@bliahub.com so BLIA can review it

None of this requires a support ticket. If you are still stuck after you try the fix above, office@bliahub.com reaches a person, not a queue.

FAQ

Support questions, not product questions

For what the five tools do, and how BLIA plans to grow coverage, see the MCP Guide. This list is about getting connected and staying connected.

Do I need to sign up or get an API key?

No. BLIA rate-limits the free tier by IP address only. You need no account, no key, and no header to configure.

Which AI tools can I connect?

Any client that supports a remote, streamable-HTTP MCP server: Claude Desktop, Claude Code, Cursor, Windsurf, and others. If your client only supports local (stdio) servers, it cannot reach a hosted endpoint like this one yet.

Is anything about my query stored or linked to me?

BLIA does not store your IP address in its usage logs. The server issues a random session identifier per connection, and this identifier does not derive from anything about you. BLIA serves a client normally even if it never returns this identifier. See the Privacy Policy for the full detail.

What if the product or bank I need is not covered yet?

Coverage today is BMO, Scotiabank, CIBC, RBC and TD chequing accounts — the full Big Five. Call list_bank_products to see current scope, or check the roadmap on the overview page for what is next.

Can I run more than one MCP server alongside BLIA's?

Yes. BLIA's entry is one more line in your client's existing MCP configuration. It does not require exclusive access or conflict with other servers.

Where do I report a bug or a wrong term?

office@bliahub.com. Include the product and the tool call if you have it. That is usually enough to reproduce the issue.

STILL STUCK?

Write to a person, not a form

office@bliahub.com reaches BLIA directly. Include what you tried and what happened.