HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News

Web and news results in any language and country (Brave index)

hubvibe_search_results

Read-onlyIdempotent

Web search API / SERP results: raw web and news results from Brave's independent index in any language and country, with title, URL, description, age and extra snippets (headline, source and age for news). Filter by country, language and freshness (day, week, month, year). Results, not an answer: pick what to read next with extract.page. Input: query; optional country, language, count, freshness, news. $0.25 per call. Returns: query, country, language, freshness, web[{title, url, description, age, page_age, language, site_name, hostname, extra_snippets[]}], web_count, news[{title, url, description, age, page_age, source, breaking}], news_count, more_results_available, source, notes[], checked_at.

Input Schema

TableJSON Schema

Name	Required	Description
`news`	No	Include news results. Default true.
`count`	No	Results per block, default 10.
`query`	Yes	Words to search for, in any language.
`country`	No	Market, ISO 3166-1 alpha-2 (US, JP, DE). Default: the engine's.
`language`	No	Optional answer language, BCP-47 (en, ja, pt-BR). Default: the input's.
`freshness`	No	Only results from this window.
`safesearch`	No	Default moderate.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes
`status`	Yes
`worker`	Yes
`price_usd`	Yes
`provenance`	Yes
`receipt_id`	Yes
`attribution`	No
`receipt_url`	Yes
`billing_warning`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed24 schema fields changedOct 1, 2026

changedInput schema / properties / language / description

Previous value: -"Optional BCP-47 language tag (en, ja, pt-BR, zh-Hant): every prose field of the answer is written in this language. Default: the language of the material or question."New value: +"Optional answer language, BCP-47 (en, ja, pt-BR). Default: the input's."

removedOutput schema / description

Removed value: -"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on every /work route. A receipt for the job is at `receipt_url`."

removedOutput schema / properties / attribution / description

Removed value: -"Present only when the result's text was machine-translated: the credit to show with it."

removedOutput schema / properties / attribution / items / description
```
Removed value: -"A credit."
```

removedOutput schema / properties / attribution / items / properties

Removed value: -{
-  "text": {
-    "description": "Credit.",
-    "examples": [
-      "Translated by Google"
-    ],
-    "type": "string"
-  },
-  "url": {
-    "description": "Link.",
-    "examples": [
-      "https://translate.google.com"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / properties / attribution / items / required
```
Removed value: -[
-  "text",
-  "url"
-]
```
removedOutput schema / properties / attribution / items / type
```
Removed value: -"object"
```

removedOutput schema / properties / billing_warning / description

Removed value: -"Present only when the charge was recorded with a caveat."

removedOutput schema / properties / billing_warning / examples
```
Removed value: -[
-  "settlement pending"
-]
```
removedOutput schema / properties / price_usd / description
```
Removed value: -"What this call cost, in USD."
```
removedOutput schema / properties / price_usd / examples
```
Removed value: -[
-  0.02
-]
```

removedOutput schema / properties / provenance / description

Removed value: -"How the result was produced: which providers ran and how long each took."

removedOutput schema / properties / provenance / properties

Removed value: -{
-  "attempts": {
-    "description": "Provider attempts made, including retries and failovers.",
-    "examples": [
-      1
-    ],
-    "type": "integer"
-  },
-  "elapsed_ms": {
-    "description": "Wall-clock milliseconds for the whole job.",
-    "examples": [
-      340
-    ],
-    "type": "integer"
-  },
-  "providers_used": {
-    "description": "Providers that served the job.",
-    "examples": [
-      [
-        "coinbase-advanced-trade-public"
-      ]
-    ],
-    "items": {
-      "description": "Provider name.",
-      "examples": [
-        "coinbase-advanced-trade-public"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "steps": {
-    "description": "Every step the job ran, in order.",
-    "items": {
-      "description": "One step of the job.",
-      "properties": {
-        "ms": {
-          "description": "Milliseconds the step took.",
-          "examples": [
-            312
-          ],
-          "type": "integer"
-        },
-        "ok": {
-          "description": "Whether the step succeeded.",
-          "examples": [
-            true
-          ],
-          "type": "boolean"
-        },
-        "provider": {
-          "description": "Provider that served the step.",
-          "examples": [
-            "coinbase-advanced-trade-public"
-          ],
-          "type": "string"
-        },
-        "reason": {
-          "description": "Failure reason, on a failed step.",
-          "examples": [
-            "provider_timeout"
-          ],
-          "type": "string"
-        },
-        "step": {
-          "description": "Step name inside the worker.",
-          "examples": [
-            "quote"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "step",
-        "ok",
-        "ms"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / properties / provenance / required

Removed value: -[
-  "steps",
-  "providers_used",
-  "attempts",
-  "elapsed_ms"
-]

removedOutput schema / properties / receipt_id / description
```
Removed value: -"Receipt id for this job."
```
removedOutput schema / properties / receipt_id / examples
```
Removed value: -[
-  "rcpt_9f1c2b3a4d5e6f70"
-]
```

removedOutput schema / properties / receipt_url / description

Removed value: -"Where to fetch the machine-readable receipt (free, no payment)."

removedOutput schema / properties / receipt_url / examples

Removed value: -[
-  "/work/receipts/rcpt_9f1c2b3a4d5e6f70"
-]

removedOutput schema / properties / result / properties

Removed value: -{
-  "checked_at": {
-    "description": "When this node read the source (UTC). Nothing here is cached.",
-    "examples": [
-      "2026-09-26T18:00:00Z"
-    ],
-    "format": "date-time",
-    "type": "string"
-  },
-  "country": {
-    "description": "Market searched.",
-    "examples": [
-      "JP"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "freshness": {
-    "description": "Window applied.",
-    "examples": [
-      "week"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "language": {
-    "description": "Search language when given.",
-    "examples": [
-      "ja"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "more_results_available": {
-    "description": "The engine has more pages.",
-    "examples": [
-      true
-    ],
-    "type": "boolean"
-  },
-  "news": {
-    "description": "News results; empty when not asked or none.",
-    "items": {
-      "description": "One news result.",
-      "properties": {
-        "age": {
-          "description": "Age as worded.",
-          "examples": [
-            "2 hours ago"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "breaking": {
-          "description": "Flagged breaking by the engine.",
-          "examples": [
-            false
-          ],
-          "type": "boolean"
-        },
-        "description": {
-          "description": "Snippet.",
-          "examples": [
-            "..."
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "page_age": {
-          "description": "Article date when known.",
-          "examples": [
-            "2026-09-27T09:00:00"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "source": {
-          "description": "Publisher or host.",
-          "examples": [
-            "Reuters"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "title": {
-          "description": "Headline.",
-          "examples": [
-            "Typhoon nears Tokyo"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "url": {
-          "description": "Article URL.",
-          "examples": [
-            "https://example.com/news/1"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "title",
-        "url",
-        "description",
-        "age",
-        "page_age",
-        "source",
-        "breaking"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "news_count": {
-    "description": "News results returned.",
-    "examples": [
-      3
-    ],
-    "type": "integer"
-  },
-  "notes": {
-    "description": "Caveats; empty when none.",
-    "examples": [
-      []
-    ],
-    "items": {
-      "description": "A caveat.",
-      "examples": [
-        "No result matched the query."
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "query": {
-    "description": "Query as given.",
-    "examples": [
-      "東京 天気予報"
-    ],
-    "type": "string"
-  },
-  "source": {
-    "const": "brave",
-    "description": "Data source.",
-    "type": "string"
-  },
-  "web": {
-    "description": "Web results in engine order.",
-    "items": {
-      "description": "One web result.",
-      "properties": {
-        "age": {
-          "description": "Age as the engine words it.",
-          "examples": [
-            "4 日前"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "description": {
-          "description": "Engine snippet.",
-          "examples": [
-            "Tokyo weather forecast with current conditions..."
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "extra_snippets": {
-          "description": "Up to 5 extra snippets.",
-          "examples": [
-            []
-          ],
-          "items": {
-            "description": "Another snippet from the page.",
-            "examples": [
-              "Wind: 10 km/h"
-            ],
-            "type": "string"
-          },
-          "type": "array"
-        },
-        "hostname": {
-          "description": "Host.",
-          "examples": [
-            "www.accuweather.com"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "language": {
-          "description": "Page language.",
-          "examples": [
-            "en"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "page_age": {
-          "description": "Page date when known.",
-          "examples": [
-            "2026-09-23T10:38:54"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "site_name": {
-          "description": "Site name.",
-          "examples": [
-            "AccuWeather"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "title": {
-          "description": "Page title.",
-          "examples": [
-            "Tokyo, Tokyo, Japan Weather Forecast | AccuWeather"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "url": {
-          "description": "Page URL.",
-          "examples": [
-            "https://www.accuweather.com/en/jp/tokyo/226396/weather-forecast/226396"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "title",
-        "url",
-        "description",
-        "age",
-        "page_age",
-        "language",
-        "site_name",
-        "hostname",
-        "extra_snippets"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "web_count": {
-    "description": "Web results returned.",
-    "examples": [
-      5
-    ],
-    "type": "integer"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "query",
-  "country",
-  "language",
-  "freshness",
-  "web",
-  "web_count",
-  "news",
-  "news_count",
-  "more_results_available",
-  "source",
-  "notes",
-  "checked_at"
-]

removedOutput schema / properties / status / description

Removed value: -"Present only on a delivered result."

removedOutput schema / properties / worker / description

Removed value: -"Catalog name of the worker that ran."

removedOutput schema / properties / worker / examples
```
Removed value: -[
-  "market.quote"
-]
```

removedOutput schema / title

Removed value: -"search.results response"

Changed1 schema field changedSep 28, 2026

addedOutput schema / properties / attribution

Added value: +{
+  "description": "Present only when the result's text was machine-translated: the credit to show with it.",
+  "items": {
+    "description": "A credit.",
+    "properties": {
+      "text": {
+        "description": "Credit.",
+        "examples": [
+          "Translated by Google"
+        ],
+        "type": "string"
+      },
+      "url": {
+        "description": "Link.",
+        "examples": [
+          "https://translate.google.com"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "text",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

AddedSep 27, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, open-world, idempotent, non-destructive behavior. The description adds useful context beyond annotations: the $0.25 per call cost, Brave-index source, raw-result nature, and returned fields including notes and more_results_available.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and cost are front-loaded, but the description is dense and repeats a detailed return-value list even though an output schema exists. That return enumeration is largely redundant and makes the definition longer than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter search tool with annotations and an output schema, the description covers purpose, filters, cost, workflow, and outputs. It omits safesearch from its inline input list and does not explicitly distinguish sibling search tools, but the schema covers parameter details and the description is otherwise sufficient.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all parameters including enums and defaults. The description lists query and several optional inputs, adding little semantic detail beyond what the schema provides, which is the baseline 3 when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: raw web and news SERP results from Brave's independent index, with language/country scope. It distinguishes from answer-producing tools via 'Results, not an answer,' but does not explicitly name or differentiate from close siblings like hubvibe_search_web or hubvibe_news_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear workflow context: use this to get results, then use extract.page to choose what to read next. It lacks explicit when-not guidance or named alternatives among search siblings, so it stops short of full routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.