Hologres MCP Server

hologres-mcp-server PyPI v1.0.3

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

A MCP Server for Hologres

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/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 = 95/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 − 5 = 95. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 39

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

  • get_hg_execution_planreads sensitive data
  • get_hg_query_planreads sensitive data
  • analyze_hg_query_by_idno sensitive capability
  • call_hg_procedureno sensitive capability
  • cancel_hg_queryno sensitive capability
  • create_hg_maxcompute_foreign_tableno sensitive capability
  • execute_hg_ddl_sqlno sensitive capability
  • execute_hg_dml_sqlno sensitive capability
  • execute_hg_select_sqlno sensitive capability
  • execute_hg_select_sql_with_serverlessno sensitive capability
Show 29 more tools ↓
  • gather_hg_table_statisticsno sensitive capability
  • get_hg_dynamic_table_refresh_historyno sensitive capability
  • get_hg_guc_configno sensitive capability
  • get_hg_lock_diagnosticsno sensitive capability
  • get_hg_slow_queriesno sensitive capability
  • get_hg_table_info_trendno sensitive capability
  • get_hg_table_propertiesno sensitive capability
  • get_hg_table_shard_infono sensitive capability
  • get_hg_table_storage_sizeno sensitive capability
  • get_hg_warehouse_statusno sensitive capability
  • list_hg_active_queriesno sensitive capability
  • list_hg_data_masking_rulesno sensitive capability
  • list_hg_dynamic_tablesno sensitive capability
  • list_hg_external_databasesno sensitive capability
  • list_hg_query_queuesno sensitive capability
  • list_hg_recyclebinno sensitive capability
  • list_hg_schemasno sensitive capability
  • list_hg_tables_in_a_schemano sensitive capability
  • list_hg_warehousesno sensitive capability
  • manage_hg_classifierno sensitive capability
  • manage_hg_query_queueno sensitive capability
  • manage_hg_warehouseno sensitive capability
  • query_and_plotly_chartno sensitive capability
  • query_hg_external_filesno sensitive capability
  • rebalance_hg_warehouseno sensitive capability
  • restore_hg_table_from_recyclebinno sensitive capability
  • set_hg_query_queue_propertyno sensitive capability
  • show_hg_table_ddlno sensitive capability
  • switch_hg_warehouseno sensitive capability

What this scan could not see

Versions 1

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
v1.0.3 latest A 95/100 0 1.13.0 2026-08-25

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 · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/hologres-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/hologres-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/hologres-mcp-server"><img src="https://mcptrustchecker.com/registry/hologres-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/hologres-mcp-server/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 hologres-mcp-server --online --registry pypi

Use the free API → How scoring works

More in Other