Analytics
falcoscan.com
Provides tools to search FalcoScan's AI product catalog, fetch detailed product scores and signals, and analyze AI market opportunity, saturation, and mortality metrics.
ENDPOINT 1
https://falcoscan.com/api/mcp
MCP server metadata
- Name
- falcoscan
- Version
- 1.0.0
FalcoScan tracks 7,000+ AI products across 29 scored markets, including whether each product is still running. Authenticate with an API key from falcoscan.com/data-access.
Known tools 4
get_toolFetch one AI product by its FalcoScan slug, with every score and signal we hold.
Inferred read-onlylist_marketsAll 29 scored AI markets with average opportunity, saturation, heat and product counts.
Inferred read-onlymarket_mortalityPer-market counts of products that have shut down or been acquired, from the liveness sweep.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.falcoscan]
url = "https://falcoscan.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"falcoscan": {
"type": "http",
"url": "https://falcoscan.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: falcoscan
Remote MCP URL: https://falcoscan.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"falcoscan": {
"url": "https://falcoscan.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"falcoscan": {
"type": "http",
"url": "https://falcoscan.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "falcoscan",
"transport": "streamable-http",
"url": "https://falcoscan.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.