Vaaya: MCP server, CLI and agent surfaces

Yes: Vaaya runs a public MCP server at vaaya.ai that listed 14 tools to a client with no credentials on 4 November 2026. Examples: stocks, jobs, vaaya_test_connection. It speaks streamable-http, protocol 2025-06-18. Ora's cached score for vaaya.ai is 90, grade A, read on 5 November 2026.

Fact sheet

Company	Vaaya
Domain	vaaya.ai
Category	Developer Tools (assigned by this directory from the registry description)
MCP server	Verified (No authentication)
Ora score	90, grade A; Ora scanned the domain on 5 November 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for vaaya.ai, a vendor-published score)
Company found through	the GitHub MCP Registry; the official MCP Registry
Last verified	4 November 2026

MCP server

Endpoint	`https://vaaya.ai/mcp`
How it was found	listed in the GitHub MCP Registry; the official MCP Registry
Transport	streamable-http
HTTP status	200
Protocol version	2025-06-18
Server	vaaya 1.0.0
Capabilities	tools
Tools	14
Resources	0
Prompts	0
Connected	4 November 2026, 20:05 UTC
Handshake time	976 ms over 1 attempt

Tools listed

14 tools

stocks
jobs
vaaya_test_connection
vaaya_onboard
vaaya_account
vaaya_logout
docs
consult
use
result
buy
session
close
llm

Connector log

2 connections on 4 November 2026, read-only methods only

20:00:10Z https://vaaya.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 1090 ms
20:05:03Z https://vaaya.ai/mcp sent initialize, notifications/initialized, tools/list result verified (HTTP 200) 976 ms

Authentication

Auth type	No authentication

The sign-in route, step by step

Send the handshake to https://vaaya.ai/mcp over streamable-http. Servers on the 2026-07-28 revision answer server/discover; older servers answer initialize.
Send tools/list, then resources/list and prompts/list if the capabilities name them.
Send no token. The connector sent none and the server answered, so any MCP client can read this list.
Calling a tool is a separate step this directory never takes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for Vaaya. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
Surface	Result
OpenAPI file	Found: vaaya.ai (JSON, via a direct request).
WebMCP in the initial HTML	Not checked: the home page was not read by the shared crawl.
MCP discovery file	Not checked: the domain is not in the shared crawl for this edition.
A2A agent card	Not checked: the domain is not in the shared crawl for this edition.
A2A agent card (older path)	Not checked: the domain is not in the shared crawl for this edition.
agents.json	Not checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadata	Not checked: the domain is not in the shared crawl for this edition.
NLWeb endpoint	Not checked in this edition.

Registry listings

Registry listings
Registry	Listed
Official MCP Registry	Yes: ai.vaaya/mcp
GitHub MCP Registry	Yes
awesome-remote-mcp-servers	No
Smithery	Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
Glama	Not checked: Glama's API needs a key and attribution terms.