mcsinglewire
What it looks like in a conversation
Section titled “What it looks like in a conversation”Instead of opening the InformaCast admin console to dig through device lists, someone on the team can just ask:
Which IP speakers in our hospital haven’t checked in today?
Three speakers haven’t reported in over the last 24 hours:
Cardiology-A-204— last seen 2 days agoER-Bay-3— last seen 18 hours agoCafeteria-Main— last seen 3 days ago
Want me to pull their last known IPs so facilities can take a look?
Each answer comes from a single read-only call to your Singlewire system. The call is recorded so you can always check who asked what.
Under the hood: this is a Model Context Protocol (MCP) server bridging Claude (or any MCP-compatible client) to InformaCast Mobile’s REST API. Example device names, sites, and timestamps throughout this site are illustrative — nothing here is real device data.
Other questions teams ask
Section titled “Other questions teams ask”A few of the audits that come up week to week — every one of them is a built-in prompt, picked from a menu, not a query you have to type from scratch:
Who has admin access to InformaCast right now?
What scenarios are configured, and who would they page?
Did Tuesday morning’s drill notification actually reach everyone?
Any incidents still open from the overnight shift?
How many users haven’t logged in for 90 days?
See Prompts reference for the full list and Your first audit for what it looks like to run one.
What you can count on
Section titled “What you can count on”It can’t change anything
Every interaction with your Singlewire system is read-only. The design refuses writes at three independent layers — nothing this server does can dispatch a notification, edit a scenario, or change a single setting.
Every question is logged
Each call is recorded with who asked, what was asked, and what came back. Useful for compliance reviews and for satisfying anyone who asks “what’s this thing doing on our network?”
Uses your existing login
Each person signs in with their own Singlewire account on first connect — no shared service credentials. The audit trail in Singlewire reflects them, not “the AI”.
