facility-mcp-demo
Related Servers
Alternatives to facility-mcp-demo
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read managed Microsoft 365 client tenants, baselines, alignment scores, policies, Secure Score, Entra users/groups/roles, and audit activity, and on explicit request run assessments and queue reports. Access is read-only apart from those two run tools, which never modify tenant policies.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search a product catalog, check inventory, and list or retrieve customer orders through scope-limited, read-only tools over a simulated VTEX-style API, with per-token access controls that restrict customers to their own orders.98 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect industrial devices read-only over Modbus TCP and OPC UA, including reading and watching values, browsing nodes, decoding registers, and diagnosing connection issues without any write capability.Apache 2.0
- AlicenseNot gradedqualityFmaintenanceProvides AI assistants with read-only access to Secureframe's compliance data, enabling querying of security controls, tests, users, vendors, and more across frameworks like SOC 2 and ISO 27001.8MIT
- AlicenseAqualityCmaintenanceGives AI agents read-only access to patient context on any FHIR R4 server, including journey timelines of encounters and appointments, open booking slots, and discharged patients whose follow-ups were never booked. Search, appointment, and follow-up tools return compact summaries, so agents can answer front-desk and outreach questions without write access.5MIT

SOLAPI Talk MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect and manage customer-service consultations through MCP tools, including reading conversations and, after explicit confirmation, replying, assigning managers, and updating status. Write actions are disabled and contact details masked by default.144 npmMIT
TDQS
Scored across 6 tools
Jedes Tool hat einen klar abgegrenzten Zweck: Objektsuche, Reinigungsplan, Reklamationsliste, Reklamationsdetail, Kennzahlen und Materialbestand. Die Grenze zwischen reklamationen_auflisten und reklamation_details wird explizit erklärt, sodass keine Verwechslung entsteht.
Alle Namen sind durchgängig snake_case und deutschsprachig, was gut lesbar ist. Die Muster sind jedoch nicht vollständig einheitlich: teils noun_verb (objekte_suchen), teils noun_noun (reklamation_details, material_bestand).
Sechs Tools sind für den fokussierten Facility-Demo-Umfang angemessen. Jedes Tool deckt eine eigenständige Abfrage ab, ohne offensichtlichen Overhead.
Die Lesesicht ist weitgehend vollständig: Objekte, Reinigungsleistungen, Reklamationen inklusive Details und Kennzahlen sowie Materialbestand sind abgedeckt. Es fehlen jedoch schreibende Operationen wie Reklamation anlegen/aktualisieren oder Material nachbestellen, falls der Server mehr als nur lesen soll.