orionbelt-analytics (ralforion/orionbelt-analytics) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 28 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Limited view
71/100

orionbelt-analytics

Ontology-based MCP server that analyzes database schemas (PostgreSQL, Snowflake, ClickHouse, Dremio) and generates RDF/OWL ontologies with SQL mappings for fan-trap-free Text-to-SQL.

→ ralforion/orionbelt-analytics· listed on glama

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

ralforion

Source: Glama · also listed on github_topic, github_repo_search

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

Glamanot scored hereGitHub

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 8 credentials: POSTGRES_PASSWORD, SNOWFLAKE_PASSWORD, DREMIO_PASSWORD, CLICKHOUSE_PASSWORD, MCP_MASTER_PASSWORD, MOTHERDUCK_TOKEN, DATABRICKS_ACCESS_TOKEN, MYSQL_PASSWORD
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.
configORIONBELT_MCP_URL
configAUTO_CLEANUP_ON_STARTUP
configWORKSPACE_MAX_AGE_DAYS
configLOG_LEVEL
configONTOLOGY_BASE_URI
configMCP_TRANSPORTSet =sse in .env, restart the server, then add to librechat.yaml:
configMCP_SERVER_HOST
configMCP_SERVER_PORTThe server starts on http://localhost:9000 (HTTP transport, configurable via ).
configCHART_RETURN_BINARY
configENABLE_SAMPLING
configPOSTGRES_HOSTEdit .env with your database credentials. At minimum, set the variables for one database (e.g. , POSTGRES_PORT, POSTGRES_DATABASE, POSTGRES_USERNAME, POSTGRES_PASSWORD).
configPOSTGRES_PORTEdit .env with your database credentials. At minimum, set the variables for one database (e.g. POSTGRES_HOST, , POSTGRES_DATABASE, POSTGRES_USERNAME, POSTGRES_PASSWORD).
configPOSTGRES_DATABASEEdit .env with your database credentials. At minimum, set the variables for one database (e.g. POSTGRES_HOST, POSTGRES_PORT, , POSTGRES_USERNAME, POSTGRES_PASSWORD).
configPOSTGRES_USERNAMEEdit .env with your database credentials. At minimum, set the variables for one database (e.g. POSTGRES_HOST, POSTGRES_PORT, POSTGRES_DATABASE, , POSTGRES_PASSWORD).
🔐 secretPOSTGRES_PASSWORDEdit .env with your database credentials. At minimum, set the variables for one database (e.g. POSTGRES_HOST, POSTGRES_PORT, POSTGRES_DATABASE, POSTGRES_USERNAME, ).
configSNOWFLAKE_ACCOUNT
configSNOWFLAKE_USERNAME
🔐 secretSNOWFLAKE_PASSWORD
configSNOWFLAKE_WAREHOUSE
configSNOWFLAKE_DATABASE
configSNOWFLAKE_ROLE
configDREMIO_URI
configDREMIO_PAT
configDREMIO_HOST
configDREMIO_PORT
configDREMIO_USERNAME
🔐 secretDREMIO_PASSWORD
configDREMIO_SSL
configCLICKHOUSE_HOST
configCLICKHOUSE_PORT
configCLICKHOUSE_DATABASE
configCLICKHOUSE_USERNAME
🔐 secretCLICKHOUSE_PASSWORD
configCLICKHOUSE_PROTOCOL
configCLICKHOUSE_SECURE
configOUTPUT_DIR
🔐 secretMCP_MASTER_PASSWORD
configGRAPHRAG_EMBEDDING_MODEL
configSNOWFLAKE_SCHEMA
configBIGQUERY_PROJECT_ID
configBIGQUERY_DATASET
configBIGQUERY_CREDENTIALS_PATH
configBIGQUERY_CREDENTIALS_JSON
configDUCKDB_DATABASE_PATH
🔐 secretMOTHERDUCK_TOKEN
configDUCKDB_READ_ONLY
configDATABRICKS_SERVER_HOSTNAME
configDATABRICKS_HTTP_PATH
🔐 secretDATABRICKS_ACCESS_TOKEN
configDATABRICKS_CATALOG
configDATABRICKS_SCHEMA
configMYSQL_HOST
configMYSQL_PORT
configMYSQL_DATABASE
configMYSQL_USERNAME
🔐 secretMYSQL_PASSWORD
configMYSQL_CHARSET
configAUTO_ONTOLOGY
configOBA_SHACL_VALIDATE
configAUTO_GRAPHRAG
configR2RML_BASE_IRI
configARTIFACT_KEEP_VERSIONS
// 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

28/28 tools missing one or more hints — connect_database (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_schemas (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); reset_cache (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +25 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

25/28 tool handlers declare input schemas (89%)

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

Tool handlers catch errors

Only 0/28 tool handlers wrap calls in try/catch (0%)

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/ralforion/orionbelt-analytics)](https://m8ven.ai/mcp/ralforion/orionbelt-analytics)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 80288d66a57bdb10e5a4a6c8c5d2b12433e1d2d5
code hash: 377b691ef33f81ca8e076a094349abfd57b1da4b2e0122933e9339352fa58e04
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