MCP Server 产品名称: 奇黄&智草MCP医疗助手的MCP服务

Created By
AiLMe-AIa year ago
APUS岐黄(医疗)& 智草(中医)大模型的MCP服务
Overview

What is APUS Medical MCP Server?

APUS Medical MCP Server is a medical consultation service that integrates both Western and Traditional Chinese medicine, providing intelligent medical advice and diagnosis based on user symptoms.

How to use APUS Medical MCP Server?

To use the server, you can either download the code to your local machine or configure it in a client application. After setup, you can access the service through a web interface or API calls.

Key features of APUS Medical MCP Server?

  • Integration of Western and Traditional Chinese medicine consultation systems.
  • Intelligent medical advice based on user symptoms.
  • Support for both API and web interface access.

Use cases of APUS Medical MCP Server?

  1. Providing medical advice for common symptoms.
  2. Offering treatment plans and medication suggestions.
  3. Delivering Traditional Chinese medicine prescriptions and wellness advice.

FAQ from APUS Medical MCP Server?

  • Can the server provide advice for all medical conditions?

Yes, it covers a wide range of conditions through both Western and Traditional Chinese medicine approaches.

  • Is there a cost to use the service?

The service is free to use, but an API key is required for access.

  • How do I obtain an API key?

You can request an API key by contacting bd [at] apusai.com.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AiLMe-AI
Star
0
Language
Python
License
Apache-2.0 license

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago