Is Clio MCP safe to use?

Clio MCP has an HVTrust score of 57.5/100 (Grade C), ranked #704 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Clio MCP?

Clio MCP scores 57.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 24 GitHub stars and is categorized under MCP Servers.

Clio MCP

oktopeak/clio-mcp

Open-source MCP server connecting Claude to Clio practice management. Built by Oktopeak.

MCP Servers TypeScript Listed MIT

Is Clio MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.1 / 10

Provenance None

Signed commits 24%

Last push 16d ago

Compare Clio MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

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

How Clio MCP compares in MCP Servers

#386 RPG Maker MV Ultimate MCP 57.7 +0.2
#387 Local Memory 57.6 +0.1
#388 Clio MCP 57.5 this agent
#389 Icon Composer MCP 57.5 ±0
#390 MCP Zenml 57.4 −0.1

Bars show each HVTrust score; the tick marks Clio MCP’s 57.5.

Where the 57.5 comes from

HVTrust dimensions vs the MCP Servers average

57.5 / 100 · 100.0% confidence

Clio MCP MCP Servers average (775 agents)

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

6.3 / 25

4.0 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.0 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

16.6 / 20

4.5 above avg 12.1

AdoptionLog-scaled stars · package downloads

6.8 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

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 rose 229 spots (#920 → #691)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.1/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.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Clio MCP View MCP Servers Report missing data

54.2

Activity sub-score · out of 100

#388

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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-10

16 days ago

Commits (4 wk)

Downloads (7d)

363

npm

HN mentions (30d)

—

Open Issues

Rank Change

was #704

Analysis

Activity Inputs

54.2 / 100

StarsRepository reach

8.4 / 30

FreshnessLast push recency

22.8 / 25

ActivityRecent commits

17.6 / 25

CommunityFork signal

5.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.1 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

24%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 7

CII-Best-Practices 0

Code-Review 2

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies 3

SAST 0

Security-Policy 10

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Clio MCP

Clio MCP 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 Clio MCP publish package provenance?

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

Does Clio MCP have an OpenSSF Scorecard?

Clio MCP has an OpenSSF Scorecard score of 4.1/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 Clio MCP actively maintained?

Maintained. Last push was 16 days ago.

What license does Clio MCP use?

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

Are Clio MCP's commits signed?

24% of the last 100 commits to Clio MCP 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

Clio MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

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

high confidence

Match

Published package metadata matches the tracked repo

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 Clio MCP'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 Clio MCP?

For maintainers

HVTrust scores Clio MCP 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-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 rose 229 spots (#920 → #691)

2026-09-23

HVTrust Changed

HVTrust up 31.3pts (26.4 → 57.7)

2026-09-22

Newly Listed

First tracked at rank #920

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-13

Rank Moved

Rank dropped 10 spots (#656 → #666)

2026-09-12

Rank Moved

Rank rose 11 spots (#667 → #656)

2026-09-10

Rank Moved

Rank dropped 18 spots (#641 → #659)

2026-09-08

Rank Moved

Rank dropped 13 spots (#626 → #639)

2026-09-07

Grade Changed

Trust grade D → C

2026-09-07

Rank Moved

Rank rose 526 spots (#1152 → #626)

2026-09-07

HVTrust Changed

HVTrust up 20.8pts (37.6 → 58.4)

2026-09-06

Rank Moved

Rank dropped 16 spots (#1136 → #1152)

2026-09-05

Rank Moved

Rank dropped 36 spots (#1100 → #1136)

2026-09-04

Rank Moved

Rank rose 18 spots (#1118 → #1100)

2026-09-02

Rank Moved

Rank dropped 32 spots (#1078 → #1110)

2026-09-01

Rank Moved

Rank dropped 36 spots (#1042 → #1078)

2026-08-31

Rank Moved

Rank dropped 34 spots (#1008 → #1042)

2026-08-30

Rank Moved

Rank dropped 52 spots (#956 → #1008)

2026-08-29

Rank Moved

Rank dropped 47 spots (#909 → #956)

2026-08-28

Scorecard Added

OSSF Scorecard: 2.5/10

2026-08-28

Rank Moved

Rank rose 254 spots (#1163 → #909)

2026-08-28

HVTrust Changed

HVTrust up 13.3pts (19.8 → 33.1)

2026-08-27

Rank Moved

Rank rose 16 spots (#1179 → #1163)

2026-08-27

Activity Score Changed

Activity score up 6pts (38 → 45)

2026-08-26

Rank Moved

Rank dropped 46 spots (#1133 → #1179)

2026-08-25

Rank Moved

Rank dropped 16 spots (#1117 → #1133)

2026-08-19

Rank Moved

Rank dropped 10 spots (#1103 → #1113)

2026-08-16

Rank Moved

Rank dropped 29 spots (#1087 → #1116)

2026-08-10

Rank Moved

Rank dropped 64 spots (#1024 → #1088)

2026-08-08

Newly Listed

First tracked at rank #1018

GitHub → npm: @oktopeak/clio-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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