Connect Vaaya and your agent gets 11 tools, among them close, consult, docs. It answers at https://vaaya.ai/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 17 October 2026, succeeded.
Paid APIs and tokenized shares for agents. Prepaid funding, including authorized Instinct checkout.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
close | Close an E2B sandbox session and stop its billing. Pass the `session_id`. Captures the final metered uptime cost and releases the hold. ALWAYS call this when finished with a session — an open session keeps billing per second of uptime. Safe Inputs: session_id |
consult | Vaaya's consultant. Describe ANY external capability you or the user might want — generate an image/video, search or scrape the web, run code in a sandbox, send/receive email, enrich a contact — and it helps figure out the best way, teachin Inputs: intent |
docs | Vaaya's deep reference, FREE and instant. Pass `topic` to get the full playbook for a capability area — exact services, actions, params, prices, model lists, and gotchas — the same reference files the vaaya skill ships. Topics: 'media' (ima Inputs: topic |
llm | Ask a DIFFERENT LLM a question and get its answer, billed per token from the Vaaya wallet (model cost + 3%, usually a fraction of a cent). Use it to get a second opinion from a rival model, cross-check an answer, summarize a huge blob cheap Inputs: prompt, model, system, max_tokens |
result | Fetch the status + output of an async job started by `use` (e.g. a video render). Pass the `job_id` that `use` returned with `{ async: true }`. Returns `{ status, result?, progress?, charged_cents }`: `running` (still working — when the job Inputs: job_id |
session | Run a command or code in an open E2B sandbox session (started by `use` with action `create_session`, which returns a `session_id`). Pass `session_id` plus either `command` (a shell command) or `code` (+ optional `language`: python/javascrip Inputs: session_id, command, code, language |
use | Execute a single external call, and bill on success. Used for any external capability (image/video/audio generation, web search, scraping, email, document parsing, code sandbox, browser automation, embeddings, etc.). The server validates pa Inputs: service, action, params, max_cost_cents, intent |
vaaya_account | Show which Vaaya account this connection is linked to and its money state. Returns { email, name, user_id, connected_client, scopes, balance_cents, credit_line, available_cents, credits_url, switch_account }. Call it whenever the user asks |
vaaya_logout | Disconnect this client from the current Vaaya account: revokes this connection's authorization server-side, so every later call fails with 401 until the user reconnects. Call it when the user asks to log out, sign out, disconnect, or switch |
vaaya_onboard | Public onboarding hint for an agent whose user isn't linked to Vaaya yet. Returns where the human should go to connect (and sign up if new). Call this when vaaya_test_connection reports needs_auth, or any tool returns unauthorized, then rel |
vaaya_test_connection | Round-trip ping that confirms the agent → Vaaya connection and whether the user is linked. Returns { ok:true, userId, scope, version, server_time, first_call } when linked — SHOW `first_call.show_to_user` to the user as written, it is the s |
Every block below points at https://vaaya.ai/mcp. Pick your client and copy.
claude mcp add --transport http vaaya https://vaaya.ai/mcp
{
"mcpServers": {
"vaaya": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://vaaya.ai/mcp"]
}
}
}{
"mcpServers": {
"vaaya": {
"url": "https://vaaya.ai/mcp"
}
}
}{
"servers": {
"vaaya": {
"type": "http",
"url": "https://vaaya.ai/mcp"
}
}
}{
"context_servers": {
"vaaya": {
"url": "https://vaaya.ai/mcp"
}
}
}{
"mcpServers": {
"vaaya": {
"serverUrl": "https://vaaya.ai/mcp"
}
}
}{
"mcpServers": {
"vaaya": {
"url": "https://vaaya.ai/mcp"
}
}
}name: Vaaya
version: 0.0.1
schema: v1
mcpServers:
- name: Vaaya
type: streamable-http
url: https://vaaya.ai/mcp{
"mcpServers": {
"vaaya": {
"httpUrl": "https://vaaya.ai/mcp"
}
}
}{
"mcpServers": {
"vaaya": {
"type": "http",
"url": "https://vaaya.ai/mcp"
}
}
}{
"mcpServers": {
"vaaya": {
"url": "https://vaaya.ai/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fvaaya.ai%2Fmcp&type=streamable_http&id=vaaya&name=Vaaya
It answered our last check on 17 October 2026 in 225 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by vaaya.ai and served from vaaya.ai, the vendor's own domain: https://vaaya.ai/mcp.
11, as returned by the server's own tools/list on 9 September 2026: close, consult, docs, llm, result, session, use, vaaya_account, and 3 more.
It answered our last check on 17 October 2026 in 225 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://vaaya.ai/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: ai.vaaya. Endpoint host: vaaya.ai. ARD identifier: urn:air:ai.vaaya:mcp:mcp.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.