clio-mcp (WYRE-AI/clio-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 25 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
1 month ago

clio-mcp

MCP server for Clio Manage that enables interaction with legal practice data including matters, contacts, activities, communications, tasks, documents, calendar entries, and bills via natural language.

→ WYRE-AI/clio-mcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

WYRE-AI

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: CLIO_ACCESS_TOKEN, CLIO_CLIENT_SECRET, CLIO_REFRESH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowtsup@8.0.0GHSA-3mv9-4h5g-vhg3

tsup DOM Clobbering vulnerability

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAUTH_MODEGateway mode (=gateway, MCP_TRANSPORT=http -- the Docker image's default): credentials
🔐 secretCLIO_ACCESS_TOKENexport =...
configCLIO_CLIENT_IDexport =... # optional, required alongside a refresh token
🔐 secretCLIO_CLIENT_SECRETexport =... # optional, required alongside a refresh token
🔐 secretCLIO_REFRESH_TOKENexport =... # optional
configCLIO_REGIONexport =us # optional, defaults to us
configLOG_LEVEL
configMCP_HTTP_HOST
configMCP_HTTP_PORT
configMCP_TRANSPORTGateway mode (AUTH_MODE=gateway, =http -- the Docker image's default): credentials
// quality suggestions

All four hints declared on every tool

25/25 tools missing one or more hints — clio_activities_list (missing: destructiveHint, idempotentHint); clio_activities_get (missing: destructiveHint, idempotentHint); clio_activities_create (missing: destructiveHint), +22 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

10/25 tools referenced in tests (40%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/wyre-technology/clio-mcp)](https://m8ven.ai/mcp/wyre-technology/clio-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 9dd5eaab8764b6504a0802a0f81404e56fc9726e
code hash: 74e2c7ca62b1231895c562b48fbfe455d50c9572b5bb45ae8d684a341ff17bfc
verified: 8/8/2026, 3:46:21 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client