_ registry / mcp streamable-http · checked 1h ago

AI Data Stream Site Search

https://aidata.stream

Registry code: a231fc9b08b18357

api record

Read-only search over the public aidata.stream marketing site (docs, blog, changelog, pricing, FAQ). Start with list_pages or search_site, then get_page for full text. This is not the customer data connector; existing customers connect their own analytics through the app (see /docs/connect-your-own-ai/).

endpoint
https://aidata.stream/mcp
protocol
streamable-http ·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 AI Data Stream Site Search live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is AI Data Stream Site Search free to use?
Not measured yet.
What tools does AI Data Stream Site Search have?
4 tools: search_site, get_page, list_pages, get_pricing.
Is AI Data Stream Site 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
248ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ 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_site unknown never probed

    Full-text search across aidata.stream: documentation, blog posts, changelog, pricing, FAQ and the home page. Returns the best-matching sections with a snippet and a URL (with anchor where available). Use get_page to read a whole page afterwards. English by default; pass lang for the French or German site.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "lang": {
          "enum": [
            "en",
            "fr",
            "de"
          ],
          "type": "string",
          "description": "Site language to search (default en)."
        },
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Max results (default 6)."
        },
        "query": {
          "type": "string",
          "description": "Search terms, e.g. \"connect GA4 service account\" or \"pricing extra seats\"."
        },
        "section": {
          "enum": [
            "docs",
            "blog",
            "changelog",
            "core"
          ],
          "type": "string",
          "description": "Restrict to one section of the site."
        }
      }
    }
    arguments 37 lines
  • get_page unknown never probed

    Fetch the full text of one aidata.stream page as Markdown. Accepts a path ("/pricing/", "/docs/getting-started/") or an absolute aidata.stream URL. Use list_pages or search_site to find URLs.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Page path or absolute URL on aidata.stream."
        },
        "max_chars": {
          "type": "integer",
          "maximum": 200000,
          "minimum": 500,
          "description": "Truncate the Markdown after this many characters (default 40000)."
        }
      }
    }
    arguments 18 lines
  • list_pages unknown never probed

    List the pages on aidata.stream with title and description, optionally filtered by section (docs, blog, changelog, core) and language. Good first call to see what documentation exists.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lang": {
          "enum": [
            "en",
            "fr",
            "de"
          ],
          "type": "string",
          "description": "Default en."
        },
        "section": {
          "enum": [
            "docs",
            "blog",
            "changelog",
            "core"
          ],
          "type": "string"
        }
      }
    }
    arguments 23 lines
  • get_pricing unknown never probed

    Current AI Data Stream plans as structured data: monthly and annual prices in USD, GBP and EUR, what each tier includes, trial terms, extra seat cost and sign-up links. AI usage is never billed by AI Data Stream: users bring their own AI API keys (BYOK).

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
_ try it 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 a231fc9b08b18357.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a231fc9b08b18357/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/a231fc9b08b18357/badge.svg)](https://brick.blue/agent/a231fc9b08b18357?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 know
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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

0 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.