F
Warning
37/100
8 days ago

regulated-reporting-mcp

MCP server for regulated financial reporting on Workiva, enabling agents to search, read, and write to Workiva workbooks with policy-gated mutations, readback verification, and immutable receipts. Supports both a compact 3-tool facade and a full 117-tool catalog, plus a credential-free mock mode.

Warning. Serious findings were identified. Review the full report before connecting. 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

dbett4

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 →

Install from

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

// key findings
🚨
Reads files from sensitive locations
Touches: ~/Library/Keychains/login.keychain-db
// 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.
configWORKIVA_MCP_CATALOG_MODE
configWORKIVA_MCP_MOCKH -. =1 .-> M[(FakeWorkiva<br/>in-memory)]
configWORKIVA_ENV_FILECredentials can also live in a .env file next to the package or pointed at with .
configWORKIVA_REGIONexport =us # us eu apac
configWORKIVA_MCP_RECEIPT_DIRwrite-once receipt store used against a real workspace). Set to
configWORKIVA_MCP_RESULT_DIR
configWORKIVA_CA_BUNDLE
configSSL_CERT_FILE
configREQUESTS_CA_BUNDLE
configSSL_CERT_DIR
// quality suggestions

Tool annotations

3/120 tools have annotations

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

All four hints declared on every tool

117/120 tools missing one or more hints — workiva_list_organizations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); workiva_get_organization (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); workiva_list_organization_users (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +114 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 inputs are validated

116/120 tool handlers declare input schemas (97%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 26/120 tool handlers wrap calls in try/catch (22%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 19/120 tools referenced in tests (16%)

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

No access to sensitive paths

Reads sensitive paths: ~/Library/Keychains/login.keychain-db

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

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 6 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 Verified](https://m8ven.ai/badge/mcp/dbett4-regulated-reporting-mcp-qmsxsa?variant=verified)](https://m8ven.ai/mcp/dbett4-regulated-reporting-mcp-qmsxsa)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: e277d1f719df751283f34742844a09c1da5b14f8
code hash: 2f12cfe5ba67ea7c991511e6917fadea74bee5d1cdcf6bcc64e1725c68b8cc78
verified: 8/11/2026, 7:32:16 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