Talandor
Public MCP report

Exa

https://mcp.exa.ai/mcp

Official Registry and a direct check

Official Registry · ai.exa/exa · user-submitted endpoint · Publisher namespace: ai.exa

Server checked today at 20:06 UTC

Displayed catalog: last complete observation from September 19

2 public tools observed. Tools were not executed. These tools come from the catalog observation above, not from the latest availability check.

Reachable

What Talandor observed

The server answered

Add the endpoint to a compatible client below. A Watch can alert you if this public catalog changes.

This is a public protocol and tools/list check, not a functional validation.

https://mcp.exa.ai/mcp
AvailabilityReachablemeasured
Tools2 public tools observedmeasured
CompatibilityEstimated from published client rules · not a hands-on testestimated

Configure your assistant · Check details

How to use this MCP

Talandor checks the server; it does not connect the server to your assistant.

Choose your assistant, then copy the configuration shown for that client. Authentication is completed with the MCP provider, never inside Talandor.

    Open the official client guide (opens in a new tab)
    Compatibility evidence by assistant

    Compatibility is estimated from published configuration rules and is not a hands-on test in each client.

    Claude
    Observed 2025-11-25.
    Likely compatible · inferred
    Cursor
    Streamable HTTP and public HTTPS were observed.
    Likely compatible · inferred
    ChatGPT
    Public tool names, descriptions and schemas were observed. Plan and workspace access still apply.
    Likely compatible · inferred
    VS Code
    Public remote HTTP configuration can be assessed.
    Likely compatible · inferred
    Generic MCP
    Observed 2025-11-25.
    Likely compatible · inferred

    Rule evidence: Remote HTTPS rule v0.2 · reviewed 2026-09-12 · Remote HTTP rule v0.2 · reviewed 2026-09-12 · Remote app rule v0.2 · reviewed 2026-09-12 · Protocol and transport rule v0.2 · reviewed 2026-09-12

    Check details

    What changed

    Public contract stable since
    Last check · No semantic contract change since the previous complete snapshot.
    Info

    This public timeline shows the latest check, the last 24 hours, and the most recent important change. Watch keeps 30 days.

    The notes above are for this connector.

    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.

    Show 2 of 2 server-provided tool definitions
    web_fetch_exa
    Declared read-only
    Show server-provided details
    Server description (copied; language not verified)
    Read a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL. Best for: Extracting full content from known URLs. Batch multiple URLs in one call. Returns: Clean text content and metadata from the page(s).
    Input schema (server-provided preview — do not copy)
    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "urls"
      ],
      "properties": {
        "urls": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "URLs to read. Batch multiple URLs in one call."
        },
        "maxCharacters": {
          "type": "number",
          "minimum": 1,
          "description": "Maximum characters to extract per page (default: 3000)"
        }
      },
      "additionalProperties": false
    }
    web_search_exa
    Declared read-only
    Show server-provided details
    Server description (copied; language not verified)
    Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search through Linkedin profiles / companies respectively. If highlights are insufficient, follow up with web_fetch_exa on the best URLs.
    Input schema (server-provided preview — do not copy)
    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "objective",
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Natural language search query. Should be a semantically rich description of the ideal page, not just keywords. Optionally include category:<type> (company, people) to focus results — e.g. 'category:people John Doe software engineer'."
        },
        "objective": {
          "type": "string",
          "maxLength": 4096,
          "minLength": 1,
          "description": "Goal for this search turn; say which documents should rank first, which should be excluded, and what specific facts or figures to pull from them."
        },
        "numResults": {
          "type": "number",
          "description": "Number of search results to return (default: 10)."
        }
      },
      "additionalProperties": false
    }
    Evidence and limitations

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

    Attempted protocols: 2026-07-28, 2025-11-25

    Protocol2025-11-25
    TransportStreamable HTTP
    AuthNo authentication challenge observed
    EvidencePublic contract observed
    Total latency3141 ms
    Response bytes2441

    No diagnostic errors.

    Observation history
    Operational
    · stable since
    2025-11-25 · 2 tools · no change · 58 checks
    Operational
    2025-11-25 · 2 tools
    Operational
    2025-11-25 · 2 tools
    Complete public contract · 2025-11-25 · 2 tools
    417745203f67
    Complete public contract · 2025-11-25 · 2 tools
    417745203f67
    Complete public contract · 2025-11-25 · 2 tools
    417745203f67

    Deep monitoring eligibility

    Eligible for deep monitoring

    A complete public tools/list contract was observed, so a future deep-monitoring baseline can be compared safely.

    Personal Watch is not open yet. This report does not start a Watch or a payment.

    See public monitoring

    Automatic monitoring later

    Saving this connector does not start a Watch. Watch is a future offer; subscriptions and alerts are not available yet.

    Full Watch. Availability, protocol, auth and public tool contract changes can be compared.