# golive (npm · golive-mcp)

Check a site before you share it: link previews, SPA refresh 404s, noindex, security headers.

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `golive-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/myanptl-golive-mcp/golive-mcp.md), [page](https://verifymcp.io/servers/myanptl-golive-mcp/golive-mcp)

## Channel facts

- Registry: `npm`
- Package: `golive-mcp`
- Version: `1.0.1`
- 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-09-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 622 tokens (~124/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 golive MCP server?

golive runs locally as an npm package, launched with npx -y golive-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add myanptl-golive-mcp -- npx -y golive-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "myanptl-golive-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "golive-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "myanptl-golive-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "golive-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add myanptl-golive-mcp -- npx -y golive-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "myanptl-golive-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "golive-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add myanptl-golive-mcp --command npx --arg -y --arg golive-mcp
```

### Hermes

```yaml
mcp_servers:
  myanptl-golive-mcp:
    command: "npx"
    args: ["-y", "golive-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "myanptl-golive-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "golive-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add myanptl-golive-mcp -t stdio -c npx -a -y golive-mcp
```

### Other

```json
{
  "mcpServers": {
    "myanptl-golive-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "golive-mcp"
      ]
    }
  }
}
```

## 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-09-25 (score 71, +15)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 56)

First indexed and scored.

## MCP tools (5)

### `golive` (~199 tokens)

Check a site is ready to go live

Run every check on a URL before it gets shared or launched: how the link preview will look on LinkedIn, X, Slack, iMessage and Discord (and whether the image loads, is the right size, and is not an SVG), sub-pages that 404 on refresh, noindex or robots.txt left on from staging, template titles and Vite favicons, missing security headers, and http that does not redirect. Returns findings with fixes, text mockups of each platform's card, and the preview image itself. Use it after deploying, before posting a link, or on localhost before pushing.

Input parameters:

- `paths` (array): Extra paths to open directly, e.g. ["/about", "/pricing"]. Use this for client-rendered apps whose links are not in the HTML.
- `url` (string, required): The page to check: a live URL, a preview deployment, or a local dev server like http://localhost:5173

### `check_link_preview` (~108 tokens)

Check how a link will look when shared

Check the Open Graph and Twitter card tags on a URL and show how the link will look on LinkedIn, X, Slack, iMessage and Discord. Loads the og:image and checks it is reachable, a raster format, about 1200x630, and under platform size limits. Returns the image so you can see it.

Input parameters:

- `url` (string, required): The page to check: a live URL, a preview deployment, or a local dev server like http://localhost:5173

### `check_routes` (~140 tokens)

Check sub-pages survive a refresh

Open a site's internal links directly, the way a refresh, bookmark or shared link does. Catches the single-page-app 404 (works when clicked, breaks on refresh) and names the host-specific fix, e.g. the vercel.json rewrite. Also checks that made-up URLs return a real 404.

Input parameters:

- `paths` (array): Extra paths to open directly, e.g. ["/about", "/pricing"]. Use this for client-rendered apps whose links are not in the HTML.
- `url` (string, required): The page to check: a live URL, a preview deployment, or a local dev server like http://localhost:5173

### `check_security_headers` (~85 tokens)

Check security headers

Check HTTPS, the http to https redirect, HSTS, nosniff, clickjacking protection, CSP, Referrer-Policy and X-Powered-By on a URL, each with the header to add.

Input parameters:

- `url` (string, required): The page to check: a live URL, a preview deployment, or a local dev server like http://localhost:5173

### `check_basics` (~90 tokens)

Check launch basics

Check the things that get forgotten at launch: template titles like 'Vite + React', the Vite favicon, missing meta description, viewport and lang, apple-touch-icon, noindex or robots.txt left on from staging, and mixed content.

Input parameters:

- `url` (string, required): The page to check: a live URL, a preview deployment, or a local dev server like http://localhost:5173

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/myanptl-golive-mcp/golive-mcp#diagnostics

## Score history

- 2026-09-25: 71
- 2026-09-24: 56

## Common questions

### What is the golive MCP server?

golive is an MCP server listed in the public MCP registry as io.github.myanptl/golive-mcp. Check a site before you share it: link previews, SPA refresh 404s, noindex, security headers. This page covers its npm package (golive-mcp).

### Is the golive MCP server safe to use?

golive scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 golive MCP server expose?

golive exposes 5 tools: golive, check_link_preview, check_routes, check_security_headers, check_basics. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.

### Is the golive MCP server still maintained?

golive is still listed as active in the MCP registry. We last reached this channel on 25 September 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 golive MCP server under?

golive 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

- npm package: https://www.npmjs.com/package/golive-mcp
- Socket report: https://socket.dev/npm/package/golive-mcp
- Repository: https://github.com/myanptl/golive-mcp
- Changelog RSS feed: https://verifymcp.io/servers/myanptl-golive-mcp/golive-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/myanptl-golive-mcp/golive-mcp.json
- HTML version of this page: https://verifymcp.io/servers/myanptl-golive-mcp/golive-mcp