Is Polymarket Agent MCP safe to use?

Polymarket Agent MCP has an HVTrust score of 71.8/100 (Grade B), ranked #296 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Polymarket Agent MCP?

Polymarket Agent MCP scores 71.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 16 GitHub stars and is categorized under MCP Servers.

Polymarket Agent MCP

demwick/polymarket-agent-mcp

The most comprehensive MCP server for Polymarket — 48 tools spanning direct trading, market discovery, smart money tracking, copy trading, backtesting, risk management, and portfolio optimization. Works with Claude Code, Cursor, or any MCP-compatible client.

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 5.7 / 10

Provenance Attested

Signed commits 52%

Last push 2d ago

Compare Polymarket Agent MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Polymarket Agent MCP scores 71.8/100 (Grade B), ranked #296 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 5.7/10; 52% of recent commits are signed; last pushed 2026-09-24. Every point is earned from checkable signals — never paid placement. How scoring works →

How Polymarket Agent MCP compares in MCP Servers

#173 Sentry MCP 71.9 +0.1
#174 Search1API 71.9 +0.1
#175 Polymarket Agent MCP 71.8 this agent
#176 Tavily MCP 71.7 −0.1
#177 Firecrawl MCP Server 71.7 −0.1

Bars show each HVTrust score; the tick marks Polymarket Agent MCP’s 71.8.

Where the 71.8 comes from

HVTrust dimensions vs the MCP Servers average

71.8 / 100 · 100.0% confidence

Polymarket Agent MCP MCP Servers average (775 agents)

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

17.2 / 25

6.9 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.3 / 17

1.1 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.9 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

5.4 / 20

1.8 below avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

Maintainer Checklist

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

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

36.0

Activity sub-score · out of 100

#175

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 B 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-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-24

2 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #298

Analysis

Activity Inputs

36.0 / 100

StarsRepository reach

7.4 / 30

FreshnessLast push recency

24.7 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

3.9 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

5.7 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

52%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 5

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 10

License 10

Maintained 2

Packaging 10

Pinned-Dependencies 10

SAST 9

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 0

Common questions about Polymarket Agent MCP

Polymarket Agent 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 Polymarket Agent MCP publish package provenance?

Yes. Polymarket Agent MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Polymarket Agent MCP have an OpenSSF Scorecard?

Polymarket Agent MCP has an OpenSSF Scorecard score of 5.7/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 Polymarket Agent MCP actively maintained?

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

What license does Polymarket Agent MCP use?

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

Are Polymarket Agent MCP's commits signed?

52% of the last 100 commits to Polymarket Agent 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

Polymarket Agent MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

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

Tool / Plugin Surface

None detected

No clear plugin system or broad tool 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 Polymarket Agent 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

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Polymarket Agent MCP?

For maintainers

HVTrust scores Polymarket Agent 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-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 700 spots (#998 → #298)

2026-09-23

HVTrust Changed

HVTrust up 46.6pts (24.9 → 71.5)

2026-09-22

Newly Listed

First tracked at rank #998

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Rank Moved

Rank rose 10 spots (#300 → #290)

2026-09-08

Rank Moved

Rank dropped 11 spots (#262 → #273)

2026-09-07

Rank Moved

Rank dropped 23 spots (#239 → #262)

2026-09-06

Rank Moved

Rank dropped 19 spots (#220 → #239)

2026-09-06

Activity Score Changed

Activity score down 8pts (43 → 35)

2026-09-05

Rank Moved

Rank dropped 53 spots (#167 → #220)

2026-09-03

Rank Moved

Rank dropped 14 spots (#147 → #161)

2026-08-31

Rank Moved

Rank dropped 17 spots (#118 → #135)

2026-08-26

Rank Moved

Rank dropped 15 spots (#98 → #113)

2026-08-10

Newly Listed

First tracked at rank #92

GitHub → npm: polymarket-agent-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/polymarket-agent-mcp.svg)](https://hvtracker.net/agents/polymarket-agent-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/polymarket-agent-mcp"><img src="https://hvtracker.net/badge/polymarket-agent-mcp.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