# io.github.CloudCorpRecords/geoscore (oci · ghcr.io/cloudcorprecords/geoscore)

AI-crawler readiness checks and fixes: GEO score, robots.txt, schema.org, FAQ and llms.txt.

- Trust score: 40/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/geoscore`: 69/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-geoscore/reneturcios-geoscore.md), [page](https://verifymcp.io/servers/cloudcorprecords-geoscore/reneturcios-geoscore)
- oci · `ghcr.io/cloudcorprecords/geoscore`: 40/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-geoscore/ghcr-io-cloudcorprecords-geoscore.md), [page](https://verifymcp.io/servers/cloudcorprecords-geoscore/ghcr-io-cloudcorprecords-geoscore)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/geoscore`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Build provenance not yet verified.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 307 tokens (~61/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the io.github.CloudCorpRecords/geoscore MCP server?

io.github.CloudCorpRecords/geoscore runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/geoscore: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.

### Claude

```bash
claude mcp add cloudcorprecords-geoscore -- docker run --rm -i ghcr.io/cloudcorprecords/geoscore:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-geoscore": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/geoscore:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-geoscore": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/geoscore:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-geoscore -- docker run --rm -i ghcr.io/cloudcorprecords/geoscore:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-geoscore": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/geoscore:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-geoscore:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/geoscore:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-geoscore": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/geoscore:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-geoscore": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/geoscore:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 40, 0)

- [security regression] Provenance: fail → unverified
- [functional regression] Security disclosure: fail → unverified

### 2026-11-04 (score 40, +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.

### 2026-11-03 (score 39)

First indexed and scored.

## MCP tools (5)

### `analyze_geo_score` (~35 tokens)

Check GEO score 0–100 + breakdown for an existing domain

Input parameters:

- `domain` (string, required): Domain this call applies to.

### `get_geo_fixes` (~40 tokens)

Get copy-paste robots.txt, Schema.org, FAQ, and llms.txt fixes

Input parameters:

- `domain` (string, required): Domain this call applies to.

### `make_site_geo_ready` (~86 tokens)

Generate all GEO assets for a new site in one shot (no API key needed)

Input parameters:

- `description` (string, required): Description text.
- `email` (string): Email address.
- `faq` (array): FAQ content.
- `name` (string, required): Name for this call.
- `services` (array): Services to include.
- `url` (string, required): URL for this call.

### `suggest_monitoring_config` (~77 tokens)

Draft a monitoring config (target audiences, location, suggested queries) from a business description — returns JSON plus the API calls to apply it on causabi.com

Input parameters:

- `business_description` (string, required): Description of the business.
- `business_name` (string, required): Name of the business.
- `location` (string): Location for this call.

### `get_site_report` (~69 tokens)

Client-ready report: pass `report_slug` for the full AI mention-rate breakdown (no API key needed), or just `domain` for a crawlability-score-only summary

Input parameters:

- `domain` (string): Domain this call applies to.
- `report_slug` (string): Slug of the report.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-geoscore/ghcr-io-cloudcorprecords-geoscore#diagnostics

## Score history

- 2026-11-05: 40
- 2026-11-04: 40
- 2026-11-03: 39

## Common questions

### What is the io.github.CloudCorpRecords/geoscore MCP server?

io.github.CloudCorpRecords/geoscore is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/geoscore. AI-crawler readiness checks and fixes: GEO score, robots.txt, schema.org, FAQ and llms.txt. This page covers its container image (ghcr.io/cloudcorprecords/geoscore).

### Is the io.github.CloudCorpRecords/geoscore MCP server safe to use?

io.github.CloudCorpRecords/geoscore scores 40 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/geoscore MCP server expose?

io.github.CloudCorpRecords/geoscore exposes 5 tools: analyze_geo_score, get_geo_fixes, make_site_geo_ready, suggest_monitoring_config, get_site_report. Their descriptions and schemas cost roughly 307 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/geoscore MCP server still maintained?

io.github.CloudCorpRecords/geoscore 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/geoscore MCP server under?

io.github.CloudCorpRecords/geoscore declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/geoscore
- Repository: https://github.com/CloudCorpRecords/geoscore
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-geoscore/ghcr-io-cloudcorprecords-geoscore.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-geoscore/ghcr-io-cloudcorprecords-geoscore.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-geoscore/ghcr-io-cloudcorprecords-geoscore