@vaaya/mcp

MCP@MaruPelkarlive
v0.6.8UnknownMITUpdated 18d agonpmGitHub

Pay for APIs and buy supported tokenized shares with prepaid funds. Search, research, media, data, compute and more through one Vaaya account. Agent purchase and Instinct funding guide: https://vaaya.ai/llms.txt

Endpoint healthlive
checked 1 day ago · 296ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

@MaruPelkar
Identity-verified publisher GitHub@MaruPelkar
Verified Jul 6, 2026
197Downloads/wk
43GitHub stars
7Forks
18d agoLast update
Package
AuthorUnknown
LicenseMIT
Version0.6.8
Sourcenpm+mcp-registry
npm@vaaya/mcp
GitHubvaaya-ai/vaaya-mcp
SBOMCycloneDX 1.6 ↓
Trust Status
A
80/100Trusted
✓Listed in Forge index+10/10
✓Publisher identity verified+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
Publisher@MaruPelkar
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface2 tools · none privileged
Security scan✓ Cleanv0.6.5 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 4, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

2 tools · none privileged
Statically extracted from the published packagev0.6.5 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

logoutDisconnect this Vaaya connection — deletes local credentials.

Disconnect this Vaaya connection — deletes local credentials.

No input schema was published for this tool.

reauthorizeRe-run the authorization flow against the Vaaya backend.

Re-run the authorization flow against the Vaaya backend.

No input schema was published for this tool.

2 of 2 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Pay for APIs and buy supported tokenized shares with prepaid funds. Search, research, media, data, compute and more through one Vaaya account. Agent purchase and Instinct funding guide: https://vaaya.ai/llms.txt

Keywords
mcpmcp-servermodel-context-protocolmodelcontextprotocolai-agentsimage-generationvideo-generationproduct-demoweb-scrapingweb-searchdeep-researchmarket-researchlead-enrichmentgtmsalesbrowser-automationcode-sandboxagent-paymentsx402micropaymentscursorclaudeclaude-codecodexagent-walletspend-limitpay-per-callmcp-paymentstokenized-stocksprepaidinstinct
Alternatives
Comparing tool surfaces…

Tools exposed

2 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-28 — observed resolution, not a publisher declaration.

60 packages resolved · 5 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

62 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+50 more not listed. The counts by reason above cover all of them.

Not followed: optionalDependencies, peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in search & retrieval