Fiscal.ai
by Fiscal.ai
Pull public-company financials, filings, ratios and ownership into your AI assistant. Two tools — an API reference and a code executor — front 48 documented endpoints. The sandbox is network-isolated with a 30-second budget, and the vendor publishes the schemas that say so.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Fiscal.ai via MCP
https://api.fiscal.ai/mcp/sseWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Fiscal.ai Tools & Capabilities (2)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The connector's containment story is not on the page Anthropic links. Fiscal.ai's MCP guide never names
api_docsorexecute_code. Everything we know about the sandbox comes from a tool-schema manifest published for Microsoft Copilot. A reader who follows the documentation link alone learns that a code executor exists only by inference. - "Network-isolated" is documented, not verified by us. Testing it would mean authenticating and executing code, which we do not do. It is a specific, credible claim — and still a claim.
- The sandbox is otherwise undescribed. No provider named, no memory ceiling, no statement of whether the runtime is per-session or shared, and no account of how the credential reaches it.
- Fiscal.ai asks for no confirmation prompt. Its Microsoft manifest annotates both tools
isNonConsequentialwithconfirmationtypeNone. Defensible for read-only tools; worth knowing before an agent runs generated JavaScript unattended. - The directory endpoint is the legacy one. Anthropic's snapshot carries
/mcp/sse; Fiscal.ai documents/mcpover streamable HTTP as current. Both answer, but register the newer one — Fiscal.ai notes Copilot Studio no longer supports SSE. This page's frontmatter mirrors the directory record, so it carries the/sseURL; the prose and the connect instructions use the current one. - We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no live schemas and no
readOnlyHintordestructiveHintannotations were readable. Every tool description here is Fiscal.ai's own, taken from the manifests it publishes unauthenticated. - Entitlement, not the tool list, decides what you can reach. Fiscal.ai states plainly that seeing a tool does not mean your plan has access. A free key is capped at 250 requests a day, 50 a minute, and 100 named companies.
- CUSIP and ISIN lookups need a licence you hold separately. Fiscal.ai documents the requirement and returns a 403 naming it. Company key, its own
fsclidentifier and FIGI carry no such gate. - We could not read Fiscal.ai's terms of service or privacy policy. Both URLs sit behind a Vercel bot challenge returning HTTP 429 to a non-browser client, with and without a browser user agent. On redistribution rights beyond the identifier licence, read them yourself.
- Ownership data is US-only, built from SEC Form 4 and 13F filings, and Fiscal.ai states it carries no market-share data at all.
- Prompts are unconfirmed. Anthropic's snapshot lists none, and the gated endpoint blocked our own check.
Frequently asked questions
Where does Fiscal.ai's execute_code tool actually run the code?
In a sandbox on Fiscal.ai's own servers, never on your machine. The tool schema Fiscal.ai publishes describes a network-isolated sandbox with a 30-second budget, and says code must arrive as a single async arrow function. Nothing is installed locally and no code touches infrastructure you administer. Fiscal.ai does not name the sandbox technology.
Can the Fiscal.ai MCP connector reach anything other than Fiscal.ai data?
Fiscal.ai states it cannot. Its published tool schema calls the sandbox network-isolated, so generated JavaScript reaches Fiscal.ai's own helper functions rather than the open internet. That is a containment claim we could not test without authenticating and executing code, which this catalogue does not do. Treat it as documented design, not verified behaviour.
How big is the API behind Fiscal.ai's api_docs tool?
Fiscal.ai's API reference documents 48 GET endpoints across roughly seventeen groups, counted on 2026-08-19. They cover company profiles, as-reported and standardized statements, ratios, segments and KPIs, ownership, filings, transcripts, news and fund letters. That is the whole reason the connector ships two tools instead of 48 — the definitions would crowd out the context window.
Is the Fiscal.ai MCP connector really read only?
Yes, in substance. Every one of the 48 documented endpoints is a GET, so generated code can query market data but cannot write to anything at Fiscal.ai. The execute_code name is a strong write verb in general, and here it is honest only because the sandbox is network-isolated and the API behind it is read-only.
Does the Fiscal.ai MCP server cost money to use?
It is gated by your Fiscal.ai plan rather than metered per call. Fiscal.ai states MCP enforces the same entitlements as its REST API, so a free key gets 250 requests a day, a 50-per-minute burst and only 100 companies. No credit is spent by the connector itself, and seeing a tool does not mean your plan can reach it.
What OAuth scopes does the Fiscal.ai MCP server request?
Eleven, and they map to data domains rather than to read and write. Fiscal.ai's authorization server advertises financials, financials_sourcing, segments_and_kpis, stock_quotes, filings, adjusted_numbers, news, ir_events, ownership, fund_letters and fiscal_earnings_calendar. We read them live on 2026-08-19. There is no scope specific to code execution, because every scope is read-shaped already.
Which Fiscal.ai MCP endpoint should I use, the SSE one or the newer URL?
Use the streamable HTTP endpoint at api.fiscal.ai/mcp. Fiscal.ai documents that URL as the current one and describes the /mcp/sse address as a legacy endpoint kept for older clients. Anthropic's directory snapshot still carries the SSE form. Fiscal.ai specifically notes Microsoft Copilot Studio dropped SSE support, so register the newer URL there.
Sources
- Fiscal.ai MCP integration documentation — https://docs.fiscal.ai/docs/guides/mcp-integration (fetched 2026-08-19; source of both endpoint URLs, the legacy-SSE note, the entitlement-enforcement statement and the Copilot Studio transport requirement). The
.mdsuffix form returns a Next.js error shell, so this was read as HTML · retrieved 2026-08-19 - Fiscal.ai published MCP tool schemas — https://api.fiscal.ai/.well-known/microsoft-copilot/mcp-tools.json (fetched 2026-08-19, unauthenticated; two tools, and the only place the network-isolated 30-second sandbox is described) · retrieved 2026-08-19
- Fiscal.ai Microsoft plugin manifest — https://api.fiscal.ai/.well-known/microsoft-copilot/ai-plugin.json (fetched 2026-08-19, unauthenticated; source of the
isNonConsequentialannotation,GetPrivateDataandDataTransformhandling tags, and the terms and privacy URLs) · retrieved 2026-08-19 - Fiscal.ai API reference — https://docs.fiscal.ai/docs/api-reference (fetched 2026-08-19; the 48 documented GET endpoints were counted from this index, and it is the source of the ~55,000-company universe and the
allCompaniesparameter) · retrieved 2026-08-19 - Fiscal.ai rate limits and errors — https://docs.fiscal.ai/docs/guides/rate-limits (fetched 2026-08-19; 50 requests/minute, 250 requests/day, 100 free-plan companies, and the CUSIP/ISIN licence 403) · retrieved 2026-08-19
- Fiscal.ai free trial documentation — https://docs.fiscal.ai/docs/guides/free-trial (fetched 2026-08-19; the 100-company allowlist enumerated in full, and the statement that the same limits apply over REST and MCP) · retrieved 2026-08-19
- Fiscal.ai company querying guide — https://docs.fiscal.ai/docs/guides/company-querying (fetched 2026-08-19; the CUSIP and ISIN licence requirement, and the identifier schemes that carry no gate) · retrieved 2026-08-19
- Fiscal.ai MCP Skills documentation — https://docs.fiscal.ai/docs/guides/mcp-skills (fetched 2026-08-19; source of the 12,300-name screenable universe, the US-only ownership limit and the no-market-share-data statement) · retrieved 2026-08-19
- Live RFC 9728 protected-resource descriptor — https://api.fiscal.ai/.well-known/oauth-protected-resource/mcp/sse (fetched 2026-08-19; the path-append form named by the
www-authenticatechallenge. The root form returns a byte-identical 357-byte body; the path-insert form returns 401) · retrieved 2026-08-19 - Live RFC 8414 authorization-server metadata — https://api.fiscal.ai/.well-known/oauth-authorization-server (fetched 2026-08-19;
issuer, the elevenscopes_supportedentries, PKCES256, grant types and registration endpoint) · retrieved 2026-08-19 - Live anonymous probe — 2026-08-19: an anonymous POST request to
https://api.fiscal.ai/mcp/ssereturns HTTP 401 withwww-authenticate: Bearer realm="OAuth", resource_metadata="https://api.fiscal.ai/.well-known/oauth-protected-resource/mcp/sse", error="invalid_token"· retrieved 2026-08-19 docs.fiscal.ai/robots.txt(fetched 2026-08-19) allows all user agents and carries noContent-Signalaxes.fiscal.ai/robots.txtcould not be read: the apex host returns a Vercel bot challenge (HTTP 429) to curl with and without a browser user agent, which is a bot-mitigation response rather than a policy signal · retrieved 2026-08-19- Fiscal.ai docs sitemap — https://docs.fiscal.ai/sitemap.xml (fetched 2026-08-19; 15 URLs, the complete documentation map. No
llms.txtis published) · retrieved 2026-08-19 - Anthropic connector directory — https://claude.ai/directory/9620ff48-f0d9-4f7f-bda0-4d7240894538 (snapshot 2026-08-16; two tools, "Read only" permissions, no prompts, and the legacy
/mcp/sseendpoint) · retrieved 2026-08-16 - Anthropic, "Code execution with MCP" — https://www.anthropic.com/engineering/code-execution-with-mcp (the published pattern both this connector and Entendre implement)
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Finance
- Developer
- Fiscal.ai
- Tools
- 2
- Domain
- api.fiscal.ai
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.