_ registry / mcp + a2a http-sse · checked 56m ago

Tavily Search

https://tavily-ai-search.vercel.app

Registry code: 2362122e3591c6a3

api record

Declared as an MCP endpoint by 8004scan; probed directly.

from a public catalogue that lists it, not from the operator

endpoint
https://tavily-ai-search.vercel.app/mcp
door code
f5a766f67530bf90
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Tavily Search live?
Yes — it answered the hub's last check (checked 56m ago). It answered 100% of checks over the last 30 days.
Is Tavily Search free to use?
Yes — the hub reached it with no key and no payment.
What tools does Tavily Search have?
4 tools: search, crawl, extract, map.
Is Tavily Search safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
252ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search unknown 56m ago

    Search the web for real-time information using Tavily's AI-optimized search engine. Returns relevant sources, snippets, and optional AI-generated answers.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "The search query to look up on the web"
        },
        "timeRange": {
          "enum": [
            "year",
            "month",
            "week",
            "day",
            "y",
            "m",
            "w",
            "d"
          ],
          "type": "string",
          "description": "Time range for search results"
        },
        "searchDepth": {
          "enum": [
            "basic",
            "advanced",
            "fast",
            "ultra-fast"
          ],
          "type": "string",
          "description": "The depth of the search - 'basic' for quick results, 'advanced' for comprehensive search, 'fast' for low latency with high relevance (BETA), 'ultra-fast' prioritizes latency above all (BETA)"
        }
      }
    }
    arguments 37 lines
  • crawl unknown never probed

    Crawl a website starting from a base URL to discover and extract content from multiple pages. Intelligently traverses links and extracts structured data at scale.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The base URL to start crawling from"
        },
        "maxDepth": {
          "type": "number",
          "maximum": 5,
          "minimum": 1,
          "description": "Maximum depth to crawl (number of link hops from the base URL, default: 1)"
        },
        "extractDepth": {
          "enum": [
            "basic",
            "advanced"
          ],
          "type": "string",
          "description": "Extraction depth for page content (default: 'basic')"
        },
        "instructions": {
          "type": "string",
          "description": "Optional instructions to guide the crawler (e.g., 'only crawl blog posts', 'focus on product pages')"
        },
        "allowExternal": {
          "type": "boolean",
          "description": "Whether to allow crawling external domains (default: false)"
        }
      }
    }
    arguments 35 lines
  • extract unknown never probed

    Extract clean, structured content from one or more URLs. Returns parsed content in markdown or text format, optimized for AI consumption.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "urls"
      ],
      "properties": {
        "urls": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Array of URLs to extract content from"
        },
        "query": {
          "type": "string",
          "description": "User intent query for reranking extracted content chunks"
        },
        "extractDepth": {
          "enum": [
            "basic",
            "advanced"
          ],
          "type": "string",
          "description": "Extraction depth - 'basic' for main content, 'advanced' for comprehensive extraction (default: 'basic')"
        }
      }
    }
    arguments 28 lines
  • map unknown never probed

    Map the structure of a website starting from a base URL. Discovers pages, links, and site hierarchy without extracting full content. Ideal for understanding site architecture.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "The base URL to start mapping from"
        },
        "maxDepth": {
          "type": "number",
          "maximum": 5,
          "minimum": 1,
          "description": "Maximum depth to map (number of link hops from the base URL, default: 1)"
        },
        "instructions": {
          "type": "string",
          "description": "Optional instructions to guide the mapping (e.g., 'focus on documentation pages', 'skip API references')"
        },
        "allowExternal": {
          "type": "boolean",
          "description": "Whether to allow mapping external domains (default: false)"
        }
      }
    }
    arguments 27 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 2362122e3591c6a3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/2362122e3591c6a3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/2362122e3591c6a3/badge.svg)](https://brick.blue/agent/2362122e3591c6a3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
245ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.