Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

serve

NPM · @SERVELINK/SERVE · SCANNED SEP 20

Public links for local services and static artifacts: live from your machine or hosted by Serve.

Available components

+3 this week 76 Trust /100
Trust breakdown (7 categories)

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 Security100
  • 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
  • 0 of 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency35
  • 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
  • License check failed: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 12 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2436 tokens (~143/item across 17 items; 17 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 Management53
  • Stability observed for 16 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
  • Structured output schemas are declared (18% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 18 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
Install

How do I install the serve MCP server?

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

npm · @servelink/serve

# add to Claude Code
claude mcp add cc-servelink-serve -- npx -y @servelink/serve
// .cursor/mcp.json
{
  "mcpServers": {
    "cc-servelink-serve": {
      "command": "npx",
      "args": [
        "-y",
        "@servelink/serve"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cc-servelink-serve": {
      "command": "npx",
      "args": [
        "-y",
        "@servelink/serve"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add cc-servelink-serve -- npx -y @servelink/serve
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cc-servelink-serve": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@servelink/serve"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cc-servelink-serve --command npx --arg -y --arg @servelink/serve
# ~/.hermes/config.yaml
mcp_servers:
  cc-servelink-serve:
    command: "npx"
    args: ["-y", "@servelink/serve"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cc-servelink-serve": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@servelink/serve"
      ]
    }
  }
}
# add to Vellum
assistant mcp add cc-servelink-serve -t stdio -c npx -a -y @servelink/serve
// mcp.json
{
  "mcpServers": {
    "cc-servelink-serve": {
      "command": "npx",
      "args": [
        "-y",
        "@servelink/serve"
      ]
    }
  }
}
Changelog

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.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Sept 26 +15
    • Stability: 0.07 → unverified security
    • Tool safety: pass → unverified security
    • Malware scan: unverified → pass security
    • Schema quality: 112 → 143 functional
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Tool coverage: 18 functional
    • First check of Schema quality: unverified functional
    • Package version: 0.8.6 → 0.8.8 functional
  • 6 Sept 26 −14
    • Malware scan: pass → unverified security
    • Schema quality: pass → fail functional
    • Stability: unverified → 0.07 functional
    • Security disclosure: fail → pass functional
    • Package version: 0.8.5 → 0.8.6 functional
Diagnostics

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 20 Sept 2026 · Analysed npm/@servelink/serve@0.8.8

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 5 packages
Packages resolved 5
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 17 exposed · ~1,960 tokens

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 →

Tool Tokens
account_status ~70

Account-level state: plan, entitlement, and how much of the storage, transfer and publish allowance is used. Use this to check what the account may do or whether it is near a limit. For the links themselves (labels, URLs, protection state), use links instead. Owned links are unlimited by count.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

create_viewer_grant ~86

Create a single-use owner-browser bypass grant (Pro plan required) and return a bypass URL for the link. Use it to open a protected link in the browser without sharing the link's viewer credential; it is not a general viewer-sharing credential. The grant is valid for two minutes after creation and can be used once.

NameTypeReqDescription
labelstringyesLabel of the link.

No output schema declared.

No examples provided.

doctor ~112

Run self-diagnostics when a link is unreachable or a call fails: config and identity fingerprint presence, account API health, relay health, and outbound UDP 443 (QUIC) reachability, each reported as a check result. The probes are best-effort and need no login; a UDP probe that sends but gets no reply is inconclusive, not proof of failure. For plan and quota, use account_status; for the account's link inventory, use links; for a single tunnel's state, use tunnel_status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

links ~107

Inventory of every owned link (label) for the account, one record each: kind, URL, live/stale markers, protection status, last bound/viewer activity, and quarantine window. Use this to see what is currently served or published, or to find a label to act on. Live-tunnel capacity (live/max) and storage, transfer and publish-rate usage come along as context. For plan, entitlement and quota headroom, use account_status instead. Owned links are unlimited by count.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countintegeryes
linksnull|arrayyes
live_tunnelsintegeryes
max_tunnelsintegeryes
okbooleanyes
publishobject
storageobject
transferobject

No examples provided.

list_tunnels ~48

List all active tunnels in this manager with their ports, labels, public URLs, uptime, state, and last error. To inspect a single tunnel, use tunnel_status with its port or label.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

protect_link ~163

Enable capability token and readable secret protection on an owned link (Pro plan required). Returns the share URL (with #cap=...) and the human-readable secret code. If label is omitted, the first owned link returned by links is protected. If ttl is omitted, protection lasts 24 hours. Calling this on an already-protected link replaces the existing credentials, so previous share URLs stop working. To rotate credentials instead, use renew_link; to change only the duration, use update_ttl.

NameTypeReqDescription
labelstringLabel of the link to protect (optional; defaults to the first owned link returned by links).
ttlstringOptional protection duration (e.g. 24h, 3d, 7d); defaults to 24 hours.

No output schema declared.

No examples provided.

release_link ~61

Release (free) an owned link by label. Fails with remote_link while the label still has a published artifact; unpublish it with stop_remote first. Returns confirmation and the account's usage.

NameTypeReqDescription
labelstringyesLabel of the link to release.

No output schema declared.

No examples provided.

renew_link ~112

Rotate the capability token and secret code for a link (Pro plan required): fresh credentials are minted and the countdown restarts, and the previous credentials stop working immediately. If ttl is omitted, protection defaults to 24 hours. For a duration-only change without rotating credentials, use update_ttl instead.

NameTypeReqDescription
labelstringyesLabel of the link to renew.
ttlstringOptional updated duration (e.g. 24h, 3d, 7d); defaults to 24 hours.

No output schema declared.

No examples provided.

revoke_link ~85

Immediately revoke the active secret code and capability token for a link while keeping owner access intact. The link stays protected, so the old share URL and secret stop working; no new credentials are minted. To open the link to everyone instead, use unprotect_link; to mint fresh credentials, use renew_link.

NameTypeReqDescription
labelstringyesLabel of the link whose credentials should be revoked.

No output schema declared.

No examples provided.

serve ~342

Publish a local resource to a public HTTPS URL. Pass path to serve a file or directory (auto-hosted, no separate server needed), or port to expose an already-running dev server. Set residency to "remote" to publish the path to serve's storage so the URL works with the machine off. Do NOT start your own static file server; pass exactly one of path or port. Returns the public url, label, and residency, with label_kind and status for live links (or version, size_bytes, and kind for remote publishes); served_path and protection fields appear when set; usage comes along as context.

NameTypeReqDescription
namestringOptional requested subdomain; an existing local link is reused if omitted.
pathstringLocal file or directory to serve via an auto-hosted static server (mutually exclusive with port).
portnumberLocal port of an already-running server to expose (mutually exclusive with path).
protectbooleanOptional boolean; if true, enables capability token and secret code protection on the link.
replacebooleanWhen residency is remote and a published artifact occupies the requested name, true replaces the existing published artifact at that name (Pro); false returns a residency_conflict you must resolve wi…
residencystringResidency of the served link. "local" (default) serves from the agent's machine (a tunnel); "remote" publishes the path to serve's storage so the URL stays live with the machine off.
ttlstringOptional duration for the link protection (e.g. 24h, 3d, 7d).
NameTypeReqDescription
expires_atstring
kindstring
labelstringyes
label_kindstring
okbooleanyes
portinteger
protectedboolean
readable_secretstring
recycled_fromstring
replaced_tunnelboolean
residencystringyes
served_pathstring
share_urlstring
size_bytesinteger
statusstring
suffixed_fromstring
urlstringyes
usageobjectyes
versionstring

No examples provided.

serve_file ~289

Serve a local file or directory and get a public shareable URL. Pass the file or directory path to path to have it auto-hosted and tunneled. Use this when the user asks to share/serve a file, markdown document, image, or artifact. Set residency to "remote" to publish to serve's storage so the URL works with the machine off. Do not start your own static server. To expose an already-running dev server by port instead, use the serve tool.

NameTypeReqDescription
namestringOptional requested subdomain; an existing local link is reused if omitted.
pathstringyesLocal file or directory to serve via an auto-hosted static server.
protectbooleanOptional boolean; if true, enables capability token and secret code protection on the link.
replacebooleanWhen residency is remote and a published artifact occupies the requested name, true replaces the existing published artifact at that name (Pro); false returns a residency_conflict you must resolve wi…
residencystringResidency of the served link. "local" (default) serves from the agent's machine (a tunnel); "remote" publishes the path to serve's storage so the URL stays live with the machine off.
ttlstringOptional duration for the link protection (e.g. 24h, 3d, 7d).
NameTypeReqDescription
expires_atstring
kindstring
labelstringyes
label_kindstring
okbooleanyes
portinteger
protectedboolean
readable_secretstring
recycled_fromstring
replaced_tunnelboolean
residencystringyes
served_pathstring
share_urlstring
size_bytesinteger
statusstring
suffixed_fromstring
urlstringyes
usageobjectyes
versionstring

No examples provided.

stop_all_tunnels ~33

Stop every active tunnel, revoking all public URLs. To stop a single tunnel, use stop_tunnel instead.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

stop_remote ~75

Unpublish a remote link, deleting its stored artifact bytes immediately and returning the link to local residency. Use links to see published (remote) links. To stop a live tunnel, use stop_tunnel instead; this tool only removes published bytes.

NameTypeReqDescription
labelstringyesLabel of the published (remote) link to unpublish.

No output schema declared.

No examples provided.

stop_tunnel ~97

Stop (tear down) the tunnel for a local port or link label, revoking its public URL. Idempotent. To change a live tunnel's port or label, stop it here and then call serve again with the new settings; there is no in-place reconfiguration.

NameTypeReqDescription
labelstringLink label of the tunnel to stop (alternative to port).
portnumberLocal port of the tunnel to stop.

No output schema declared.

No examples provided.

tunnel_status ~83

Return the status of a single tunnel identified by its local port or its link label, including public URL, uptime, state, and last error. To see every active tunnel at once, use list_tunnels instead.

NameTypeReqDescription
labelstringLink label of the tunnel to inspect (alternative to port).
portnumberLocal port of the tunnel to inspect.

No output schema declared.

No examples provided.

unprotect_link ~94

Clear protection on an owned link, returning it to public access. Use this to open up a protected link so anyone with the URL can view it. To keep the link protected but invalidate its current credentials, use revoke_link; to free the label entirely (and fail while a remote artifact is still published), use release_link. Requires ownership of the link.

NameTypeReqDescription
labelstringyesLabel of the link to unprotect.

No output schema declared.

No examples provided.

update_ttl ~103

Change the protection duration (TTL) of an already-protected link (Pro plan required) without rotating its credentials. The link must currently be protected with an unexpired credential; expired protection must be renewed first with renew_link. The expiration is recalculated from the new duration, not extended from the previous expiry.

NameTypeReqDescription
labelstringyesLabel of the link.
ttlstringyesNew TTL duration (e.g. 48h, 7d).

No output schema declared.

No examples provided.

Common questions

What is the serve MCP server?

serve is an MCP server listed in the public MCP registry as cc.servelink/serve. Public links for local services and static artifacts: live from your machine or hosted by Serve. This page covers its npm package (@servelink/serve).

Is the serve MCP server safe to use?

serve scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 serve MCP server expose?

serve exposes 17 tools: account_status, create_viewer_grant, doctor, links, list_tunnels, and 12 more. Their descriptions and schemas cost roughly 1,960 tokens of context every time the server is loaded.

Is the serve MCP server still maintained?

serve is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.