io.github.CloudCorpRecords/sitedoctor
OCI · GHCR.IO/CLOUDCORPRECORDS/SITEDOCTOR · 2 COMPONENTS
SEO site audits, issue search, Google visibility checks and improvement plans for your sites.
Available components
Last scanned (11 hours ago)
Scores higher than 53% of OCI servers
Category Marketing and SEO
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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 895 tokens (~89/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 41
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 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/sitedoctor@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 | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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_google_visibility ~91
Check Google indexability for all sites (or one): noindex tags, robots blocks, sitemap errors, canonical problems, redirect chains and broken internal links found in the last crawl. Explains per site whether anything blocks indexing. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Restrict to one site (optional) |
No output schema declared.
No examples provided.
find_issues ~93
Search open issues across all sites (or one site). Returns issue groups: site, issue type, severity, how many pages are affected, and an example page. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Restrict to one site (optional) |
| severity | string | – | Restrict to one severity (optional) |
No output schema declared.
No examples provided.
free_page_check ~99
Free single-page SEO/health audit of any public URL — no API key, no account. Returns the same score, grade, categories and issues as the product's free check, plus an `upgrade` field describing what the authenticated tools add. Rate limited per caller (3/day). Whole-site crawls, history and tasks need a DrUrls account.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page to audit, e.g. https://example.com |
No output schema declared.
No examples provided.
generate_report ~101
Compile a full SEO report — for one site (score, issues by severity, top issue types, Google visibility, social presence, ranked fix plan) or the whole organization (per-site scores, visibility verdicts, top cross-site actions). Cost: 2 credits per call, charged only if the call succeeds. Rate limit: 100 requests/minute per API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | One site's domain; omit for the whole-organization report |
No output schema declared.
No examples provided.
get_improvement_plan ~80
The highest-impact actions to improve quality right now, ranked by severity and how many pages each fix touches, with concrete how-to-fix guidance. Cost: 2 credits per call, charged only if the call succeeds. Rate limit: 100 requests/minute per API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Restrict to one site (optional) |
No output schema declared.
No examples provided.
get_scan_status ~60
What is running right now and what finished recently: every in-flight scan plus the last 10 completed/failed ones with scores and errors. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_site_report ~76
Deep-dive one site: latest audit score, issue counts by severity, the most frequent issue types with counts, and social-network presence. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The site's domain, e.g. example.com |
No output schema declared.
No examples provided.
list_sites ~71
List every site in the user's organization with its latest completed audit: SEO score, grade, issues found, pages crawled, when it was last scanned, and whether a scan is running right now. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tester_offers ~135
Browse the catalogue of tests a real person will run on a real device: mobile UX on a handset, end-to-end checkout, a screen-reader pass by somebody who uses one daily, native-speaker translation review, and more. These cover what reading a page cannot answer — how something feels on a handset, what a screen reader announces, whether a checkout completes on a real phone: what an automated audit cannot measure. Returns each offer with its price in credits, turnaround, and exactly what gets delivered. Cost: free — reads data your organisation already produced. Rate limit: 100 requests/minute per API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
start_scan ~89
Launch a fresh audit of a website. Creates the site in the org if it doesn't exist yet. Enforces the user's plan quota — if the quota is used up it explains that instead of scanning. Cost: 1 credit per call, charged only if the call succeeds. Rate limit: 100 requests/minute per API key.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The website URL or domain to audit |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/sitedoctor MCP server?
io.github.CloudCorpRecords/sitedoctor runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/sitedoctor:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/sitedoctor
claude mcp add cloudcorprecords-sitedoctor -- docker run --rm -i ghcr.io/cloudcorprecords/sitedoctor:0.1.0
What is the io.github.CloudCorpRecords/sitedoctor MCP server?
io.github.CloudCorpRecords/sitedoctor is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/sitedoctor. SEO site audits, issue search, Google visibility checks and improvement plans for your sites. This page covers its container image (ghcr.io/cloudcorprecords/sitedoctor).
Is the io.github.CloudCorpRecords/sitedoctor MCP server safe to use?
io.github.CloudCorpRecords/sitedoctor scores 42 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 io.github.CloudCorpRecords/sitedoctor MCP server expose?
io.github.CloudCorpRecords/sitedoctor exposes 10 tools: list_tester_offers, list_sites, get_site_report, find_issues, check_google_visibility, and 5 more. Their descriptions and schemas cost roughly 895 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/sitedoctor MCP server still maintained?
io.github.CloudCorpRecords/sitedoctor is still listed as active in the MCP registry. We last reached this channel on 5 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/sitedoctor MCP server under?
io.github.CloudCorpRecords/sitedoctor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.