updated 2026-08-12 05:02 UTC

Jarvis Registry

ascending-llc/jarvis-registry

Connect any AI copilot or autonomous agent to your enterprise tools — through a single, secure MCP/Agent gateway with bu

Protocols & Tool Integration Python Grade D Listed Apache-2.0
26.5/100
Rank #802 of 1283
Compare Jarvis Registry

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-12 · 0d ago
Recent change
New

Is Jarvis Registry safe? Jarvis Registry scores 26.5/100 (Grade D), ranked #802 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 99% of recent commits are signed; last pushed 2026-08-12. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#39 wcgw — 34.3 (D) → #40 ToolHive — 27.8 (D) → #42 MCP Context Forge — 26.1 (D) → #43 open-connector — 26.0 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Newly Listed
First tracked at rank #803
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 Jarvis Registry View Protocols & Tool Integration Report missing data
79.8
Activity sub-score · out of 100
#41
In Protocols & Tool Integration

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed today

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
2.8k
Forks
433
Last Push
2026-08-12
today
Commits (4 wk)
55
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▲1
was #803

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

26.5 / 100 · 50.0% confidence

Jarvis Registry Protocols & Tool Integration average (57 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.0 / 25
3.6 below avg 8.6
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.9 below avg 11.7
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
2.9 below avg 11.4
Maintenance60% last-push freshness · 40% commit activity
19.0 / 20
5.2 above avg 13.8
AdoptionLog-scaled stars · package downloads
8.3 / 20
2.1 below avg 10.4

Activity Inputs

79.8 / 100
StarsRepository reach
20.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
21.8 / 25
CommunityFork signal
12.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
99%
of last 100 commits verified

Is Jarvis Registry safe?

Public trust evidence for Jarvis Registry 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 Jarvis Registry publish package provenance?
No published build provenance is currently detected for Jarvis Registry. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Jarvis Registry have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Jarvis Registry. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Jarvis Registry actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Jarvis Registry use?
Jarvis Registry ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Jarvis Registry's commits signed?
99% of the last 100 commits to Jarvis Registry 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
Jarvis Registry appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Jarvis Registry?

For maintainers

HVTrust scores Jarvis Registry 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
Listed 1
2026-08-10
Newly Listed
First tracked at rank #803
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 26.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/jarvis-registry.svg)](https://hvtracker.net/agents/jarvis-registry)
HTML:
<a href="https://hvtracker.net/agents/jarvis-registry"><img src="https://hvtracker.net/badge/jarvis-registry.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON