FalcoScan
REMOTE · FALCOSCAN.COM · SCANNED OCT 4
AI market intelligence on 7,000+ AI products in 29 markets. API, MCP and dashboard at falcoscan.com.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 261 tokens (~65/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the FalcoScan MCP server?
FalcoScan is a hosted endpoint at https://falcoscan.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · falcoscan.com
claude mcp add --transport http com-falcoscan-mcp 'https://falcoscan.com/api/mcp'
{
"mcpServers": {
"com-falcoscan-mcp": {
"url": "https://falcoscan.com/api/mcp"
}
}
} {
"servers": {
"com-falcoscan-mcp": {
"type": "http",
"url": "https://falcoscan.com/api/mcp"
}
}
} [mcp_servers.com-falcoscan-mcp] url = "https://falcoscan.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-falcoscan-mcp": {
"type": "remote",
"url": "https://falcoscan.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-falcoscan-mcp --url 'https://falcoscan.com/api/mcp' --transport streamable-http
mcp_servers:
com-falcoscan-mcp:
url: "https://falcoscan.com/api/mcp" {
"McpServers": {
"com-falcoscan-mcp": {
"Transport": "http",
"Url": "https://falcoscan.com/api/mcp"
}
}
} assistant mcp add com-falcoscan-mcp -t streamable-http -u 'https://falcoscan.com/api/mcp'
{
"mcpServers": {
"com-falcoscan-mcp": {
"type": "http",
"url": "https://falcoscan.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 26 Sept 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://falcoscan.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=falcoscan.com | CN=YR2,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | RSA 2048 | SHA256-RSA | 58a9d6bd3a8063144cf2f54f8635081c7eb |
| SANs: falcoscan.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of falcoscan.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| falcoscan.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://falcoscan.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://falcoscan.com/api/mcp | HTTPS enforced | 308 | https://falcoscan.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_tool ~34
Fetch one AI product by its FalcoScan slug, with every score and signal we hold.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_markets ~37
All 29 scored AI markets with average opportunity, saturation, heat and product counts. The fastest way to see where the market is crowded.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
market_mortality ~35
Per-market counts of products that have shut down or been acquired, from the liveness sweep. Unique to FalcoScan.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_tools ~114
Search the FalcoScan AI product catalog. Filter by category, pricing, liveness and opportunity, and sort by opportunity or rating.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Market name, e.g. "Healthcare". |
| include_dead | boolean | – | Include products that no longer resolve. Defaults to false. |
| limit | number | – | Rows to return, max 200. |
| min_opportunity | number | – | Only return products at or above this opportunity score. |
| query | string | – | Free text matched against name and tagline. |
No output schema declared.
No examples provided.
What is the FalcoScan MCP server?
FalcoScan is an MCP server listed in the public MCP registry as com.falcoscan/mcp. AI market intelligence on 7,000+ AI products in 29 markets. API, MCP and dashboard at falcoscan.com. This page covers its hosted endpoint (https://falcoscan.com/api/mcp).
Is the FalcoScan MCP server safe to use?
FalcoScan scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FalcoScan MCP server expose?
FalcoScan exposes 4 tools: search_tools, get_tool, list_markets, market_mortality. Their descriptions and schemas cost roughly 220 tokens of context every time the server is loaded.
Does the FalcoScan MCP server require authentication?
Yes. FalcoScan asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the FalcoScan MCP server still maintained?
FalcoScan is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.