Is McpStamp Delivery Schedule MCP server safe?
Yes, with the usual care.
Safe to use. Minor gaps such as a missing repository or slower maintenance.
What to know before installing
- highWrite-action tools reachable without authentication
How McpStamp Delivery Schedule compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,255 servers
- Tools that change things
- 25%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 21%
- of our recent checks; the typical remote server answers 100%
What its tools let an agent do: 9 read · 3 change
Release history: 5 versions in the registry since 2026-09-17, latest 2026-11-02, typically one every 19 days.
Public scan report
scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it
1 high
- –Code scanpackage could not be scannedn/a
- Live reliabilityremote reachable in 3013ms17/20
- Tool poisoning12 tool descriptions checked15/15
- Auth qualityopen endpoint exposes 3 write-action tools with no auth3/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highWrite-action tools reachable without authentication
auth.open-write
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON