Is Waggle MCP safe to use?

Waggle MCP has an HVTrust score of 58.9/100 (Grade C), ranked #723 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Waggle MCP?

Waggle MCP scores 58.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 45 GitHub stars and is categorized under MCP Servers.

Waggle MCP

Repository

MCP server for external memory layer for AI agents + more . Download from pypi , and get started

MCP Servers Python Listed Apache-2.0

Is Waggle MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.2 / 10

Provenance None

Signed commits 87%

Last push 11d ago

Advisories None known

Compare Waggle MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Waggle MCP scores 58.9/100 (Grade C), ranked #723 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 6.2/10; 87% of recent commits are signed; no published advisory affects its latest release (waggle-mcp); last pushed 2026-10-30. Every point is earned from checkable signals — never paid placement. How scoring works →

How Waggle MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.7 → 73.6 B · #172 of 778
Raise the OSSF Scorecard from 6.2 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Signed-Releases 0 +5.8 → 64.7 C · #309 of 778
Sign every commit87% signed today +0.7 → 59.6 C · #385 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Waggle MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/Abhigyan-Shekhar/Waggle-mcp, Apache-2.0, last pushed 2026-10-30. 87% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 6.2/10 (scanned Nov 10, 2026). The checks that decide who can get a change released:
- Code Review8
- Branch Protection8
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies5
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 8

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 5

SAST 10

Security-Policy 4

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0
Published packages Linked, not attested
- PyPI waggle-mcp Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
What you install today No known advisories

Latest release checked: waggle-mcp 0.0.1. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

2026-08-26 OSSF Scorecard: 6.1/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

GitHub repository data
Package downloads
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Waggle MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Waggle MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Waggle MCP’s 58.9.

Where the 58.9 comes from

HVTrust dimensions vs the MCP Servers average

58.9 / 100 · 100.0% confidence

Waggle MCP MCP Servers average (778 agents)

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

12.1 / 25

1.3 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.8 / 17

1.5 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

12.5 / 20

in line with avg 12.2

AdoptionLog-scaled stars · package downloads

5.5 / 20

2.1 below avg 7.6

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-11-08

Rank Moved

Rank rose 21 spots (#740 → #719)

2026-11-07

Rank Moved

Rank dropped 23 spots (#717 → #740)

2026-11-06

Rank Moved

Rank dropped 19 spots (#698 → #717)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.2/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.

Compare with another agent View MCP Servers Report missing data

47.4

Activity sub-score · out of 100

#392

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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

138

Last Push

2026-10-30

11 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

171

Rank Change

▲2

was #725

Analysis

Activity Inputs

47.4 / 100

StarsRepository reach

10.0 / 30

FreshnessLast push recency

23.5 / 25

ActivityRecent commits

3.8 / 25

CommunityFork signal

10.0 / 20

Common questions about Waggle MCP

Waggle MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Waggle MCP publish package provenance?

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

Does Waggle MCP have an OpenSSF Scorecard?

Waggle MCP has an OpenSSF Scorecard score of 6.2/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 Waggle MCP actively maintained?

Maintained. Last push was 11 days ago.

What license does Waggle MCP use?

Waggle MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Waggle MCP's commits signed?

87% of the last 100 commits to Waggle MCP 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

Waggle MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

4 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

How this surface has changed

Detected changes to Waggle MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, E2B, Google Gemini, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Waggle MCP?

For maintainers

HVTrust scores Waggle MCP 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-11-08

Rank Moved

Rank rose 21 spots (#740 → #719)

2026-11-07

Rank Moved

Rank dropped 23 spots (#717 → #740)

2026-11-06

Rank Moved

Rank dropped 19 spots (#698 → #717)

2026-10-25

Rank Moved

Rank dropped 92 spots (#583 → #675)

2026-10-23

Rank Moved

Rank rose 18 spots (#607 → #589)

2026-10-22

Rank Moved

Rank dropped 21 spots (#586 → #607)

2026-10-20

Rank Moved

Rank dropped 10 spots (#570 → #580)

2026-10-16

Rank Moved

Rank rose 19 spots (#573 → #554)

2026-10-14

Rank Moved

Rank dropped 10 spots (#558 → #568)

2026-10-11

Rank Moved

Rank dropped 11 spots (#544 → #555)

2026-10-07

Rank Moved

Rank rose 35 spots (#583 → #548)

2026-10-05

Rank Moved

Rank dropped 13 spots (#563 → #576)

2026-09-30

Rank Moved

Rank dropped 19 spots (#535 → #554)

2026-09-25

Rank Moved

Rank rose 30 spots (#563 → #533)

2026-09-24

Rank Moved

Rank rose 10 spots (#573 → #563)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Anthropic, E2B, Google Gemini, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 215 spots (#788 → #573)

2026-09-23

HVTrust Changed

HVTrust up 32.9pts (29.0 → 61.9)

2026-09-22

Newly Listed

First tracked at rank #788

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 28 spots (#532 → #560)

2026-09-17

Rank Moved

Rank rose 12 spots (#540 → #528)

2026-09-16

Rank Moved

Rank dropped 26 spots (#514 → #540)

2026-09-12

Rank Moved

Rank dropped 10 spots (#498 → #508)

2026-09-11

Rank Moved

Rank dropped 12 spots (#486 → #498)

2026-09-08

Rank Moved

Rank dropped 22 spots (#452 → #474)

2026-09-07

Rank Moved

Rank dropped 27 spots (#425 → #452)

2026-09-06

Rank Moved

Rank dropped 15 spots (#410 → #425)

2026-09-05

Rank Moved

Rank dropped 62 spots (#348 → #410)

2026-09-03

Rank Moved

Rank dropped 19 spots (#320 → #339)

2026-09-02

Rank Moved

Rank rose 13 spots (#333 → #320)

2026-09-01

Rank Moved

Rank dropped 10 spots (#323 → #333)

2026-08-31

Rank Moved

Rank dropped 37 spots (#286 → #323)

2026-08-29

Rank Moved

Rank dropped 12 spots (#277 → #289)

2026-08-26

Scorecard Added

OSSF Scorecard: 6.1/10

2026-08-26

Grade Changed

Trust grade D → C

2026-08-26

Rank Moved

Rank rose 437 spots (#705 → #268)

2026-08-26

HVTrust Changed

HVTrust up 28.6pts (35.7 → 64.3)

2026-08-16

Rank Moved

Rank dropped 13 spots (#687 → #700)

GitHub → PyPI: waggle-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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

Waggle MCP

How Waggle MCP could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages Linked, not attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Waggle MCP compares in MCP Servers

Where the 58.9 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Waggle MCP

AI agent surface

Maintain Waggle MCP?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers