io.github.CloudCorpRecords/sitestatus
NPM · @RENETURCIOS/SITESTATUS · 2 COMPONENTS
Website up/down checks from two continents, outage lists, uptime history and TLS expiry.
Available components
Last scanned (21 hours ago)
Scores higher than 42% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 499 tokens (~99/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Nov 26 56
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 · Analysed npm/@reneturcios/sitestatus@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_certificate TLS certificate expiry of a website ~46
Reads the HTTPS certificate of a public domain and reports days until expiry, the expiry date and the issuer.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain to inspect, e.g. "example.com". |
No output schema declared.
No examples provided.
check_site Check whether a website is down ~125
Live up/down check of any public website from an independent server (Singapore; Boston for sites that geo-block Singapore). Returns a one-sentence verdict plus status code, latency, resolved IP, redirect target, the view from the other region when available, and how many users reported problems in the last hour. Results are cached 30 s per domain.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain or URL to check, e.g. "github.com" or "https://www.reddit.com/r/all". Scheme, path, port and query are ignored; the host is checked as given. |
No output schema declared.
No examples provided.
list_monitored_sites Sites with stored history ~125
The 634 sites checked every 5 minutes, grouped in 17 categories. Without arguments returns the category list with counts; filter by category or a text query to get domains (at most 200 per call).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category slug or name: social, streaming, ai, work, developer, shopping, finance, banks, gaming, telecom, government, education, messaging, news, travel, health, dating. |
| query | string | – | Case-insensitive substring of the domain or display name, e.g. "bank" or "google". |
No output schema declared.
No examples provided.
list_outages Which monitored sites are down right now ~99
Lists the monitored sites (634 across 17 categories) that are confirmed down right now: two consecutive failed checks from their home region and no other region seeing them up in the last 15 minutes. Optional category filter.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category slug or name: social, streaming, ai, work, developer, shopping, finance, banks, gaming, telecom, government, education, messaging, news, travel, health, dating. |
No output schema declared.
No examples provided.
site_history Uptime and recent incidents of a monitored site ~104
Uptime percentage over 24 h and over the requested window (up to 7 days), the list of outages in that window, when the site was last seen down, the current state and user-report counts. Only for monitored sites (see list_monitored_sites); use check_site for anything else.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window in days (1–7, default 7). |
| domain | string | yes | A monitored domain, e.g. "github.com". |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/sitestatus MCP server?
io.github.CloudCorpRecords/sitestatus runs locally as an npm package, launched with npx -y @reneturcios/sitestatus mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/sitestatus
claude mcp add cloudcorprecords-sitestatus -- npx -y @reneturcios/sitestatus mcp
What is the io.github.CloudCorpRecords/sitestatus MCP server?
io.github.CloudCorpRecords/sitestatus is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/sitestatus. Website up/down checks from two continents, outage lists, uptime history and TLS expiry. This page covers its npm package (@reneturcios/sitestatus).
Is the io.github.CloudCorpRecords/sitestatus MCP server safe to use?
io.github.CloudCorpRecords/sitestatus scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/sitestatus MCP server expose?
io.github.CloudCorpRecords/sitestatus exposes 5 tools: check_site, list_outages, site_history, check_certificate, list_monitored_sites. Their descriptions and schemas cost roughly 499 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/sitestatus MCP server still maintained?
io.github.CloudCorpRecords/sitestatus 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 licence is the io.github.CloudCorpRecords/sitestatus MCP server under?
io.github.CloudCorpRecords/sitestatus declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.CloudCorpRecords/sitestatus MCP server?
VerifyMCP ran 15 checks on io.github.CloudCorpRecords/sitestatus, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/sitestatus: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.