Ai Doctor Api Ai Medical Chatbot Healthcare Ai Assistant MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API 密钥 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| neurosurgeryD | Neurosurgery |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool 'neurosurgery' has a distinct purpose, even if vaguely described.
With a single tool, naming consistency is trivial. However, the name 'neurosurgery' is a noun rather than a verb_noun pattern, which is slightly atypical but not inconsistent.
The server name implies a broad healthcare AI assistant, but it offers only one tool. This is a severe mismatch; the tool count is far too low for the claimed domain.
The tool surface is severely incomplete. A healthcare AI assistant would need many more capabilities (e.g., general diagnosis, symptom checking, other specialties). Covering only neurosurgery leaves obvious gaps.