Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AIdata site search

REMOTE · AIDATA.STREAM

Read-only search over the aidata.stream documentation, blog, changelog, pricing and FAQ.

Available components

+3 this week 85 Trust /100

Last scanned (14 minutes ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security83
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 428 tokens (~107/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 Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 5 Nov 2026 · Probed https://aidata.stream/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aidata.stream CN=WE1,O=Google Trust Services,C=US 2 Oct 2026 31 Dec 2026 ECDSA 256 ECDSA-SHA256 e1c718e07907ceff13e3bd582bf81a50
SANs: aidata.stream
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of aidata.stream. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
stream. present 31735 8 Verified
aidata.stream. present 2371 13 Verified
aidata.stream. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=2592000; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aidata.stream/mcp Verified 200
http (plaintext) http://aidata.stream/mcp HTTPS enforced 301 https://aidata.stream/mcp
MCP tools · 4 exposed · ~360 tokens

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 →

Tool Tokens
get_page ~92

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.

NameTypeReqDescription
max_charsinteger–Truncate the Markdown after this many characters (default 40000).
urlstringyesPage path or absolute URL on aidata.stream.
NameTypeReqDescription
markdownstringyes–
truncatedbooleanyes–
urlstringyes–

No examples provided.

get_pricing ~66

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

Input schema present but exposes no named parameters.

NameTypeReqDescription
billing_modelstringyes–
extra_seat_per_monthobject––
notesarray––
plansarrayyes–
urlstringyes–

No examples provided.

list_pages ~62

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.

NameTypeReqDescription
langstring–Default en.
sectionstring––
NameTypeReqDescription
pagesarrayyes–
totalintegeryes–

No examples provided.

search_site ~140

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.

NameTypeReqDescription
langstring–Site language to search (default en).
limitinteger–Max results (default 6).
querystringyesSearch terms, e.g. "connect GA4 service account" or "pricing extra seats".
sectionstring–Restrict to one section of the site.
NameTypeReqDescription
querystringyes–
resultsarrayyes–
total_matchesintegeryes–

No examples provided.

Install

How do I install the AIdata site search MCP server?

AIdata site search is a hosted endpoint at https://aidata.stream/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 · aidata.stream

# add to Claude Code
claude mcp add --transport http stream-aidata-site-search 'https://aidata.stream/mcp'
Common questions

What is the AIdata site search MCP server?

AIdata site search is an MCP server listed in the public MCP registry as stream.aidata/site-search. Read-only search over the aidata.stream documentation, blog, changelog, pricing and FAQ. This page covers its hosted endpoint (https://aidata.stream/mcp).

Is the AIdata site search MCP server safe to use?

AIdata site search scores 85 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 AIdata site search MCP server expose?

AIdata site search exposes 4 tools: search_site, get_page, list_pages, get_pricing. Their descriptions and schemas cost roughly 360 tokens of context every time the server is loaded.

Does the AIdata site search MCP server require authentication?

No. We connected to AIdata site search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AIdata site search MCP server still maintained?

AIdata site search is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.