Runapi Ai MCP

RunAPI MCP server for model discovery, pricing lookup, media task creation, and balance checks.

MCP Servers TypeScript Grade C Listed Apache-2.0
54.4/100
Rank #768 of 1328
Compare Runapi Ai MCP

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-09-07 · 1d ago
Recent change
Grade Changed +8

Is Runapi Ai MCP safe? Runapi Ai MCP scores 54.4/100 (Grade C), ranked #768 of 1328 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 4.3/10; recent commits are unsigned; last pushed 2026-09-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 421 spots (#1181 → #760)
2026-09-07
HVTrust Changed
HVTrust up 18.9pts (35.6 → 54.5)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.3/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.
47.3
Activity sub-score · out of 100
#418

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-08 16:17 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars
55
Forks
0
Last Push
2026-09-07
yesterday
Commits (4 wk)
8?
Downloads (7d)
291
npm
HN mentions (30d)
Open Issues
2
Rank Change
▼8
was #760

Analysis

HVTrust Dimensions vs MCP Servers

54.4 / 100 · 100.0% confidence

Runapi Ai MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.4 / 25
4.5 below avg 9.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.0
Maintenance60% last-push freshness · 40% commit activity
13.8 / 20
1.6 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.5 / 20
0.6 above avg 6.9

Activity Inputs

47.3 / 100
StarsRepository reach
10.5 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
11.9 / 25
CommunityFork signal
0.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.3 / 10
OpenSSF Scorecard · scanned Sep 6, 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 3
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 6
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 10
Vulnerabilities 0

Is Runapi Ai MCP safe?

Public trust evidence for Runapi Ai MCP 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 Runapi Ai MCP publish package provenance?
No published build provenance is currently detected for Runapi Ai 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 Runapi Ai MCP have an OpenSSF Scorecard?
Runapi Ai MCP has an OpenSSF Scorecard score of 4.3/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 Runapi Ai MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Runapi Ai MCP use?
Runapi Ai MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Runapi Ai MCP's commits signed?
0% of the last 100 commits to Runapi Ai 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
Runapi Ai MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
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

Maintain Runapi Ai MCP?

For maintainers

HVTrust scores Runapi Ai 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
Rank 19HVTrust 2Listed 1Scorecard 1Grade 1
2026-09-07
Grade Changed
Trust grade D → C
2026-09-07
Rank Moved
Rank rose 421 spots (#1181 → #760)
2026-09-07
HVTrust Changed
HVTrust up 18.9pts (35.6 → 54.5)
2026-09-06
Rank Moved
Rank rose 10 spots (#1191 → #1181)
2026-09-05
Rank Moved
Rank dropped 36 spots (#1155 → #1191)
2026-09-04
Rank Moved
Rank dropped 31 spots (#1124 → #1155)
2026-09-03
Rank Moved
Rank dropped 53 spots (#1071 → #1124)
2026-09-02
Rank Moved
Rank dropped 43 spots (#1028 → #1071)
2026-09-01
Rank Moved
Rank dropped 43 spots (#985 → #1028)
2026-08-31
Scorecard Added
OSSF Scorecard: 3.5/10
2026-08-31
Rank Moved
Rank rose 218 spots (#1203 → #985)
2026-08-31
HVTrust Changed
HVTrust up 15.3pts (20.4 → 35.7)
2026-08-30
Rank Moved
Rank dropped 22 spots (#1181 → #1203)
2026-08-29
Rank Moved
Rank dropped 26 spots (#1155 → #1181)
2026-08-28
Rank Moved
Rank dropped 23 spots (#1132 → #1155)
2026-08-27
Rank Moved
Rank dropped 25 spots (#1107 → #1132)
2026-08-26
Rank Moved
Rank dropped 68 spots (#1039 → #1107)
2026-08-25
Rank Moved
Rank rose 12 spots (#1051 → #1039)
2026-08-24
Rank Moved
Rank dropped 11 spots (#1040 → #1051)
2026-08-17
Rank Moved
Rank rose 14 spots (#1048 → #1034)
2026-08-16
Rank Moved
Rank dropped 32 spots (#1016 → #1048)
2026-08-12
Rank Moved
Rank rose 16 spots (#1024 → #1008)
2026-08-10
Rank Moved
Rank dropped 54 spots (#968 → #1022)
2026-08-08
Newly Listed
First tracked at rank #964

Embed Badge Badge guide for maintainers →

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