himc-mcp
Related Servers
Alternatives to himc-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables LLMs to securely query synthetic clinical data through validated, scoped tools (patient summaries, conditions, medications, lab trends, encounters) while maintaining audit logs and access controls.-
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server that enables LLMs to safely explore and query any SQLite database via natural language. It exposes tools for listing tables, describing schemas, and executing SELECT/WITH queries with built-in safety guards like write prevention and row limits.MIT
- AlicenseAqualityDmaintenanceMCP server providing LLMs with safe, read-only access to the Chinook SQLite sample database, including schema exploration and SQL query execution.11MIT
- AlicenseCqualityDmaintenanceA local-first, model-agnostic MCP server that stores personal health data in a SQLite file and provides analysis-ready views for any AI client to log, retrieve, and reason over health records.79MIT
- AlicenseNot gradedqualityDmaintenanceA remote MCP server that lets an LLM explore, query, aggregate, and benchmark the ~234 datasets in the CMS Provider Data Catalog — hospitals, dialysis facilities, nursing homes, home health, hospice, physicians, and more — in plain language.AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server for SQL databases (SQLite/PostgreSQL) that enables listing tables, describing schemas, and executing SELECT queries with safety guardrails.MIT
TDQS
Scored across 5 tools
Each tool has a distinct role: overview for orientation, list_tables for discovery, describe_table for schema detail, query for execution, and data_quality_log for cleaning provenance. The only mild overlap is between overview and data_quality_log, since both discuss how the data was cleaned, though one is dataset-wide narrative and the other is per-table issue logging.
All names are snake_case and readable, with list_/describe_ verb prefixes on the discovery tools. query, overview, and data_quality_log are noun/single-verb forms rather than verb_noun, a minor deviation but nothing confusing.
Five tools is well-scoped for a read-only analytical dataset server: discovery, inspection, execution, and two context tools. Nothing feels padded and every tool earns its place in the exploration workflow.
The surface covers the full read-only lifecycle: orient (overview), discover (list_tables), inspect (describe_table), query (query), and audit provenance (data_quality_log), with SQL handling joins and aggregation. Minor gaps include no schema-wide search or column-level lookup, but agents can work around these with query.