golive
NPM · GOLIVE-MCP · SCANNED SEP 25
Check a site before you share it: link previews, SPA refresh 404s, noindex, security headers.
Available components
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 95 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 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- 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.
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.
npm · golive-mcp
claude mcp add myanptl-golive-mcp -- npx -y golive-mcp
{
"mcpServers": {
"myanptl-golive-mcp": {
"command": "npx",
"args": [
"-y",
"golive-mcp"
]
}
}
} {
"servers": {
"myanptl-golive-mcp": {
"command": "npx",
"args": [
"-y",
"golive-mcp"
]
}
}
} codex mcp add myanptl-golive-mcp -- npx -y golive-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"myanptl-golive-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"golive-mcp"
],
"enabled": true
}
}
} openclaw mcp add myanptl-golive-mcp --command npx --arg -y --arg golive-mcp
mcp_servers:
myanptl-golive-mcp:
command: "npx"
args: ["-y", "golive-mcp"] {
"McpServers": {
"myanptl-golive-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"golive-mcp"
]
}
}
} assistant mcp add myanptl-golive-mcp -t stdio -c npx -a -y golive-mcp
{
"mcpServers": {
"myanptl-golive-mcp": {
"command": "npx",
"args": [
"-y",
"golive-mcp"
]
}
}
} 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.
- 25 Sept 26 +15
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 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 25 Sept 2026 · Analysed npm/golive-mcp@1.0.1
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 95 packages
| Packages resolved | 95 |
|---|---|
| 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_basics Check launch basics ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page to check: a live URL, a preview deployment, or a local dev server like http://localhost:5173 |
No output schema declared.
No examples provided.
check_link_preview Check how a link will look when shared ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page to check: a live URL, a preview deployment, or a local dev server like http://localhost:5173 |
No output schema declared.
No examples provided.
check_routes Check sub-pages survive a refresh ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The page to check: a live URL, a preview deployment, or a local dev server like http://localhost:5173 |
No output schema declared.
No examples provided.
check_security_headers Check security headers ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page to check: a live URL, a preview deployment, or a local dev server like http://localhost:5173 |
No output schema declared.
No examples provided.
golive Check a site is ready to go live ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The page to check: a live URL, a preview deployment, or a local dev server like http://localhost:5173 |
No output schema declared.
No examples provided.
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.