Précis-MCP (precis-finance/precis-finance-mcp) is an MCP server listed on the M8ven Trust Index. It scores 69 out of 100, grade C. It declares 17 tools. No publisher has claimed this listing.

C
Limited view
69/100

Précis-MCP

Read-only MCP server for FP&A & management reporting — governed metrics, financial statements and drill-down over a SQL semantic layer. Your own financials on your own warehouse, not market data. Open core of Précis. (metric engine · ClickHouse · OIDC · Docker)

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

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

precis-finance

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// 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 7 credentials: KC_BOOTSTRAP_ADMIN_PASSWORD, MCP_DEV_KEY, INGEST_BINDING_JWT_SECRET, PRECIS_S3_SECRET_ACCESS_KEY, PRECIS_SFTP_PASSWORD, PRECIS_SFTP_HOST_KEY, OIDC_CLIENT_SECRET
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.
configKC_BASE_URL_INTERNAL
configKC_REALM
configKC_BOOTSTRAP_ADMIN_USERNAME
🔐 secretKC_BOOTSTRAP_ADMIN_PASSWORD
configPRECIS_BASE_URL
configKC_BASE_URL_PUBLIC
configKC_MCP_AUDIENCE
configKC_ENABLE_EXCEL_ADDIN
configKC_ADDIN_REDIRECT_URIS
configPRECIS_AUTH_PREFLIGHT
configPRECIS_IDENTITY_CLAIM
configPRECIS_IDENTITY_COLUMN
configSANDBOX_USER_UID
configPRECIS_AUTH_MODE
configOIDC_ISSUER
🔐 secretMCP_DEV_KEYexport =$(openssl rand -hex 32)
configPGHOST
configPGPORT
configPGUSER
configPGPASSWORD
configPG_CONNECT_TIMEOUT
configPLATFORM_DB_NAME
configPRECIS_BACKUP_CH_TIMEOUT
configPRECIS_BACKUP_CONFIG
configPRECIS_INSTANCE_DIR
configPRECIS_CLICKHOUSE_POOL_MAXSIZE
configCHHOST
configCHPORT
configCHUSER
configCHPASSWORD
configCHCACERT
configCHVERIFY
configREDIS_HOST
configREDIS_PORT
configPGSSLMODE
configPGSSLROOTCERT
configPG_POOL_MIN
configPG_POOL_MAX
configPG_POOL_TIMEOUT
configINSPECTION_ROW_CAP
🔐 secretINGEST_BINDING_JWT_SECRET
configPRECIS_SCHEDULER_INTERVAL_SECONDS
configPRECIS_WATCHER_INTERVAL_SECONDS
configCHDATABASE
configPRECIS_S3_BUCKET
configPRECIS_S3_PREFIX
configPRECIS_S3_REGION
configPRECIS_S3_ENDPOINT_URL
configPRECIS_S3_ACCESS_KEY_ID
🔐 secretPRECIS_S3_SECRET_ACCESS_KEY
configPRECIS_SFTP_HOST
configPRECIS_SFTP_USER
🔐 secretPRECIS_SFTP_PASSWORD
configPRECIS_SFTP_PORT
configPRECIS_SFTP_KEY_PATH
configPRECIS_SFTP_PREFIX
configPRECIS_SFTP_KNOWN_HOSTS
🔐 secretPRECIS_SFTP_HOST_KEY
configEXCEL_ADDIN_CLIENT_ID
configEXCEL_ADDIN_SCOPE
configEXCEL_ADDIN_RESOURCE_INDICATOR
configEXCEL_ADDIN_DIST_DIR
configCOMPANY_NAME
configPRECIS_TELEMETRY_ENABLED
configOTEL_EXPORTER_OTLP_ENDPOINT
configOTEL_SERVICE_NAME
configPRECIS_TELEMETRY_CAPTURE_CONTENT
configOTEL_PYTHON_EXCLUDED_URLS
configOIDC_CLIENT_ID
configKC_CLIENT_ID
🔐 secretOIDC_CLIENT_SECRET
configOIDC_JWKS_URL
configOIDC_AUDIENCE
configPRECIS_COOKIE_SECURE
configENABLE_MCP_DEV_SERVER
configMCP_BIND_HOST
configMCP_BIND_PORT
// 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 — reload_integrations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_load_history (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_load_status (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 inputs are validated

11/16 tool handlers declare input schemas (69%)

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

Tool handlers catch errors

Only 7/16 tool handlers wrap calls in try/catch (44%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

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 5 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/precis-finance/precis-finance-mcp)](https://m8ven.ai/mcp/precis-finance/precis-finance-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 26257cd8901d9e40be381c9580e3c95c31acccea
code hash: 2752025363abc90ca51ec463a764f4c0fd4bfadbfc566148848dffd556ff256a
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