SUS healthcare MCP
Related Servers
Alternatives to SUS healthcare MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables secure, read-only querying of the e-SUS APS/PEC PostgreSQL data warehouse for clinical extraction, care-line tracking, audit, and public-health indicator monitoring through LGPD-compliant anonymization.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural-language querying of Brazilian public health indicators from DataSUS microdata — mortality, dengue, hospitalizations, ICSAP, and births — through 41 tools covering consultation, analysis (peer-stratum comparison, dengue endemic channel, weekly bulletin), reliability warnings, and anomaly detection. It runs locally against the public API with anti-hallucination rules so every figure comes from a tool with its source cited.MIT
- AlicenseNot gradedqualityBmaintenanceEnables agents to query 153 live Brazilian government data tools across federal and state sources, including economy, legislature, judiciary, elections, health, education, and more, reading directly from original APIs.MIT
- AlicenseAqualityAmaintenanceEnables analysis of Brazilian public hospital admissions (SIH/SUS) focusing on primary care-sensitive conditions, with tools for querying annual cubes, monthly series, and municipal rates per 100,000 inhabitants from 1992 to 2025.12870 npm1MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM clients to run aggregated epidemiological queries over public SINAN/DATASUS microdata through predefined tools for listing bases, describing fields, counting notifications, and calculating an exploratory tuberculosis abandonment proportion, with small-cell suppression and no arbitrary SQL or individual-record access.MIT
- AlicenseNot gradedqualityCmaintenanceEnables querying health establishment data from the Brazilian Federal Council of Medicine (CFM), providing read-only access to official information.MIT
TDQS
Scored across 7 tools
dataset_info and dataset_coverage both describe coverage/availability metadata, making them easy to confuse. geographic_signals, fixed_proxy_activity, and ecological_hits all return fixed ecological/proxy signals with subtle jargon-based distinctions that an agent may not reliably parse.
All names are snake_case noun phrases with no camelCase or mixed-style violations, so the surface is readable. However, there is no consistent verb_noun action pattern and prefix conventions vary (dataset_* versus standalone noun phrases).
Seven tools is well within the ideal 3–15 range for a domain-specific data server. Each tool maps to a distinct data product or metadata concern, so the count feels well-scoped.
The surface covers metadata, coverage, geographic signals, facility capacity, proxy activity, ecological hits, and protocol/billing association, which is broad for ecological SUS data. A minor gap is the absence of an explicit data dictionary/variable lookup or flexible query/filter tool, but core read-only data products are present.