Suncture Healthcare

Created By
wilforlana year ago
A Model Context Protocol (MCP) server that provides healthcare-related tools for AI assistants, enabling them to offer practical healthcare information to users.
Overview

What is Suncture Healthcare?

Suncture Healthcare is a Model Context Protocol (MCP) server that provides healthcare-related tools for AI assistants, enabling them to offer practical healthcare information to users.

How to use Suncture Healthcare?

To use Suncture Healthcare, install the server locally or run it using Docker. Connect it with MCP-enabled AI models to access healthcare tools.

Key features of Suncture Healthcare?

  • Health Recommendations Tool: Get personalized health screening and preventive care recommendations.
  • Medication Information Tool: Look up comprehensive information about medications.
  • Disease Information Tool: Find information about diseases and medical conditions.
  • BMI Calculator Tool: Calculate Body Mass Index and get tailored health recommendations.
  • Symptom Checker Tool: Analyze reported symptoms and get preliminary advice.

Use cases of Suncture Healthcare?

  1. Providing personalized health recommendations based on user data.
  2. Offering detailed medication information to users.
  3. Assisting users in understanding diseases and their treatments.
  4. Helping users calculate their BMI and understand health implications.
  5. Guiding users through symptom analysis and potential conditions.

FAQ from Suncture Healthcare?

  • Is the healthcare information provided by the server reliable?

The information is for educational purposes only and not a substitute for professional medical advice.

  • Can I run the server using Docker?

Yes! You can build and run the server using Docker for easy deployment.

  • What are the prerequisites for local installation?

You need Node.js (v18 or later) and npm (v7 or later) to install the server locally.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wilforlan
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago