Hosted MCP server/Finance Official

Official Fiscal.ai MCP server

Hosted at api.fiscal.ai·SSE

Fiscal.ai provides clean public-equity fundamental data for financial research. Its connector gives assistants structured company and market context for analysis, comparison, and investment-oriented questions. Connect over Streamable HTTP at https://api.fiscal.ai/mcp with OAuth, or send an API key as Authorization: Bearer. Both paths map to the same account, plan, and entitlements. The /mcp/sse endpoint is a legacy SSE fallback for older clients, and VS Code needs a servers entry with type http and the /mcp URL.

api.fiscal.ai SSE OAuth or API key (Bearer) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Financial researchers and analysts using Fiscal.ai for public-equity fundamentals and market context.

  • Analyze company fundamentals using structured market context.
  • Compare public-equity data across companies and markets.
  • Connect Codex or a script with a Bearer API key.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses SSE.

All client guides
  1. 01

    Run this command in your terminal

    This adds Fiscal.ai as a remote SSE server in Claude Code.

    Claude Code
    claude mcp add --transport sse fiscal-ai https://api.fiscal.ai/mcp --header "Authorization: Bearer <FISCAL_API_KEY>" --scope project
  2. 02

    Send the credential

    The provider expects the following header. Replace each placeholder with your own key or token before you connect.

    Required headers
    Authorization: Bearer <FISCAL_API_KEY>
  3. 03

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://api.fiscal.ai/mcp
Host
api.fiscal.ai · /mcp
Transport
SSE
Authentication
OAuth or API key (Bearer)
Server name
fiscal-ai
Listing type
Official provider listing

The installer uses the server name fiscal-ai. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that fiscal-ai appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Analyze company fundamentals using structured market context. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client only supports Streamable HTTP. Use a client that supports SSE or the provider's HTTP endpoint.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Fiscal.ai documentationhttps://docs.fiscal.ai/docs/guides/mcp-integration