← Registry

General Tools

visit.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint1 known toolsFirst detected October 10, 2026Last detected October 10, 2026

ENDPOINT 1

https://visit.com/mcp

No auth detected

MCP server metadata

Name
visit-public-marketing-content
Version
1.0.0
Capabilities
tools
Server instructions

Read-only published marketing pages. No customer, booking, CRM, account or protected product access. Help MCP uses its separate authorization requirements.

Known tools 1

read_public_content

Read one anonymously readable, published VISIT marketing page.

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.visit-public-marketing-content]
url = "https://visit.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "visit-public-marketing-content": {
      "type": "http",
      "url": "https://visit.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: visit-public-marketing-content
Remote MCP URL: https://visit.com/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": {
    "visit-public-marketing-content": {
      "url": "https://visit.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "visit-public-marketing-content": {
      "type": "http",
      "url": "https://visit.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "visit-public-marketing-content",
  "transport": "streamable-http",
  "url": "https://visit.com/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.