Marketing

onyxsend.com

Provides competitive analysis, industry playbooks, and buyer Q&A for cold outreach marketing.

1 endpoint6 known toolsFirst detected August 29, 2026Last detected August 29, 2026

ENDPOINT 1

https://onyxsend.com/mcp

No auth detected

MCP server metadata

Name: OnyxSend MCP
Version: 1.0.0

Capabilities

tools

Known tools 6

list_competitors

List OnyxSend's head-to-head competitor comparison pages.

Inferred read-only

get_comparison

Get the OnyxSend vs <competitor> comparison page payload.

Inferred read-only

list_industries

List cold outreach industry playbooks OnyxSend publishes.

Inferred read-only

get_industry

Get the OnyxSend industry playbook for a specific vertical.

Inferred read-only

list_questions

List OnyxSend's canonical answers to cold outreach buyer questions.

Inferred read-only

get_question

Get OnyxSend's canonical answer to a cold outreach buyer question.

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.onyxsend-mcp]
url = "https://onyxsend.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "onyxsend-mcp": {
      "type": "http",
      "url": "https://onyxsend.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: onyxsend-mcp
Remote MCP URL: https://onyxsend.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": {
    "onyxsend-mcp": {
      "url": "https://onyxsend.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "onyxsend-mcp": {
      "type": "http",
      "url": "https://onyxsend.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "onyxsend-mcp",
  "transport": "streamable-http",
  "url": "https://onyxsend.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.