← Registry

Content Tools

teamcadence.ai

Fetches and summarizes content from Cadence's public website, allowing search and retrieval of site sections, pricing, and key links.

1 endpoint3 known toolsFirst detected August 26, 2026Last detected August 26, 2026

ENDPOINT 1

https://teamcadence.ai/mcp

No auth detected

MCP server metadata

Name
cadence-marketing-site
Version
0.0.1
Capabilities
tools

Known tools 3

cadence_get_site_summary

Return a concise, structured summary of Cadence, its public site sections, pricing, and primary links.

Inferred read-only
cadence_find_content

Search Cadence public site sections and return matching section summaries and URLs.

Inferred read-only
cadence_get_link

Resolve a known Cadence destination such as signup, demo, pricing, docs, or agent discovery resources.

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.cadence-marketing-site]
url = "https://teamcadence.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "cadence-marketing-site": {
      "type": "http",
      "url": "https://teamcadence.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: cadence-marketing-site
Remote MCP URL: https://teamcadence.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": {
    "cadence-marketing-site": {
      "url": "https://teamcadence.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "cadence-marketing-site": {
      "type": "http",
      "url": "https://teamcadence.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "cadence-marketing-site",
  "transport": "streamable-http",
  "url": "https://teamcadence.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.