Orionbelt Analytics MCP Server

orionbelt-analytics PyPI v2.0.3

Published by ralforion — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

OrionBelt Analytics - the Ontology-based MCP server for your Text-2-SQL convenience

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

low Shell/command execution in packaging/dev tooling (scripts/gen-third-party-notices.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/gen-third-party-notices.py:325`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ). """ result = subprocess.run( [ "uv", "export", "--frozen",

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server scripts/gen-third-party-notices.py

low Shell/command execution in packaging/dev tooling (tests/test_output_dir_guard.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_output_dir_guard.py:75`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ion. """ proc = subprocess.run( [sys.executable, "-c", "import src.paths"], cwd=PROJECT_ROOT,

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_output_dir_guard.py

Tools 28

Each tool and what it can reach — statically extracted from the published source.

  • download_artifactingests untrusted input
  • execute_sql_queryreads sensitive data
  • add_rdf_knowledgeno sensitive capability
  • add_semantic_contextno sensitive capability
  • apply_semantic_namesno sensitive capability
  • cleanup_old_versionsno sensitive capability
  • cleanup_workspaceno sensitive capability
  • connect_databaseno sensitive capability
  • discover_schemano sensitive capability
  • generate_chartno sensitive capability
Show 18 more tools ↓
  • generate_ontologyno sensitive capability
  • get_semantic_modelno sensitive capability
  • get_table_detailsno sensitive capability
  • graphrag_find_join_pathno sensitive capability
  • graphrag_query_contextno sensitive capability
  • graphrag_searchno sensitive capability
  • list_schemasno sensitive capability
  • list_semantic_modelsno sensitive capability
  • load_my_ontologyno sensitive capability
  • measurable_fromno sensitive capability
  • plan_composite_queryno sensitive capability
  • query_sparqlno sensitive capability
  • reachable_fromno sensitive capability
  • reset_cacheno sensitive capability
  • sample_table_datano sensitive capability
  • save_semantic_modelno sensitive capability
  • store_ontology_in_rdfno sensitive capability
  • suggest_semantic_namesno sensitive capability

What this scan could not see

Versions 5

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.0.3 latest A 96/100 2 1.13.0 2026-09-01
v2.0.1 A 96/100 2 1.13.0 2026-08-30
v2.0.0 A 96/100 1 1.13.0 2026-08-25
v1.8.0 A 96/100 1 1.12.1 2026-08-06
v1.7.2 A 96/100 0 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/orionbelt-analytics/badge.svg)](https://mcptrustchecker.com/registry/orionbelt-analytics)
HTML
<a href="https://mcptrustchecker.com/registry/orionbelt-analytics"><img src="https://mcptrustchecker.com/registry/orionbelt-analytics/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/orionbelt-analytics/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan orionbelt-analytics --online --registry pypi

Use the free API → How scoring works

More in Learning & Documentation