Scriptivox MCP Server

MCP Servers TypeScript Listed MIT

Is Scriptivox MCP Server safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.9 / 10
Provenance None
Signed commits 0%
Last push 29d ago
Compare Scriptivox MCP Server
Suggest a correction

In detail: Scriptivox MCP Server scores 50.0/100 (Grade C), ranked #936 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 2.9/10; recent commits are unsigned; last pushed 2026-08-28. Every point is earned from checkable signals — never paid placement. How scoring works →

How Scriptivox MCP Server compares in MCP Servers

  1. #535 Markdownify MCP 50.1 +0.1
  2. #536 fastctx 50.0 ±0
  3. #537 Scriptivox MCP Server 50.0 this agent
  4. #538 ConnectWise Manage 49.9 −0.1
  5. #539 Danishashko Yahoo Finance 49.9 −0.1

Bars show each HVTrust score; the tick marks Scriptivox MCP Server’s 50.0.

Where the 50.0 comes from

HVTrust dimensions vs the MCP Servers average

50.0 / 100 · 100.0% confidence

Scriptivox MCP Server MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
3.6 / 25
6.7 below 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
11.0 / 17
1.2 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
12.9 / 20
0.8 above avg 12.1
AdoptionLog-scaled stars · package downloads
6.7 / 20
0.5 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 dropped 18 spots (#920 → #938)
2026-09-24
Grade Changed
Trust grade D → C
2026-09-24
Rank Moved
Rank rose 34 spots (#954 → #920)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.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.
36.3
Activity sub-score · out of 100
#537

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 29 days ago

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
11
Forks
0
Last Push
2026-08-28
29 days ago
Commits (4 wk)
4
Downloads (7d)
1,158
npm+docker
HN mentions (30d)
—
Open Issues
0
Rank Change
▲2
was #938

Analysis

Activity Inputs

36.3 / 100
StarsRepository reach
6.5 / 30
FreshnessLast push recency
21.0 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
0.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
2.9 / 10
OpenSSF Scorecard · scanned Sep 26, 2026
Signed Commits
0%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 5
Packaging -1
Pinned-Dependencies 5
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 0

Common questions about Scriptivox MCP Server

Public trust evidence for Scriptivox MCP Server 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 Scriptivox MCP Server publish package provenance?
No published build provenance is currently detected for Scriptivox MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Scriptivox MCP Server have an OpenSSF Scorecard?
Scriptivox MCP Server has an OpenSSF Scorecard score of 2.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 Scriptivox MCP Server actively maintained?
Maintained. Last push was 29 days ago.
What license does Scriptivox MCP Server use?
Scriptivox MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Scriptivox MCP Server's commits signed?
0% of the last 100 commits to Scriptivox MCP Server 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
Scriptivox MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
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 Scriptivox MCP Server'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-08-25
Activity Resumed
Activity resumed
2026-08-21
Activity Went Stale
No commits for 90 days

Maintain Scriptivox MCP Server?

For maintainers

HVTrust scores Scriptivox MCP Server 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
Rank 23HVTrust 5Grade 5Listed 2Score 2Stale 1Fresh 1Scorecard 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank dropped 18 spots (#920 → #938)
2026-09-24
Grade Changed
Trust grade D → C
2026-09-24
Rank Moved
Rank rose 34 spots (#954 → #920)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 143 spots (#1097 → #954)
2026-09-23
HVTrust Changed
HVTrust up 26.8pts (22.3 → 49.1)
2026-09-22
Newly Listed
First tracked at rank #1097
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Grade Changed
Trust grade C → D
2026-09-11
Rank Moved
Rank dropped 10 spots (#900 → #910)
2026-09-09
Rank Moved
Rank dropped 22 spots (#871 → #893)
2026-09-08
Rank Moved
Rank dropped 10 spots (#861 → #871)
2026-09-07
Rank Moved
Rank dropped 31 spots (#830 → #861)
2026-09-06
Grade Changed
Trust grade D → C
2026-09-06
Rank Moved
Rank rose 33 spots (#863 → #830)
2026-09-05
Rank Moved
Rank rose 321 spots (#1184 → #863)
2026-09-05
HVTrust Changed
HVTrust up 16.4pts (32.7 → 49.1)
2026-09-04
Rank Moved
Rank dropped 16 spots (#1168 → #1184)
2026-09-03
Grade Changed
Trust grade C → D
2026-09-03
Rank Moved
Rank dropped 490 spots (#678 → #1168)
2026-09-03
HVTrust Changed
HVTrust down 18.4pts (51.1 → 32.7)
2026-09-02
Rank Moved
Rank dropped 30 spots (#648 → #678)
2026-09-01
Rank Moved
Rank dropped 24 spots (#624 → #648)
2026-08-31
Scorecard Added
OSSF Scorecard: 2.9/10
2026-08-31
Grade Changed
Trust grade D → C
2026-08-31
Rank Moved
Rank rose 403 spots (#1027 → #624)
2026-08-31
HVTrust Changed
HVTrust up 19.4pts (31.8 → 51.2)
2026-08-30
Rank Moved
Rank dropped 54 spots (#973 → #1027)
2026-08-29
Rank Moved
Rank dropped 50 spots (#923 → #973)
2026-08-28
Rank Moved
Rank dropped 32 spots (#891 → #923)
2026-08-27
Activity Score Changed
Activity score up 5pts (38 → 43)
2026-08-26
Rank Moved
Rank dropped 108 spots (#774 → #882)
2026-08-25
Activity Resumed
Activity resumed
2026-08-25
Rank Moved
Rank rose 61 spots (#835 → #774)
2026-08-25
HVTrust Changed
HVTrust up 5.4pts (25.3 → 30.7)
2026-08-25
Activity Score Changed
Activity score up 19pts (19 → 38)
2026-08-24
Rank Moved
Rank dropped 10 spots (#825 → #835)
2026-08-21
Activity Went Stale
No commits for 90 days
2026-08-19
Rank Moved
Rank dropped 11 spots (#825 → #836)
2026-08-16
Rank Moved
Rank dropped 16 spots (#817 → #833)
2026-08-10
Rank Moved
Rank dropped 46 spots (#768 → #814)
2026-08-08
Newly Listed
First tracked at rank #757

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 50.0 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/scriptivox-mcp-server.svg)](https://hvtracker.net/agents/scriptivox-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/scriptivox-mcp-server"><img src="https://hvtracker.net/badge/scriptivox-mcp-server.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