Content Tools

zship.ai

Reads and searches public ZShip pages, documentation, blog posts, and store assets.

1 endpoint2 known toolsFirst detected October 25, 2026Last detected October 25, 2026

ENDPOINT 1

https://zship.ai/mcp

No auth detected

MCP server metadata

Name: ZShip Public Knowledge MCP
Version: 1.0.0

Capabilities

tools.listChangedresources.listChangedprompts.listChanged

Server instructions

Use search-public-content to discover public ZShip knowledge, then get-public-content to retrieve one page. Do not expect account, checkout, support, or private dashboard data.

Known tools 2

get-public-content

Read one public ZShip page, documentation article, blog post, or store asset by path.

Potential side effects

search-public-content

Search public ZShip pages, documentation, blog posts, and store assets.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.zship-public-knowledge-mcp]
url = "https://zship.ai/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "zship-public-knowledge-mcp": {
      "type": "http",
      "url": "https://zship.ai/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: zship-public-knowledge-mcp
Remote MCP URL: https://zship.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "zship-public-knowledge-mcp": {
      "url": "https://zship.ai/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "zship-public-knowledge-mcp": {
      "type": "http",
      "url": "https://zship.ai/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "zship-public-knowledge-mcp",
  "transport": "streamable-http",
  "url": "https://zship.ai/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.