updated 2026-09-26 06:32 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 built-in identity, access control, and full observability.

Protocols & Tool Integration Python Listed Apache-2.0

Is Jarvis Registry safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.5 / 10
Provenance None
Signed commits 99%
Last push yesterday
Compare Jarvis Registry

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

Pick any agent to compare →
Suggest a correction

In detail: Jarvis Registry scores 63.0/100 (Grade C), ranked #536 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.5/10; 99% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →

How Jarvis Registry compares in Protocols & Tool Integration

  1. #32 MCP Java SDK 63.5 +0.5
  2. #33 mcphub 63.4 +0.4
  3. #34 Jarvis Registry 63.0 this agent
  4. #35 CodeGraph 62.1 −0.9
  5. #36 MCP C# SDK 61.4 −1.6

Bars show each HVTrust score; the tick marks Jarvis Registry’s 63.0.

Where the 63.0 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

63.0 / 100 · 100.0% confidence

Jarvis Registry Protocols & Tool Integration average (61 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.6 / 25
in line with avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
0.6 below avg 12.9
Maintenance60% last-push freshness · 40% commit activity
18.9 / 20
4.8 above avg 14.1
AdoptionLog-scaled stars · package downloads
8.4 / 20
2.2 below avg 10.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Amazon Bedrock
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.5/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.
Compare with another agent Get email alerts for Jarvis Registry View Protocols & Tool Integration Report missing data
80.3
Activity sub-score · out of 100
#34
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 C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
3.1k
Forks
473
Last Push
2026-09-25
yesterday
Commits (4 wk)
56
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #536

Analysis

Activity Inputs

80.3 / 100
StarsRepository reach
21.0 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
21.9 / 25
CommunityFork signal
12.4 / 20

Supply Chain Trust

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

Common questions about Jarvis Registry

Jarvis Registry 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 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?
Jarvis Registry has an OpenSSF Scorecard score of 4.5/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 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
medium confidence
1 detected
Public provider/service dependencies 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
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
How this surface has changed

Detected changes to Jarvis Registry'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
Provider Added
Runtime surface grew — new detected provider dependency: Amazon Bedrock
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-19
Provider Removed
Runtime surface shrank — no longer detected: Multi-provider (LiteLLM)
2026-08-15
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none

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
Rank 13Listed 2Surface 2HVTrust 2Grade 2Surface 1Scorecard 1Delisted 1MCP 1Surface 1
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Amazon Bedrock
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank dropped 138 spots (#394 → #532)
2026-09-23
HVTrust Changed
HVTrust up 15.7pts (47.4 → 63.1)
2026-09-22
Newly Listed
First tracked at rank #394
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Provider Removed
Runtime surface shrank — no longer detected: Multi-provider (LiteLLM)
2026-09-19
Rank Moved
Rank rose 12 spots (#545 → #533)
2026-09-12
Rank Moved
Rank dropped 14 spots (#524 → #538)
2026-09-07
Rank Moved
Rank dropped 33 spots (#487 → #520)
2026-09-06
Rank Moved
Rank dropped 10 spots (#477 → #487)
2026-09-05
Rank Moved
Rank dropped 78 spots (#399 → #477)
2026-09-04
Rank Moved
Rank dropped 14 spots (#385 → #399)
2026-09-03
Rank Moved
Rank dropped 20 spots (#365 → #385)
2026-08-31
Rank Moved
Rank dropped 28 spots (#325 → #353)
2026-08-30
Rank Moved
Rank rose 13 spots (#338 → #325)
2026-08-27
Scorecard Added
OSSF Scorecard: 4.6/10
2026-08-27
Grade Changed
Trust grade D → C
2026-08-27
Rank Moved
Rank rose 598 spots (#923 → #325)
2026-08-27
HVTrust Changed
HVTrust up 35.2pts (27.1 → 62.3)
2026-08-26
Rank Moved
Rank dropped 110 spots (#813 → #923)
2026-08-16
Rank Moved
Rank dropped 15 spots (#799 → #814)
2026-08-15
Provider Removed
Runtime surface shrank — no longer detected: Anthropic
2026-08-12
Tool Surface Changed
Detected tool/plugin surface changed: declared → none
2026-08-10
Newly Listed
First tracked at rank #803
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 63.0 Grade C
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) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON