Vaeo AI Discovery Reports
REMOTE · VAEO.COM.AU
How often AI assistants name a local Australian business, and which pages they read.
Available components
Last scanned (19 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Marketing and SEO
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 705 tokens (~100/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 70
First indexed and scored.
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 22 Oct 2026 · Probed https://vaeo.com.au/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vaeo.com.au | CN=WE1,O=Google Trust Services,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e053e6d4ee3bede40ec10c663e5e66b8 |
| SANs: vaeo.com.au, *.vaeo.com.au | ||||||
| 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 insecure
Validation of vaeo.com.au. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| au. | present | 26642 | 8 | Verified |
| com.au. | present | 14185 | 8 | Verified |
| vaeo.com.au. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vaeo.com.au/mcp | Verified | 200 | |
| http (plaintext) | http://vaeo.com.au/mcp | HTTPS enforced | 301 | https://vaeo.com.au/mcp |
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 →
ask_about_report One part of the report ~95
One part of a finished report, from the saved results (no new AI questions, no cost). Topics: short_answer, who_the_ais_named (who is named more), each_ai, each_question, pages_the_ais_read (which sites to get on), website, start_here (what to do first).
| Name | Type | Req | Description |
|---|---|---|---|
| order_key | string | yes | The order_key that order_report gave. |
| topic | string | yes | – |
No output schema declared.
No examples provided.
check_order Check an order ~47
Where an order is: not paid yet, being made, waiting, in its final check, done, or failed.
| Name | Type | Req | Description |
|---|---|---|---|
| order_key | string | yes | The order_key that order_report gave. |
No output schema declared.
No examples provided.
find_business Find a business ~52
Search Google Maps for an Australian business by name and suburb, for example "Corner Dental Newtown". Gives each match's place_id for get_questions and order_report.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Business name and suburb. |
No output schema declared.
No examples provided.
get_questions Questions and price ~71
For one business: its details, our trade for it, the questions a report asks the AIs, and the price in A$.
| Name | Type | Req | Description |
|---|---|---|---|
| place_id | string | yes | From find_business. |
| trade | string | – | Optional. One of list_trades, when ours for the business is wrong or missing. |
No output schema declared.
No examples provided.
get_report Read the report ~87
The finished report as data: how often the AIs named the business, its place among the businesses they named, each AI, each question, the sites the AIs cited, its website check, and "Start here" (at most 3 things to do first, each with the fact and count behind it).
| Name | Type | Req | Description |
|---|---|---|---|
| order_key | string | yes | The order_key that order_report gave. |
No output schema declared.
No examples provided.
list_trades Trades we report on ~30
The kinds of business Vaeo makes reports for. A business of another kind cannot be ordered yet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
order_report Order a report ~162
Start an order and get a Stripe payment link. Nothing is charged here: the person opens the link and pays on Stripe's page, and gets the report by email. Give the person the link and the price. Keep the order_key to follow the order. With compare_with_place_id (a business of the same trade in the same suburb): two reports and a comparison.
| Name | Type | Req | Description |
|---|---|---|---|
| compare_with_place_id | string | – | Optional. A second business to compare with. |
| place_id | string | yes | – |
| trade | string | yes | One of list_trades. |
| trade_questions | array | – | Optional. Labels of the trade questions from get_questions. Without it: the usual 2. The 8 general questions are always asked; 16 questions at most. |
No output schema declared.
No examples provided.
How do I install the Vaeo AI Discovery Reports MCP server?
Vaeo AI Discovery Reports is a hosted endpoint at https://vaeo.com.au/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 · vaeo.com.au
claude mcp add --transport http au-com-vaeo-reports 'https://vaeo.com.au/mcp'
What is the Vaeo AI Discovery Reports MCP server?
Vaeo AI Discovery Reports is an MCP server listed in the public MCP registry as au.com.vaeo/reports. How often AI assistants name a local Australian business, and which pages they read. This page covers its hosted endpoint (https://vaeo.com.au/mcp).
Is the Vaeo AI Discovery Reports MCP server safe to use?
Vaeo AI Discovery Reports scores 73 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 Vaeo AI Discovery Reports MCP server expose?
Vaeo AI Discovery Reports exposes 7 tools: list_trades, find_business, get_questions, order_report, check_order, and 2 more. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.
Does the Vaeo AI Discovery Reports MCP server require authentication?
No. We connected to Vaeo AI Discovery Reports without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vaeo AI Discovery Reports MCP server still maintained?
Vaeo AI Discovery Reports is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.