Sec Edgar MCP
A SEC EDGAR MCP (Model Context Protocol) Server
Is Sec Edgar MCP safe? Strong public trust posture, backed by multiple independent signals.
Compare Sec Edgar MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Sec Edgar MCP scores 75.4/100 (Grade B), ranked #262 of 1374 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.1/10; 66% of recent commits are signed; no published advisory affects its latest release (sec-edgar-mcp); last pushed 2026-11-01. Every point is earned from checkable signals — never paid placement. How scoring works →
How Sec Edgar 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.
- Raise the OSSF Scorecard from 5.1 to 9.0lowest checks: CII-Best-Practices 0, Fuzzing 0, Pinned-Dependencies 0 +8.2 → 83.6 A · #51 of 778
- Sign every commit66% signed today +1.7 → 77.1 B · #136 of 778
Chain of custody
Scanners check what the code says. This traces who ships Sec Edgar 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 Partly signed
github.com/stefanoamorelli/sec-edgar-mcp, AGPL-3.0, last pushed 2026-11-01. 66% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 5.1/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:
- Code Review2
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 9CII-Best-Practices 0Code-Review 2Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 10Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 0SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages Linked and attested
- PyPI sec-edgar-mcp Source link points back to this repo Build provenance attested
-
What you install today No known advisories
Latest release checked: sec-edgar-mcp 1.1.0. No published advisory affects it (OSV, checked 2026-11-09).
Changes to this chain
- 2026-09-23 Package provenance attestation detected
- 2026-09-03 OSSF Scorecard: 5.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 Sec Edgar 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.
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 Sec Edgar MCP compares in MCP Servers
- #150 Code Index MCP 75.5 +0.1
- #151 Oxylabs MCP 75.5 +0.1
- #152 Sec Edgar MCP 75.4 this agent
- #153 Cronometer Api MCP 75.4 ±0
- #154 ITASCA MCP Server 75.3 −0.1
Bars show each HVTrust score; the tick marks Sec Edgar MCP’s 75.4.
Where the 75.4 comes from
HVTrust dimensions vs the MCP Servers average
75.4 / 100 · 100.0% confidenceSec Edgar MCP MCP Servers average (778 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
48.7 / 100Common questions about Sec Edgar MCP
Does Sec Edgar MCP publish package provenance?
Does Sec Edgar MCP have an OpenSSF Scorecard?
Is Sec Edgar MCP actively maintained?
What license does Sec Edgar MCP use?
Are Sec Edgar MCP's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Sec Edgar 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.
Maintain Sec Edgar MCP?
For maintainers
HVTrust scores Sec Edgar 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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/sec-edgar-mcp)
<a href="https://hvtracker.net/agents/sec-edgar-mcp"><img src="https://hvtracker.net/badge/sec-edgar-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
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