Other · Remote MCP server
TickerFacts
SEC EDGAR fundamentals as agent tools: look up or screen US public companies. Free, no key, CC0.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.tickerfacts/fundamentals- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-21
- Updated
- 2026-07-21
- Publisher
- com.tickerfacts
- Namespace
- Namespace verified by the MCP Registry via the domain tickerfacts.com · how
- Listed under
- SEC EDGAR MCP servers
- Website
- tickerfacts.com/developers
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://tickerfacts.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- tickerfacts 0.1.0 · protocol 2025-06-18
- Tools discovered
- 10:
get_fundamentals,screen_companies,get_company_research,get_economic_context,get_fundamentals_batch,get_company_evidence,get_county_context,get_cashflow_inputs,search_companies,send_feedback - Checked on
- 2026-10-05
How to connect TickerFacts
TickerFacts is a remote MCP server: there is nothing to install. Its endpoint is https://tickerfacts.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| ThruactName the job, not the vendor. Routes a provider, fails over, catalog off the tool list. | Remote · HTTPLive check: ✓ handshake |
| ThryxProtocol MCP ServerThryxProtocol v3.1 - gasless AI agent launchpad on Base. 21 tools wrap thryx.fun HTTP API. | Local · stdio |
| ThumbGatePre-action gates that block AI agents from repeating known mistakes. | Local · stdio |
| Tick MCPA time server that keeps your AI honest about time. Real clock + drift guard, zero dependencies. | Remote · HTTPLive check: ✓ handshake |
| TickerInsideHoldings, overlap, correlation and look-through risk for US ETFs, from issuer files, with no key. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| TickerrLive status, API pricing and rate limits for ChatGPT, Claude, Gemini, Cursor and 42+ AI tools. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| Tickwind US Market BoardsNo-API-key US market boards from SEC, Cboe, FINRA and CFTC: options flow, insiders, 13F, buybacks. | Remote · HTTPLive check: ✓ handshake |
| TidebaseInspect Tidebase agent runs, resolve approval gates, and trigger recovery from your AI assistant. | Local · stdio |