isup.tools — is it down?
REMOTE · ISUP.TOOLS
Website status check: is a site down for everyone or just you? Shows HTTP code, time and location.
Available components
Last scanned (17 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 257 tokens (~257/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +3
- HSTS header: fail → pass ▲ security
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://isup.tools/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=isup.tools | CN=WE1,O=Google Trust Services,C=US | 17 Nov 2026 | 15 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | ddc7c9aec6d245b4131bb7d1c4976cdf |
| SANs: isup.tools, *.isup.tools | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of isup.tools. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| tools. | DS published | 1547 | 8 | Verified |
| isup.tools. | DS published | 2371 | 13 | Verified |
| isup.tools. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://isup.tools/mcp | Verified | 200 | |
| http (plaintext) | http://isup.tools/mcp | HTTPS enforced | 301 | https://isup.tools/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_site Check if a website is down ~138
Check if a website is up or down right now. Use it when someone asks whether a site is down, or if it is just them. Makes one request to the site and returns a verdict sentence, the status (UP, DOWN or NOT CHECKABLE), the HTTP code, the time taken, and the real place the check ran from. The check runs near the machine that calls this tool, which may not be near the end user. The site's content is never read.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The domain or full URL to check, for example example.com or https://example.com/status. A bare domain is tried over https first. |
| Name | Type | Req | Description |
|---|---|---|---|
| checkedAt | string | yes | When the check ran (UTC). |
| checkedFrom | string | yes | The real place the check ran from: a city, a raw location code when the city is not known, or "Location unavailable". Never guessed. |
| finalUrl | string|null | yes | The last URL requested, after any redirects, or null when no request was sent. |
| httpCode | integer|null | yes | HTTP status code of the last answer, or null when there was no answer. |
| latencyMs | number|null | yes | Time the whole check took, in milliseconds, or null when no request was sent (unsupported port). |
| reason | string | yes | One line on what happened. |
| redirects | array | yes | Every redirect answer, in order: the URL requested and the 3xx code it answered. Empty when there were no redirects. A redirect the safety rules refused is not listed (reason says it was not followed… |
| resultUrl | string | yes | HTML page for this target. Opening it runs a new check. |
| status | string | yes | UP: answered below HTTP 400. DOWN: answered 400 or higher (except 401, 403, 429), or no answer. NOT CHECKABLE: isup cannot reach this port or address (httpCode null), or the site answered 401, 403 or… |
| target | string | yes | The last URL checked, after any redirects. |
| verdict | string | yes | The verdict sentence, for example "It's just you. example.com is up." |
No examples provided.
How do I install the isup.tools — is it down? MCP server?
isup.tools — is it down? is a hosted endpoint at https://isup.tools/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · isup.tools
claude mcp add --transport http tools-isup-isup 'https://isup.tools/mcp'
What is the isup.tools — is it down? MCP server?
isup.tools — is it down? is an MCP server listed in the public MCP registry as tools.isup/isup. Website status check: is a site down for everyone or just you? Shows HTTP code, time and location. This page covers its hosted endpoint (https://isup.tools/mcp).
Is the isup.tools — is it down? MCP server safe to use?
isup.tools — is it down? scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the isup.tools — is it down? MCP server expose?
isup.tools — is it down? exposes 1 tool: check_site. Their descriptions and schemas cost roughly 138 tokens of context every time the server is loaded.
Does the isup.tools — is it down? MCP server require authentication?
No. We connected to isup.tools — is it down? without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the isup.tools — is it down? MCP server still maintained?
isup.tools — is it down? is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the isup.tools — is it down? MCP server?
VerifyMCP ran 13 checks on isup.tools — is it down?, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.