pecorino (pecorino-mcp/pecorino) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
14 days ago

pecorino

→ pecorino-mcp/pecorino· listed on github_code

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

pecorino-mcp

Source: github_code

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

GitHub

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: OAUTH_JWT_SECRET, HF_TOKEN, HUGGING_FACE_HUB_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configMCP_TRANSPORT
configHOST
configMCP_MAX_CONCURRENT
configMCP_QUEUE_TIMEOUT
🔐 secretOAUTH_JWT_SECRET
configOAUTH_RESOURCE
configOAUTH_ISSUER
configOAUTH_REQUIRED
configPECORINO_WORKSPACE_ROOT
configPECORINO_INDEX_DIR
configPECORINO_ENABLE_EMBEDDINGS
configPECORINO_EMBEDDING_MODEL
configPECORINO_EMBEDDING_DIM
configPECORINO_ENABLE_LSP
configPECORINO_LSP_POOL_SIZE
configPECORINO_LSP_TIMEOUT
configPECORINO_ENABLE_HCGS
configPECORINO_INDEX_CHUNK_SIZE
configPECORINO_INDEX_MAX_WORKERS
configPECORINO_ENABLE_OOD
configPECORINO_ALLOWED_EXTERNAL_DIRS
configPECORINO_CROSS_ENCODER_TOP_N
configMCP_USER_ROLE
🔐 secretHF_TOKEN
🔐 secretHUGGING_FACE_HUB_TOKEN
configOMP_NUM_THREADS
configTOKENIZERS_PARALLELISM
configPECORINO_LLM_MODEL
configPECORINO_STRICT_INJECTION_CHECK
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

16/16 tools missing one or more hints — browse (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); update_index (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +13 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

Only 4/16 tools referenced in tests (25%)

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 3 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/pecorino-mcp-pecorino-1dihn3)](https://m8ven.ai/mcp/pecorino-mcp-pecorino-1dihn3)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 7a347658b8a6e258c9a5139ec8d1aabdf2d2c8c7
code hash: d82c06e703f7c25fd617f261fc42cc1378b6b434295d3f7bb54bbc0bc5370d6d
verified: 8/13/2026, 8:05:33 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