MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

Financial Modeling Prep MCP Server

Earlier Revision Publisher unverified Confidence: Good (0.85)

Financial Modeling Prep MCP Server is an MCP server published by imbenrabi, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.

Does Financial Modeling Prep MCP Server support the current MCP specification (2026-07-28)?

Not yet confirmed. Financial Modeling Prep MCP Server is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.

Is Financial Modeling Prep MCP Server a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for Financial Modeling Prep MCP Server (as of 2026-08-20).

How do I connect to Financial Modeling Prep MCP Server?

Financial Modeling Prep MCP Server is available via the package npm:financial-modeling-prep-mcp-server, the official MCP Registry under io.github.imbenrabi/financial-modeling-prep-mcp-server, the source repository at https://github.com/imbenrabi/financial-modeling-prep-mcp-server. Authentication: unknown. Transports: stdio.

Does Financial Modeling Prep MCP Server support MCP revision 2025-11-25?

Yes. Financial Modeling Prep MCP Server supports MCP revision 2025-11-25 (checked 2026-08-20).

Does Financial Modeling Prep MCP Server support MCP revision 2026-07-28?

No. Financial Modeling Prep MCP Server was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).

When were Financial Modeling Prep MCP Server's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

MCP server for Financial Modeling Prep API with 250+ financial data tools

Which MCP spec revisions does Financial Modeling Prep MCP Server support?

Financial Modeling Prep MCP Server has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source
MCP 2026-07-28 Not supported Source

How widely adopted is Financial Modeling Prep MCP Server?

Ranked #371 in The MCP 500 with Adoption Index 47.93 (snapshot , methodology v1).

Measurement Value Source
Official MCP Registry yes API ·
Docker MCP Catalog no API ·
npm downloads (weekly) 315 API ·
GitHub stars 147 API ·
GitHub forks 51 API ·
Last push 2026-07-02T17:24:51Z API ·
Repository archived no API ·

Repository and package signals for Financial Modeling Prep MCP Server

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Created
Open issues
2
Primary language
TypeScript
License (repository)
Apache-2.0
Continuous integration
Present
Tests
Present
Security policy
None

Declared topics: ai, etf-investments, financial-modeling-prep, fmp, llm, mcp, mcp-server, mcp-tools, smithery-ai, stock-data, stock-market — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
2.6.12
Last published
First published
Releases
17
License (package)
Apache-2.0
Maintainers
1
Direct dependencies
7
Unpacked size
917 KB
Registry signature
Signed
Build provenance
No attestation

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for io.github.imbenrabi/financial-modeling-prep-mcp-server at version 2.6.12 - lists package npm:financial-modeling-prep-mcp-server and repository https://github.com/imbenrabi/financial-modeling-prep-mcp-server - accessed
  2. npm registry metadata for financial-modeling-prep-mcp-server at published version 2.6.12, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
  3. Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed