Klavis AI

Klavis AI: MCP integration platforms that let AI agents use tools reliably at any scale

Protocols & Tool Integration Python Grade D Listed Apache-2.0
48.3/100
Rank #480 of 1283
Compare Klavis AI

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 C · 2/5 signals
Last push
2026-06-01 · 75d ago
Recent change
Rank +3

Is Klavis AI safe? Klavis AI scores 48.3/100 (Grade D), ranked #480 of 1283 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 3.8/10; 97% of recent commits are signed; last pushed 2026-06-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-13
Rank Moved
Rank dropped 15 spots (#464 → #479)
2026-08-12
Rank Moved
Rank rose 12 spots (#476 → #464)
2026-08-10
Rank Moved
Rank dropped 18 spots (#458 → #476)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.8/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.
Refresh maintenance signals The repo was last pushed 75 days ago. Fresh activity helps separate stable projects from stale ones.
50.1
Activity sub-score · out of 100
#31

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 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-08-15 09:32 UTC · Repo last pushed 75 days ago

Rank Trend

2026-08-11 2026-08-15

Activity & Reach

Stars
5.8k
Forks
557
Last Push
2026-06-01
75 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
27
Rank Change
▼1
was #479

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

48.3 / 100 · 100.0% confidence

Klavis AI Protocols & Tool Integration average (57 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
9.6 / 25
1.0 above 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
11.7 / 17
in line with avg 11.4
Maintenance60% last-push freshness · 40% commit activity
7.0 / 20
6.8 below avg 13.8
AdoptionLog-scaled stars · package downloads
9.0 / 20
1.4 below avg 10.4

Activity Inputs

50.1 / 100
StarsRepository reach
22.6 / 30
FreshnessLast push recency
14.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.8 / 20

Supply Chain Trust

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

Is Klavis AI safe?

Public trust evidence for Klavis AI 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 Klavis AI publish package provenance?
No published build provenance is currently detected for Klavis AI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Klavis AI have an OpenSSF Scorecard?
Klavis AI has an OpenSSF Scorecard score of 3.8/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 Klavis AI actively maintained?
Slowing down. Last push was 75 days ago — keep an eye on whether activity resumes.
What license does Klavis AI use?
Klavis AI ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Klavis AI's commits signed?
97% of the last 100 commits to Klavis AI 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
Klavis AI appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
4 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high 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 Klavis AI?

For maintainers

HVTrust scores Klavis AI 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 5Grade 2Listed 1HVTrust 1Scorecard 1
2026-08-13
Rank Moved
Rank dropped 15 spots (#464 → #479)
2026-08-12
Rank Moved
Rank rose 12 spots (#476 → #464)
2026-08-10
Rank Moved
Rank dropped 18 spots (#458 → #476)
2026-08-08
Rank Moved
Rank dropped 115 spots (#338 → #453)
2026-08-04
Grade Changed
Trust grade C → D
2026-07-15
Scorecard Added
OSSF Scorecard: 4.5/10
2026-07-15
Grade Changed
Trust grade D → C
2026-07-15
Rank Moved
Rank rose 120 spots (#402 → #282)
2026-07-15
HVTrust Changed
HVTrust up 30.5pts (21.9 → 52.4)
2026-07-14
Newly Listed
First tracked at rank #402

Embed Badge Badge guide for maintainers →

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