Talandor

What Talandor observed

Firecrawl MCP Server

https://mcp.firecrawl.dev/v2/mcp

Not verified

MCP protocol not verified

Server checked October 27

The address answered, but this check did not complete an MCP exchange. An HTTP response does not show that MCP works.

Address availability
Reachable
HTTP 400 was received.
MCP protocol
Not verified
HTTP 400 does not establish an MCP exchange.
Public tools
List not read
No public tool list was recorded.
Use in your assistant: not verified · authentication details
Authentication
Unknown
Authentication was not recorded by this check.
Your assistant
Not verified
Talandor does not check the local setup in Cursor, ChatGPT, Claude, or Windsurf. Private tools were not verified. No tool call was executed.

What should I do next?

Set up in my assistant

Still blocked in your assistant? Diagnose the symptom →

  1. Check the exact MCP address

    Compare this address with the provider's documentation. A website homepage is not necessarily its MCP endpoint.

  2. Run another public check

    Use Check again below. A recent result may be reused; read the confirmation before treating it as a fresh check.

  3. Check with the provider

    If the problem persists, consult its status page or contact its support with the address and check time. This result alone does not identify the cause.

The tools still do not appear?

These are checks you can carry out. A public result does not identify a fault in your assistant.

  1. Check your client's MCP support

    Check your client's documentation for support of this remote HTTP endpoint and how to enable its tools. Local-server and remote-server configuration can differ.

  2. Check provider access

    If sign-in is requested, check the account and permissions in the assistant. An accessible public endpoint does not establish access to private tools.

  3. Read the error shown by the assistant

    Compare its configured address with this report, then use the provider's or assistant's official help. If you contact Talandor, share the error with tokens and private data removed.

Help and contact

Check details

Official Registry

Official Registry · io.github.firecrawl/firecrawl-mcp-server · Publisher namespace: io.github.firecrawl

What changed

No earlier complete public snapshot yet. Watch would start a baseline on the next complete check.

Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
Tools and declared exposure

Server annotations are declarations, not verified behavior.

Tools are not observable for this result. A private catalog is not published. This is not a claim that the server has no tools.
Evidence and limitations

Method: anonymous Streamable HTTP probe. We never invoke a tool.

Attempted protocols: 2026-07-28

ProtocolNot listed in this check
TransportHTTPS · HTTP 400
AuthNo authentication challenge in this check
EvidenceTransport only
Total latency695 ms
Response bytes0

MCP_RESPONSE_ERROR — The endpoint returned an incomplete or incompatible MCP response.

Observation history
Unknown
· stable since
No protocol · no change · 49 checks

No snapshots have been stored yet.

Deep monitoring eligibility

Not eligible yet

Only transport-level evidence was observed; no public tools/list contract was confirmed.

A Watch starts from the payment section on this page, and only after a verified payment.

See public monitoring
Watch · recurring plan

Watch is not available for this evidence

Optional. Setting up the connector does not require Watch.

A Watch needs a complete public contract or a qualified authentication surface before it can monitor meaningful changes.

Live checkout is open. A Watch activates only after a verified payment event; a browser return never starts monitoring.

See Watch coverage and status