SteadySite MCP server
dev.steadysite/steadysitesteadysite.devstreamable-httpv1.0.0Scanned
Check SSL certificate and domain expiry for any site, see plans, and get a monitoring sign-up link.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the SteadySite MCP server can do
The SteadySite MCP server is published by steadysite.dev, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: check_ssl_domain_expiry and start_monitoring), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (check_ssl_domain_expiry).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 9, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 2Claude Code: ask
check_ssl_domain_expiryLook up a website's SSL certificate expiry (date, days left, issuer), domain registration expiry (date, days left, registrar) and current HTTP status.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Look up a website's SSL certificate expiry (date, days left, issuer), domain registration expiry (date, days left, registrar) and current HTTP status. Use when someone asks when a site's certificate or domain expires, who issued it, or whether the site is up. "warn" means expiring within 30 days, "bad" means expired or down. Results are cached for 15 minutes; fresh lookups are limited to 15 per 10 minutes.
Annotations the server declares
- title: Check SSL & domain expiry
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
start_monitoringReturn a sign-up link that starts SteadySite monitoring (uptime, SSL expiry and domain expiry email alerts, monthly client report) for a domain.1 finding
Why it is in this group
- The name "start_monitoring" says "start": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "start_monitoring" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "start_monitoring" says "start": a word for a change.
Description, as the server wrote it Return a sign-up link that starts SteadySite monitoring (uptime, SSL expiry and domain expiry email alerts, monthly client report) for a domain. The person opens the link, signs in with their email (free plan, no credit card) and the domain is pre-filled. Nothing is created until they confirm.
Annotations the server declares
- title: Start monitoring
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
get_plansReturn SteadySite plans (Free, Pro, Agency): monthly price in USD, monitors, check interval, client groups with their own branded reports and status pages, white-label, and whether…No findings
Why it is in this group
- The name "get_plans" says "get": a word for reading.
Description, as the server wrote it Return SteadySite plans (Free, Pro, Agency): monthly price in USD, monitors, check interval, client groups with their own branded reports and status pages, white-label, and whether paid checkout is open. Use when someone asks what SteadySite costs or which plan fits.
Annotations the server declares
- title: Plans & pricing
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:21 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://steadysite.dev/mcp: tools/list returned 3 tools to an anonymous client, including check_ssl_domain_expiry (write), start_monitoring (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnstart_monitoring
The server marks "start_monitoring" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "start_monitoring" says "start": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http steadysite https://steadysite.dev/mcpclaude mcp add --transport http steadysite https://steadysite.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__steadysite__get_plans"
],
"ask": [
"mcp__steadysite__check_ssl_domain_expiry",
"mcp__steadysite__start_monitoring"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as steadysite. Review it before you use it.
Capability tags behind 1 rule
- mcp__steadysite__check_ssl_domain_expiry untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.steadysite/steadysite/verify?hash=918750d4bba52cd376bc0bc1db893f96376170937be134f6b8bd7c133b08b6ad" | jq -e '.changed == false'Pinned hash 918750d4bba5, from Nov 9, 2026, 08:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.steadysite/steadysite/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.steadysite/steadysite)Source: MCP Registry. Synced Nov 9, 2026, 08:17 UTC.
SteadySite MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SteadySite MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SteadySite MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SteadySite MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the SteadySite MCP server have?
- 3 tools: 2 write, 1 read. check_ssl_domain_expiry, start_monitoring and get_plans.
Does the SteadySite MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SteadySite MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SteadySite MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.