The Fincanva MCP server

Where is the MCP server, and which transport does it use?

The server is at https://app.fincanva.com/mcp. It speaks Streamable HTTP, stateless and with JSON responses: every request is a POST, and GET and DELETE answer HTTP 405, because there is no event stream to open and no session to end.

Which tools does the MCP server serve?

Each tool is one operation, named by its operation id, with the same input schema, the same result and the same error codes as its REST endpoint; the Reference documents each one. tools/list answers with the operations of the families your plan includes.

For each connected app, the user can switch families off in Fincanva's Settings, under Connected apps, or set the app to read-only: it is then given only the tools whose readOnlyHint is true, which read, analyse and simulate but create and change nothing in the library, and a call to any other answers toolset_disabled. A change reaches the app at its next tools/list.

What does a client receive when it connects?

At initialize the server answers with instructions: a briefing on what Fincanva is, what each listed family makes possible and how the tools combine, written for exactly the tools the client is given. A tool whose result may carry a chart points at the UI resource ui://fincanva/chart, which a client that renders MCP UI resources can show.

How does an MCP client authenticate?

With an OAuth 2.1 access token carrying the fincanva.research scope, found through the discovery documents in Authentication and API keys. An API key is refused on MCP with HTTP 401: a key works over REST only.