Vaaya MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Vaaya priced API calls and tokenized-share purchases: Do stated spend ceilings and human funding gates still prevent agent purchases beyond the quoted plan?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Budgeted pay-per-call access to many external agent services with explicit spend ceilings.

What we know

Hosted action/payment gateway with local shim, live catalog discovery, OAuth, `consult/use/result`, per-call ceilings, prepaid/x402/MPP rails and broad service actions.

Maintenance / activity evidence

@vaaya/mcp 0.6.8 published 2026-09-13T17:43:29.633Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Potentially broad external-service, connected-account, commerce and financial-action authority. Writes: Send email; Run browser/compute/media jobs; Create CRM/sheet/calendar records; Buy products/bookings; Create automations; Use metered sandboxes; Buy supported tokenized shares.
OAuth grants/API tokens/payment rails.
Sensitive access: Connected accounts, Contact/lead data, Email, Balances/purchases, Financial transactions, Browser sessions

Action/payment gateway with real spending and third-party effects; budget ceilings do not replace user authorization.
OAuth/PKCE, revocation, local credential file mode 0600 and failed-call no-charge claims are documented.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do stated spend ceilings and human funding gates still prevent agent purchases beyond the quoted plan?

The bounded review of the publisher's documented Vaaya priced API calls and tokenized-share purchases and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Action/payment gateway with real spending and third-party effects; budget ceilings do not replace user authorization.
OAuth/PKCE, revocation, local credential file mode 0600 and failed-call no-charge claims are documented.
Potentially broad external-service, connected-account, commerce and financial-action authority.
OAuth grants/API tokens/payment rails.
Queries/outputs/payment metadata and connected-account data pass through Vaaya; vendor keys/upstream URLs are not exposed to the agent.
Reviewed write actions: Send email; Run browser/compute/media jobs; Create CRM/sheet/calendar records; Buy products/bookings; Create automations; Use metered sandboxes; Buy supported tokenized shares
Sensitive access: Connected accounts, Contact/lead data, Email, Balances/purchases, Financial transactions, Browser sessions
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
detailed retention/deletion
live catalog/tool count
per-service live pricing
Prices, availability and tool surface are live.
External actions can spend money or contact third parties.
Share purchases require supported tickers, stock permission and prepaid funds.
Detailed retention was not established.

Original activity observations

@vaaya/mcp 0.6.8 published 2026-09-13T17:43:29.633Z

Technical identity

npm/@vaaya/mcp

Exact implementation source: https://www.npmjs.com/package/@vaaya/mcp ↗
Reviewed resource type: Gateway
Repository identity: vaaya-ai/vaaya-mcp
Package identity: npm:@vaaya/mcp
Service endpoint: https://vaaya.ai/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@vaaya/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
vaaya-ai/vaaya-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
Evidence source ↗
vaaya.ai/llms.txt
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
vaaya.ai/llms-full.txt
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect gateway
Publisher instructions
OAuth grants can enable tokenized share purchases. Publisher documents grant revocation; confirm before financial operations.
publisher documented install or connect · Publisher instructions
npx @vaaya/mcp install
Configure / authenticate
MCP100 setup guide
Publisher supports OAuth authorization; avoid tokenized-share buying or account funding as check. `install` edits host registrations, so preview target host before running.
remote_streamable_http: https://vaaya.ai/mcp
Remote client registration · Publisher instructions
claude mcp add --transport http vaaya https://vaaya.ai/mcp
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

Hosted action/payment gateway with local shim, live catalog discovery, OAuth, `consult/use/result`, per-call ceilings, prepaid/x402/MPP rails and broad service actions.

Capability: Finance & Payments
Resource type: Gateway
Industry: Financial Services & Investing
Best fit: Budgeted pay-per-call access to many external agent services with explicit spend ceilings.

Representative uses

Plan/execute paid search, scraping, research, browser, compute, media or email calls
Enforce `max_cost_cents`
Run/close metered sandboxes
Use commerce tools
Quote/buy supported tokenized shares where enabled

Limitations

Prices, availability and tool surface are live.
External actions can spend money or contact third parties.
Share purchases require supported tickers, stock permission and prepaid funds.
Detailed retention was not established.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: OAuth grants/API tokens/payment rails.
Permissions: Potentially broad external-service, connected-account, commerce and financial-action authority.
Data handling: Queries/outputs/payment metadata and connected-account data pass through Vaaya; vendor keys/upstream URLs are not exposed to the agent.
Cost: usage_based
Risk and cautions: Action/payment gateway with real spending and third-party effects; budget ceilings do not replace user authorization.

Access scope and cautions

Write actions: Send email Run browser/compute/media jobs Create CRM/sheet/calendar records Buy products/bookings Create automations Use metered sandboxes Buy supported tokenized shares
Sensitive access: Connected accounts Contact/lead data Email Balances/purchases Financial transactions Browser sessions
Risk level: high
Security notes: OAuth/PKCE, revocation, local credential file mode 0600 and failed-call no-charge claims are documented.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Plan/execute paid search, scraping, research, browser, compute, media or email calls; Enforce `max_cost_cents`; Run/close metered sandboxes; Use commerce tools; Quote/buy supported tokenized shares where enabled.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @vaaya/mcp. Recorded endpoint: https://vaaya.ai/mcp. Recorded transport: stdio, streamable_http. Recorded environment-variable notes: VAAYA_BACKEND_URL (optional); VAAYA_DEBUG (optional); VAAYA_NON_INTERACTIVE (optional). No configuration values are supplied here. Prerequisites: MCP client; Vaaya account/grant; funded balance/payment rail for paid calls. Client notes: Use `consult` before `use`; enforce `max_cost_cents`; close metered sessions and revoke access when done. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: OAuth 2.1 with PKCE/DCR; REST/bearer and payment-rail paths also documented.

Can it modify data or perform write operations?

Documented write actions include: Send email; Run browser/compute/media jobs; Create CRM/sheet/calendar records; Buy products/bookings; Create automations; Use metered sandboxes; Buy supported tokenized shares. Recorded permission boundary: Potentially broad external-service, connected-account, commerce and financial-action authority.

What data-handling boundary should I consider?

Queries/outputs/payment metadata and connected-account data pass through Vaaya; vendor keys/upstream URLs are not exposed to the agent. Recorded sensitive-access context: Connected accounts; Contact/lead data; Email; Balances/purchases; Financial transactions; Browser sessions.

What limitations and risks should I check before use?

Action/payment gateway with real spending and third-party effects; budget ceilings do not replace user authorization. Prices, availability and tool surface are live. External actions can spend money or contact third parties. Share purchases require supported tickers, stock permission and prepaid funds. Detailed retention was not established. OAuth/PKCE, revocation, local credential file mode 0600 and failed-call no-charge claims are documented. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Vaaya is listed as First-party MCP in MCP100’s current evidence.