General Tools

alexpolonsky.com

Provides access to Alex Polonsky's professional profile and availability information.

1 endpoint2 known toolsFirst detected August 30, 2026Last detected August 30, 2026

ENDPOINT 1

https://alexpolonsky.com/mcp

No auth detected

MCP server metadata

Name: alexpolonsky-mcp
Version: 0.1.0

Capabilities

toolsprompts

Known tools 2

get_profile

Get Alex Polonsky's curated public professional profile, including selected experience, demonstrated capabilities, journalism background, public projects, and future professional directions.

Inferred read-only

get_availability

Get Alex Polonsky's current public opportunity status, preferred work and engagement contexts, and public contact routes.

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

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