rocq-proof-development-mcp (LLM4Rocq/rocq-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 13 tools. No publisher has claimed this listing.

C
Emerging
74/100
4 days ago

rocq-proof-development-mcp

An server for (formerly Coq) proof development. It exposes compilation, verification, querying, and interactive tactic stepping as MCP tools, so that LLM agents can write and check Rocq proofs.

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

LLM4Rocq

Source: modelscope

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 →

Install from

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.
// 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.
configROCQ_WORKSPACEWorking directory for Rocq compilation; used as the final fallback when no project marker is found by walking up from the file. When set explicitly, all workspace parameters are constrained to this directory or its subdirectories.
configROCQ_COQC_TIMEOUTTimeout (seconds) for rocq_compile
configROCQ_VERIFY_TIMEOUTTimeout (seconds) for rocq_verify
configROCQ_PET_TIMEOUTTimeout (seconds) for pytanque-based tools
configROCQ_QUERY_TIMEOUT_CAPCap (seconds) on the per-call timeout parameter of any pytanque-based tool (rocq_query, rocq_start, rocq_step_multi, rocq_check, rocq_assumptions, rocq_toc, rocq_notations); larger values are clamped and the response carries clamped_timeout: <cap>
configROCQ_COQC_BINARYPath to the coqc binary
configROCQ_MAX_SOURCE_SIZEMaximum source size in bytes
configROCQ_MAX_PET_RSS_MBMaximum pet subprocess RSS (MB). On breach, the call aborts via the timeout recovery path; response includes reason: "memory_exhausted" and pet_restarted: True.
configROCQ_COMPILE_MULTI_ERROR_CAPMaximum number of per-declaration errors collected in the errors field on a failed rocq_compile_file. Set to 0 to disable the feature.
configROCQ_COMPILE_MULTI_ERROR_TIMEOUTPer-chunk timeout (seconds) for the multi-error walker used by rocq_compile_file. Raise it for heavy projects (e.g. a slow VST Require); the walker's overall budget follows it (at least 2× this value), so bumping it now takes effect rather than being clamped by ROCQ_ENRICHMENT_TIMEOUT_CAP.
configROCQ_DUNE_BUILDWhen 1 (default), rocq_compile_file in a dune project builds via dune build / redirects coqc output into _build/default so the source tree stays free of .vo shadows. Set to 0 to force legacy coqc-into-source-tree compilation.
configROCQ_ENRICHMENT_TIMEOUT_CAPCap (seconds) on per-call proof-state capture after a rocq_compile / rocq_compile_file failure
configOPAMROOT
configOPAM_SWITCH_PREFIX
configOPAMSWITCH
configROCQ_PET_TIMEOUT_GRACE
configROCQ_MAX_STATESLRU-protected state table. A state_id you keep querying via from_state will not be evicted by a peer caller churning through new states (see ).
// 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

13/13 tools missing one or more hints — rocq_compile (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); rocq_compile_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); rocq_verify (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +10 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.

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/llm4rocq/rocq-mcp)](https://m8ven.ai/mcp/llm4rocq/rocq-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6983113d0844c0b7f987c79dab13988445109bfb
code hash: 828ff5380d7b6ddf53c130350aa0b0a69a9547be2a03e0aded64361ea6ef0d05
verified: 9/6/2026, 9:02:23 PM
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