Is Ris MCP Ts safe to use?

Ris MCP Ts has an HVTrust score of 54.8/100 (Grade C), ranked #854 of 1374 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Ris MCP Ts?

Ris MCP Ts scores 54.8/100 on HVTracker's evidence-weighted HVTrust scale. It has 20 GitHub stars and is categorized under MCP Servers.

Ris MCP Ts

Repository

MCP Server for the Austrian Legal Information System (RIS) - Access Austrian federal laws, state laws, court decisions and more

MCP Servers TypeScript Listed MIT

Is Ris MCP Ts safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 6.2 / 10

Provenance None

Signed commits 82%

Last push 7d ago

Compare Ris MCP Ts

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Ris MCP Ts scores 54.8/100 (Grade C), ranked #854 of 1374 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 6.2/10; 82% of recent commits are signed; last pushed 2026-11-03. Every point is earned from checkable signals — never paid placement. How scoring works →

How Ris MCP Ts could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Raise the OSSF Scorecard from 6.2 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Contributors 0 +5.8 → 60.6 C · #375 of 778
Sign every commit82% signed today +1.0 → 55.8 C · #452 of 778

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Ris MCP Ts and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

Source Signed

github.com/Honeyfield-Org/ris-mcp-ts, MIT, last pushed 2026-11-03. 82% of the last 100 commits carry a verified signature, so changes trace to a verified account.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 6.2/10 (scanned Nov 1, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 9

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 0

SAST 9

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 9
Published packages None

No registry package. Ris MCP Ts is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

2026-08-29 OSSF Scorecard: 5.5/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

GitHub repository data
Package downloads (missing)
Supply-chain checks
Public actions (missing)
Community mentions (missing)

Verify this score yourself

Every build re-issues Ris MCP Ts’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Ris MCP Ts compares in MCP Servers

Bars show each HVTrust score; the tick marks Ris MCP Ts’s 54.8.

Where the 54.8 comes from

HVTrust dimensions vs the MCP Servers average

54.8 / 100 · 100.0% confidence

Ris MCP Ts MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

11.8 / 25

1.0 above avg 10.8

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.9 below avg 13.7

Transparency50% declared license · 50% OSSF Scorecard

13.8 / 17

1.5 above avg 12.3

Maintenance60% last-push freshness · 40% commit activity

13.2 / 20

1.0 above avg 12.2

AdoptionLog-scaled stars · package downloads

3.2 / 20

4.4 below avg 7.6

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-11-04

Rank Moved

Rank rose 25 spots (#870 → #845)

2026-11-02

Rank Moved

Rank rose 55 spots (#918 → #863)

2026-10-30

Rank Moved

Rank dropped 10 spots (#911 → #921)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.2/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 View MCP Servers Report missing data

45.9

Activity sub-score · out of 100

#473

In MCP Servers

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 →

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars

Forks

Last Push

2026-11-03

7 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #854

Analysis

Activity Inputs

45.9 / 100

StarsRepository reach

7.9 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

3.3 / 20

Common questions about Ris MCP Ts

Public trust evidence for Ris MCP Ts 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 Ris MCP Ts publish package provenance?

No published build provenance is currently detected for Ris MCP Ts. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Ris MCP Ts have an OpenSSF Scorecard?

Ris MCP Ts has an OpenSSF Scorecard score of 6.2/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 Ris MCP Ts actively maintained?

Actively maintained. The repository was pushed to within the last 7 day(s).

What license does Ris MCP Ts use?

Ris MCP Ts ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Ris MCP Ts's commits signed?

82% of the last 100 commits to Ris MCP Ts 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

Ris MCP Ts appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency 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 Ris MCP Ts'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

Maintain Ris MCP Ts?

For maintainers

HVTrust scores Ris MCP Ts 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

2026-11-04

Rank Moved

Rank rose 25 spots (#870 → #845)

2026-11-02

Rank Moved

Rank rose 55 spots (#918 → #863)

2026-10-30

Rank Moved

Rank dropped 10 spots (#911 → #921)

2026-10-28

Rank Moved

Rank dropped 50 spots (#864 → #914)

2026-10-27

Grade Changed

Trust grade D → C

2026-10-27

Rank Moved

Rank rose 190 spots (#1054 → #864)

2026-10-27

HVTrust Changed

HVTrust up 6.1pts (48.6 → 54.7)

2026-10-27

Activity Score Changed

Activity score up 16pts (29 → 44)

2026-10-15

Rank Moved

Rank dropped 10 spots (#1015 → #1025)

2026-10-11

Rank Moved

Rank dropped 12 spots (#988 → #1000)

2026-10-09

Rank Moved

Rank dropped 16 spots (#965 → #981)

2026-10-08

Grade Changed

Trust grade C → D

2026-10-08

Rank Moved

Rank dropped 113 spots (#852 → #965)

2026-10-08

HVTrust Changed

HVTrust down 3.7pts (53.5 → 49.8)

2026-10-08

Activity Score Changed

Activity score down 11pts (42 → 31)

2026-10-04

Rank Moved

Rank dropped 15 spots (#825 → #840)

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 283 spots (#506 → #789)

2026-09-23

HVTrust Changed

HVTrust up 14.2pts (40.6 → 54.8)

2026-09-22

Newly Listed

First tracked at rank #506

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Rank Moved

Rank rose 60 spots (#830 → #770)

2026-09-15

Rank Moved

Rank dropped 10 spots (#826 → #836)

2026-09-12

Rank Moved

Rank dropped 10 spots (#815 → #825)

2026-09-11

Rank Moved

Rank dropped 15 spots (#800 → #815)

2026-09-09

Rank Moved

Rank dropped 12 spots (#792 → #804)

2026-09-08

Rank Moved

Rank rose 34 spots (#826 → #792)

2026-09-08

Activity Score Changed

Activity score up 7pts (40 → 47)

2026-09-07

Rank Moved

Rank dropped 38 spots (#788 → #826)

2026-09-06

Rank Moved

Rank dropped 33 spots (#755 → #788)

2026-09-05

Rank Moved

Rank dropped 142 spots (#613 → #755)

2026-09-04

Rank Moved

Rank rose 58 spots (#671 → #613)

2026-09-04

Activity Score Changed

Activity score up 5pts (41 → 46)

2026-09-03

Rank Moved

Rank dropped 72 spots (#599 → #671)

2026-09-02

Rank Moved

Rank dropped 33 spots (#566 → #599)

2026-09-01

Rank Moved

Rank dropped 51 spots (#515 → #566)

2026-08-31

Rank Moved

Rank dropped 34 spots (#481 → #515)

2026-08-29

Scorecard Added

OSSF Scorecard: 5.5/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 567 spots (#1045 → #478)

2026-08-29

HVTrust Changed

HVTrust up 32.9pts (23.5 → 56.4)

2026-08-28

Rank Moved

Rank dropped 32 spots (#1013 → #1045)

2026-08-27

Rank Moved

Rank dropped 20 spots (#993 → #1013)

2026-08-26

Rank Moved

Rank dropped 102 spots (#891 → #993)

2026-08-17

Rank Moved

Rank rose 11 spots (#893 → #882)

2026-08-16

Rank Moved

Rank dropped 18 spots (#875 → #893)

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/ris-mcp-ts.svg)](https://hvtracker.net/agents/ris-mcp-ts)
            
HTML:
            <a href="https://hvtracker.net/agents/ris-mcp-ts"><img src="https://hvtracker.net/badge/ris-mcp-ts.svg" alt="HVTrust"></a>

Other agents in MCP Servers

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.4 · Raw JSON

Ris MCP Ts

How Ris MCP Ts could raise its score

Chain of custody

Source Signed

Review and release Mixed

Published packages None

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Ris MCP Ts compares in MCP Servers

Where the 54.8 comes from

HVTrust dimensions vs the MCP Servers average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Ris MCP Ts

AI agent surface

Maintain Ris MCP Ts?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in MCP Servers