PluginBench
MCP Server

QSimHealth MCP Server

com.qsimhealth/public

RepositoryRegistry
How to choose

What this kind of tool is for

  • Chain multi-step workflows across the other tools in this directory.
  • Run a scheduled or triggered job instead of retyping the same request.
  • Have your agent watch a feed, queue, or repo and act on new items.

How to compare servers like this

Trigger model:
Understand what starts the automation — a command, a schedule, or an event — before relying on it.
Blast radius:
Prefer tools that hand you a review point before an irreversible action runs.
Chaining cost:
Each chained step adds a failure point; keep critical paths on the fewest tools.
Maintenance signal:
Automations break quietly; a maintained tool is the difference between repair and rediscovery.

This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.

What is the QSimHealth MCP server?

Healthcare staffing simulator — ED, walk-in clinic, and appointment office DES tools.

How to install QSimHealth

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
~/.cursor/mcp.json
JSON config
{
  "mcpServers": {
    "public": {
      "url": "https://qsimhealth.com/mcp/v1"
    }
  }
}

Related MCP servers

Query, browse, and automate OmegaAI workspaces from any MCP client. Streamable HTTP with OAuth 2.0.

View repository →

Assess recurring workflows and submit an authorized sanitized inquiry for human review.

Find, call and pay per call: the capability layer for agents, plus skills. One key or OAuth.

Lead enrichment plus AI-written cold emails in one run.

Multi-agent governance: task orchestration, compliance, decision validation, and ML predictions.

Verify email addresses and clean lists to improve deliverability and sender reputation.