Fisk MCP

Fisk MCP lets a compatible AI assistant find companies, inspect financial facts and retrieve source excerpts from Fisk. You sign in to your Fisk account and approve the connection.

The assistant supplies its own model. Fisk MCP retrieves research data and does not generate AI responses.

What you can ask

• “Find KCB’s listing and show its available net income figures.”
• “Find where this company discusses dividend payments, and cite the report pages.”
• “Which company events are confirmed, and which are only estimated?”
• “Open the source page behind this financial fact.”

Results depend on Fisk’s available coverage. Ask the assistant to preserve currencies, reporting periods and source links, and to distinguish missing information from zero.

Connect your assistant

1. Request pilot access with the name of your MCP client and its exact callback URL. Fisk registers and enables clients manually.
2. Ensure your Fisk account has active Pro access.
3. Add https://api.fisk.co.tz/mcp to your approved client as a remote Streamable HTTP server.
4. Use the client ID and OAuth configuration supplied during onboarding, with resource URI https://api.fisk.co.tz and scope openid. Dynamic client registration is disabled.
5. Sign in on Fisk, review the read-only permissions and approve access.
6. Ask your assistant to find a company. It can discover the eight available tools automatically.

The server URL alone is not sufficient to connect an arbitrary client. Client settings differ, and your client must support pre-registered OAuth credentials, remote Streamable HTTP, PKCE and resource indicators. Fisk has not certified every assistant or client; confirm compatibility during onboarding.

Permissions

The connector reads available company profiles, reviewed financial facts, processed documents, company events and available quotes.

It does not expose private notes, saved items, billing details, payment data or account credentials. It cannot place a trade, modify your account or create an alert.

Access is checked on every data operation. REST and MCP share the same account allowance; opening a second client does not create a separate quota.

Disconnect

Open Fisk → Settings → Connected apps, find the integration and revoke it. The gateway stops accepting data requests for that grant, even if its access token has not expired.

If a client asks you to reconnect after revocation, approve only if you intend to restore access.

Transport

Property	Value
Endpoint	https://api.fisk.co.tz/mcp
Transport	Stateless Streamable HTTP
Method	POST
Authentication	OAuth bearer token
Protocol discovery	Standard MCP initialization and tool discovery
Batching	One JSON-RPC message per request
Server-initiated streams	Not provided in this pilot

GET and DELETE requests to /mcp are not supported. Use an MCP client or the official protocol SDK rather than treating a tool invocation as an ordinary REST request.

See the tool reference and limits before building an automated workflow.