Shire Automations MCP server
by praisondani·
io.github.praisondani/shireautomations-cli·v0.1.1Read Shire Automations services and pricing; plan business workflows with stateless tools.
A88/100grade A
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed Shire Automations yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Shire Automations tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
How Shire Automations compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
Install Shire Automations in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
Shire Automations: common questions
- Is Shire Automations MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the Shire Automations safety report
- Does Shire Automations need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Shire Automations maintained?
- The last commit was 14 days ago (2026-10-21). The latest release is v0.1.1.