Ris MCP Ts
MCP Server for the Austrian Legal Information System (RIS) - Access Austrian federal laws, state laws, court decisions and more
Is Ris MCP Ts safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Ris MCP Ts
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Ris MCP Ts scores 54.6/100 (Grade C), ranked #796 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 5.5/10; 77% of recent commits are signed; last pushed 2026-09-08. Every point is earned from checkable signals — never paid placement. How scoring works →
How Ris MCP Ts compares in MCP Servers
- #442 Fr24api MCP 54.7 +0.1
- #443 Happy Platform MCP 54.6 ±0
- #444 Ris MCP Ts 54.6 this agent
- #445 Reddit Research MCP 54.5 −0.1
- #446 Tradingview MCP 54.5 −0.1
Bars show each HVTrust score; the tick marks Ris MCP Ts’s 54.6.
Where the 54.6 comes from
HVTrust dimensions vs the MCP Servers average
54.6 / 100 · 100.0% confidenceRis MCP Ts MCP Servers average (775 agents)
Quick Trust Read
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
Activity & Reach
Analysis
Activity Inputs
45.0 / 100Supply Chain Trust
Common questions about Ris MCP Ts
Does Ris MCP Ts publish package provenance?
Does Ris MCP Ts have an OpenSSF Scorecard?
Is Ris MCP Ts actively maintained?
What license does Ris MCP Ts use?
Are Ris MCP Ts's commits signed?
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
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 signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
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.
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.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/ris-mcp-ts)
<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
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