Is Vaaya safe to use?

Vaaya has an HVTrust score of 35.7/100 (Grade D), ranked #1123 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Vaaya?

Vaaya scores 35.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 42 GitHub stars and is categorized under MCP Servers.

Vaaya

vaaya-ai/vaaya-mcp

Vaaya MCP server — pay-per-call agent superpowers: media & video generation, product demo videos, web search & scraping,

MCP Servers JavaScript Grade D Listed MIT

35.7/100

Rank #1123 of 1320

Compare Vaaya

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-03 · 1d ago

Recent change

Rank +6

Is Vaaya safe? Vaaya scores 35.7/100 (Grade D), ranked #1123 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.9/10; 15% of recent commits are signed; last pushed 2026-09-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#644 spreadsheet-kit MCP — 35.9 (D) → #645 ByteAsk Embedded MCP — 35.8 (D) → #647 Clio MCP — 35.7 (D) → #648 MCP Apple Music — 35.6 (D) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-03

Rank Moved

Rank dropped 42 spots (#1075 → #1117)

2026-09-02

Rank Moved

Rank dropped 43 spots (#1032 → #1075)

2026-09-01

Rank Moved

Rank dropped 44 spots (#988 → #1032)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.9/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Vaaya View MCP Servers Report missing data

49.5

Activity sub-score · out of 100

#646

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars

Forks

Last Push

2026-09-03

yesterday

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▼6

was #1117

Analysis

HVTrust Dimensions vs MCP Servers

35.7 / 100 · 67.0% confidence

Vaaya MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

5.6 / 25

3.9 below avg 9.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.8 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

13.6 / 20

1.4 above avg 12.2

AdoptionLog-scaled stars · package downloads

3.9 / 20

2.3 below avg 6.2

Activity Inputs

49.5 / 100

StarsRepository reach

9.8 / 30

FreshnessLast push recency

24.9 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

4.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.9 / 10

OpenSSF Scorecard · scanned Sep 4, 2026

Signed Commits

15%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 1

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging -1

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 10

Vulnerabilities 10

Is Vaaya safe?

Public trust evidence for Vaaya is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Vaaya publish package provenance?

No published build provenance is currently detected for Vaaya. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Vaaya have an OpenSSF Scorecard?

Vaaya has an OpenSSF Scorecard score of 3.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Vaaya actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Vaaya use?

Vaaya ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Vaaya's commits signed?

15% of the last 100 commits to Vaaya are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Vaaya appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

2 detected

Public provider/service dependencies detected.

Credential signal: No explicit API-key/config marker detected.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

Maintain Vaaya?

For maintainers

HVTrust scores Vaaya from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-03

Rank Moved

Rank dropped 42 spots (#1075 → #1117)

2026-09-02

Rank Moved

Rank dropped 43 spots (#1032 → #1075)

2026-09-01

Rank Moved

Rank dropped 44 spots (#988 → #1032)

2026-08-31

Rank Moved

Rank dropped 35 spots (#953 → #988)

2026-08-30

Rank Moved

Rank dropped 42 spots (#911 → #953)

2026-08-29

Rank Moved

Rank dropped 51 spots (#860 → #911)

2026-08-28

Rank Moved

Rank dropped 29 spots (#831 → #860)

2026-08-27

Rank Moved

Rank dropped 20 spots (#811 → #831)

2026-08-26

Scorecard Added

OSSF Scorecard: 3.9/10

2026-08-26

Rank Moved

Rank rose 262 spots (#1073 → #811)

2026-08-26

HVTrust Changed

HVTrust up 15.4pts (20.2 → 35.6)

2026-08-25

Rank Moved

Rank rose 39 spots (#1112 → #1073)

2026-08-25

Activity Score Changed

Activity score up 7pts (40 → 48)

2026-08-16

Rank Moved

Rank dropped 31 spots (#1061 → #1092)

2026-08-13

Rank Moved

Rank dropped 10 spots (#1055 → #1065)

2026-08-12

Rank Moved

Rank rose 12 spots (#1067 → #1055)

2026-08-10

Rank Moved

Rank dropped 61 spots (#1001 → #1062)

2026-08-08

Newly Listed

First tracked at rank #990

GitHub → npm: @vaaya/mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/vaaya.svg)](https://hvtracker.net/agents/vaaya)
            
HTML:
            <a href="https://hvtracker.net/agents/vaaya"><img src="https://hvtracker.net/badge/vaaya.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON