scroll-world
A skill that turn any brand into a scrollable 3D world landing page
Website maintenance checks: domains, SSL, uptime, technical SEO and accessibility
Skills that teach the AI this kind of work; they work alongside this one
A skill that turn any brand into a scrollable 3D world landing page
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 0/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 12/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Let your AI install it with one sentence
Please install upkeep-mcp. Follow https://mcp.popnx.com/i/tiagocalado600-upkeep-mcp.md, show me the commands and wait for my OK before running them.Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads
Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 18, 2026
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server upkeep-mcp for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "upkeep": { "command": "npx", "args": [ "-y", "upkeep-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the upkeep-mcp tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
SettingsDeveloperEdit Config
{
"mcpServers": {
"upkeep": {
"command": "npx",
"args": [
"-y",
"upkeep-mcp"
]
}
}
}Use upkeep-mcp and tell me what you can do for me, then show me one thing✓ If Claude says it is using upkeep-mcp or shows a upkeep-mcp tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect upkeep-mcp yet
upkeep-mcp runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect upkeep-mcp
B · Others in Marketing & social media that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
Works with Claude Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server upkeep-mcp for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user upkeep -- npx -y upkeep-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the upkeep-mcp tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Mac: press Command+Space and type Terminal · Windows: open PowerShell
claude mcp add --scope user upkeep -- npx -y upkeep-mcpYou should see upkeep-mcp listed as connected
Use upkeep-mcp and tell me what you can do for me, then show me one thing✓ If Claude Code says it is using upkeep-mcp or shows a upkeep-mcp tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with Cursor, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server upkeep-mcp for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "upkeep": { "command": "npx", "args": [ "-y", "upkeep-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the upkeep-mcp tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use upkeep-mcp and tell me what you can do for me, then show me one thing✓ If Cursor says it is using upkeep-mcp or shows a upkeep-mcp tool in the answer, you are connected
Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Works with VS Code, with some setup first
Install Node.js on your computer first (one time)
Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.
Please install the MCP server upkeep-mcp for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "upkeep": { "type": "stdio", "command": "npx", "args": [ "-y", "upkeep-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the upkeep-mcp tools really show up.This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.
Already installed? Check first · Open Terminal, type this command and press Enter
node -vMac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Use upkeep-mcp and tell me what you can do for me, then show me one thing✓ If VS Code says it is using upkeep-mcp or shows a upkeep-mcp tool in the answer, you are connected
Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version
Claude Code
claude mcp add --scope user upkeep -- npx -y upkeep-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"upkeep": {
"command": "npx",
"args": [
"-y",
"upkeep-mcp"
]
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"upkeep": {
"command": "npx",
"args": [
"-y",
"upkeep-mcp"
]
}
}
}VS Code (mcp.json)
{
"servers": {
"upkeep": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"upkeep-mcp"
]
}
}
}These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
npm: upkeep-mcpBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account tiagocalado600, which owns the repo
Code last changed 2 days ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
No entries on OSV.dev for upkeep-mcp@0.7.0
Checks only this package version, not every dependency · checked Nov 18, 2026
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/tiagocalado600-upkeep-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 2 days ago, and the latest version (0.7.0) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Relaticle, ChatbotX, X (Twitter) MCP Server by Xquik, Betterlytics, BibiGPT YouTube Video Summarizer
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Open-source CRM your AI agents can write to: companies, people, opportunities, tasks and notes.
Omnichannel customer messaging, CRM contacts, flows, sequences, broadcasts, and AI automation.
Xquik is the world's fastest and cheapest X (Twitter) data API with the most complete X data.
Query your Betterlytics web analytics from AI agents: traffic, funnels, journeys, errors, uptime.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
| This one upkeep-mcp | Relaticle | ChatbotX | X (Twitter) MCP Server by Xquik | Betterlytics | BibiGPT YouTube Video Summarizer | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | Yes | No |
| Add with + in Claude | No | No | No | No | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | AGPL-3.0 | NOASSERTION | MIT | AGPL-3.0 | MIT |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An MCP server for the recurring checks behind ongoing website maintenance: domains, SSL certificates, uptime, technical SEO and accessibility — all from publicly available information.
Built for people who look after a portfolio of client sites on a retainer, not just a single domain. The goal is to answer one question quickly: what needs attention this week?
Early development, built in public phase by phase. Every planned tool is implemented, accessibility_audit included, and useful today.
| Tool | Purpose | Status |
|---|---|---|
domain_check | Registration expiry, registrar, nameserver agreement, DNS records, DNSSEC | Available |
ssl_check | Certificate expiry, issuer, chain validity, SAN coverage, TLS version | Available |
uptime_check | HTTP status, response time, redirect chain, HTTPS upgrade, security headers | Available |
health | Server name, version, Node.js version, uptime | Available |
seo_audit | Title, meta, headings, canonical, robots.txt, sitemap, broken links | Available |
site_crawl | Duplicate titles, broken links and stray noindex across a whole site | Available |
portfolio_report | All of the above across a portfolio, sorted by urgency | Available |
accessibility_audit | WCAG violations via axe-core, in a real browser | Available |
It also exposes the portfolio://sites resource (the site list, for a client to read without spending a tool call) and the quarterly_report prompt (turns a portfolio run into the report a client actually reads).
Published on npm, so it installs with one command — see Installation. A public instance is also running, for anyone who would rather point a client at a URL than run anything — see The hosted instance.
> Is example.com about to expire?
example.com expires 2027-08-13 (268 days). Registrar: RESERVED-Internet Assigned Numbers Authority. Nameservers: elliott.ns.cloudflare.com, hera.ns.cloudflare.com (2 of 2 answered, all on serial 2420077714). Resolves: apex yes, www yes. DNSSEC: signed and validating. Email: SPF -all, DMARC p=reject.
Needs attention:
Check the certificate on expired.badssl.com
expired.badssl.com:443 certificate expires 2015-04-12 (-4238 days). Issued by COMODO RSA Domain Validation Secure Server CA. Chain does not verify (CERT_HAS_EXPIRED). Negotiated TLSv1.2. Host matched via *.badssl.com. Revocation not established: http://ocsp.comodoca.com could not answer: the responder is not authorised to answer for this certificate.
Needs attention:
Check the certificate on revoked-ecc-dv.ssl.com
revoked-ecc-dv.ssl.com:443 certificate expires 2026-12-24 (36 days). Issued by SSL.com TLS Issuing ECC CA R2. Chain verifies. Negotiated TLSv1.3. Host matched via revoked-ecc-dv.ssl.com. Revoked on 2026-06-09.
Needs attention:
Note what the revoked one does: the chain verifies. Node performs no revocation lookup of its own, so that certificate completes a handshake and reports as trusted. Only asking its issuer finds the problem.
Every tool also returns structured data alongside the text, so results can be sorted, filtered and fed into a report. Full input and output for each tool is in examples/, and a whole portfolio session — the weekly triage, a drill-down, and what the comparison against the previous run will and will not claim — is in examples/conversation.md.
domain_checkInput: domain — a bare domain, a full URL, or an internationalised name. A subdomain is reduced to its registrable domain, since that is what a registration belongs to. A bare public suffix such as co.uk is refused as invalid input — here, in ssl_check and in a portfolio's domain — since nobody owns one.
Returns the expiry date and days remaining, the registrar and its IANA ID, registry statuses, A/AAAA/NS/MX/TXT/CAA records, whether the apex and www resolve, whether the delegation is signed with DNSSEC, and what the domain's SPF and DMARC records say about who may send email as it.
Email authentication is read from the domain's own DNS — the SPF record at the apex, the DMARC record at _dmarc. A record that is absent is reported as information, because it is a standing improvement rather than something that broke this week. A record that is present and wrong is a warning, because it fails right now: two SPF records make receivers skip SPF entirely, and +all authorises the whole internet to send as the domain. A record the resolver could not read — a TXT answer too large for UDP, retried over TCP to a home router that refuses TCP, is the usual cause — is never reported as absent: it is unknown, with the resolver's reason, and the same goes for any other record set that went unanswered while the rest of the lookup succeeded.
DKIM is deliberately not reported. A DKIM key lives at ._domainkey, and a selector cannot be discovered — only guessed, one DNS query per guess. That is subdomain enumeration, which this project does not do, so a domain with no DKIM and one whose selector was not guessed are left indistinguishable rather than the second being reported as the first.
Each of the domain's own nameservers is then asked about the zone directly, over TCP port 53 with recursion off, which is the one question a recursive resolver cannot answer: it replies with whatever one server told it and does not say which. That finds a server left in the delegation after a migration — it answers REFUSED, or its own hostname stopped resolving, and every resolver query landing there is slow or fails — and it finds nameservers holding different versions of the zone, which is the "it works for me but not for my colleague" outage.
What is a fault and what is only unestablished are graded apart. Resolvers ask over UDP first and this server can only use TCP, so a nameserver that refuses TCP is not a broken one: sapo.pt's four all refuse it and the domain resolves perfectly. Different serials are info too — github.com runs two providers that do not transfer between them, so four of its nameservers report 1656468023 and four report 1, and nothing is wrong. A hostname that does not resolve, or an answer without authority for the zone, is broken for everybody and is a warning. Pass checkNameservers: false to skip the whole thing — portfolio_report does, because a portfolio would pay this per site and a deployment that cannot open port 53 would grade every site at once as unestablished. docs/adr/0020 records why it speaks DNS by hand and what it deliberately does not check.
ssl_checkInput: domain, optional port (443 by default).
Returns expiry and days remaining, issuer, whether the chain verifies and why not when it does not, which hostnames the certificate covers and via which SAN entry, the negotiated TLS version and cipher, and whether the certificate has been revoked. Expired, self-signed and untrusted certificates are inspected and reported rather than refused — those are the ones worth finding.
A certificate that covers the bare domain but not www (or the reverse) is not by itself a fault: many sites, cloudflare.com among them, serve www from a certificate of its own. So when the host asked about is one of the two and the other resolves but is not covered, one more handshake is made with the other name, and only what it actually serves decides the finding — www_not_covered when that is not valid for it, www_https_failed when no secure connection can be made there at all, www_coverage_unjudged when it could not be established (and the apex_ equivalents from the other side).
Revocation is checked over OCSP. The response a server staples to the handshake is preferred, because it costs no request at all; when there is none, the responder named in the certificate is asked directly. An answer is only believed once its signature verifies against the issuing authority, only once its CertID is shown to be about the certificate that was actually served — a server serving a revoked certificate alongside a valid response for a different one is otherwise the easy way to fake a clean result — and only while it is current, allowing five minutes of clock skew either side. A staple that fails any of these is not the end of it: the responder is asked anyway, so a server cannot suppress its own revoked by stapling something unusable.
Many healthy certificates cannot be checked at all: since 2025 the two largest issuers, Let's Encrypt and Google Trust Services, publish no OCSP responder and distribute revocation by CRL. That is reported as an unavailableReason and produces no finding, because it is a decision of the certificate authority and nothing the site owner can act on. A responder that was asked and would not answer is different, and gets one unknown.
uptime_checkInput: url — a full http or https URL, or a bare domain, which is tried over HTTPS. Any other scheme, such as ftp:, is refused as invalid input.
Returns the status code, response time, every hop of the redirect chain, whether plain HTTP is upgraded to HTTPS, the HSTS policy, and the security headers worth reporting on. A site whose certificate browsers refuse — expired, issued for another host, self-signed — is reported as down, since no visitor gets past the warning.
seo_auditInput: url — the page to audit, plus optional checkLinks (true by default) and maxLinks (25 by default).
Returns title and meta description with their lengths, the heading structure, canonical, lang, viewport, Open Graph, hreflang alternates, the images with no alt attribute, the state of robots.txt and the sitemap, and which internal links are broken.
Only a sitemap URL that answers 404 or 410 is reported as no sitemap, an info gap. One that answers 403 or a server error may well exist and is unreadable to search engines too, so it is a warning that the sitemap could not be read. One that does not answer at all — a timeout, a failed connection — says nothing about the sitemap, so it is graded unknown: the check failed, not the site.
A gzipped sitemap is unpacked before it is read. Whether it is gzipped is decided by the first two bytes rather than by the file name or the content type, because plenty of files called .xml.gz are not, and plenty that are get labelled text/xml.
The sitemap is then checked against the rules of the protocol, because a file that answers 200 and parses is not the same as a file that works: a root element with no sitemaps.org namespace is dropped whole, an entry on another host is discarded, and one unescaped & makes the document ill-formed XML and costs every entry after it. Each broken rule is reported once with the number of en