updated 2026-09-26 06:32 UTC

Waggle MCP

Abhigyan-Shekhar/Waggle-mcp

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.1 / 10
Provenance None
Signed commits 85%
Last push yesterday
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 63.0/100 (Grade C), ranked #534 of 1325 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.1/10; 85% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Waggle MCP compares in MCP Servers

  1. #301 Appwrite MCP 63.1 +0.1
  2. #302 MCP Server Kalshi 63.1 +0.1
  3. #303 Waggle MCP 63.0 this agent
  4. #304 Unreal MCP 63.0 ±0
  5. #305 Yazio MCP 63.0 ±0

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

Where the 63.0 comes from

HVTrust dimensions vs the MCP Servers average

63.0 / 100 · 100.0% confidence

Waggle MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.9 / 25
1.6 above avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
13.7 / 17
1.5 above avg 12.2
Maintenance60% last-push freshness · 40% commit activity
17.2 / 20
5.1 above avg 12.1
AdoptionLog-scaled stars · package downloads
5.2 / 20
2.0 below avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.1/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 Get email alerts for Waggle MCP View MCP Servers Report missing data
61.5
Activity sub-score · out of 100
#303
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 →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
44
Forks
144
Last Push
2026-09-25
yesterday
Commits (4 wk)
20
Downloads (7d)
7
pypi
HN mentions (30d)
—
Open Issues
173
Rank Change
▼1
was #533

Analysis

Activity Inputs

61.5 / 100
StarsRepository reach
9.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
16.5 / 25
CommunityFork signal
10.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
6.1 / 10
OpenSSF Scorecard · scanned Sep 25, 2026
Signed Commits
85%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 8
CI-Tests 10
CII-Best-Practices 0
Code-Review 6
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

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.1/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?
Actively maintained. The repository was pushed to within the last 1 day(s).
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?
85% 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
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared

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
Rank 21Listed 2Surface 2HVTrust 2Grade 2Scorecard 1Delisted 1MCP 1Surface 1
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)
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: marketplace → declared
2026-08-12
Rank Moved
Rank rose 18 spots (#710 → #692)
2026-08-10
Rank Moved
Rank dropped 28 spots (#681 → #709)
2026-08-08
Newly Listed
First tracked at rank #888
GitHub → PyPI: waggle-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.0 Grade C
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.3 · Raw JSON