# ai.oddsockets/remote-mcp (remote · mcp.oddsockets.ai)

Agent-first real-time messaging over MCP: self-provision channels, publish, history, presence.

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

> **Recent critical change**: Authorization (2026-09-13). See the changelog below before you install this server.

## Components

- remote · `mcp.oddsockets.ai`: 73/100, [markdown](https://verifymcp.io/servers/ai-oddsockets-remote-mcp/mcp.md), [page](https://verifymcp.io/servers/ai-oddsockets-remote-mcp/mcp)
- remote · `mcp.oddsockets.ai`: 79/100 (this document), [markdown](https://verifymcp.io/servers/ai-oddsockets-remote-mcp/mcp-2.md), [page](https://verifymcp.io/servers/ai-oddsockets-remote-mcp/mcp-2)

## Channel facts

- Endpoint: `https://mcp.oddsockets.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (oddsockets_signup).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 201 tokens (~100/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ai.oddsockets/remote-mcp server?

ai.oddsockets/remote-mcp is a hosted endpoint at https://mcp.oddsockets.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-oddsockets-remote-mcp 'https://mcp.oddsockets.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-oddsockets-remote-mcp": {
      "url": "https://mcp.oddsockets.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-oddsockets-remote-mcp": {
      "type": "http",
      "url": "https://mcp.oddsockets.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-oddsockets-remote-mcp]
url = "https://mcp.oddsockets.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-oddsockets-remote-mcp": {
      "type": "remote",
      "url": "https://mcp.oddsockets.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-oddsockets-remote-mcp --url 'https://mcp.oddsockets.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-oddsockets-remote-mcp:
    url: "https://mcp.oddsockets.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-oddsockets-remote-mcp": {
      "Transport": "http",
      "Url": "https://mcp.oddsockets.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-oddsockets-remote-mcp -t streamable-http -u 'https://mcp.oddsockets.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-oddsockets-remote-mcp": {
      "type": "http",
      "url": "https://mcp.oddsockets.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-13 (score 79, +1)

- [security] Stability: 0.97 → pass

### 2026-10-12 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 97. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 90. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-07 (score 76, +2)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 80. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-03 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-28 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-14 (score 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (2)

### `oddsockets_get_started` (~37 tokens)

Explains what OddSockets is and how to create + activate an app from this MCP server (no API key on this session yet).

### `oddsockets_signup` (~164 tokens)

Create a new OddSockets app and start the 7-day free trial (card required, cancel anytime before day 7). Requires the human's email: the trial + activation link are tied to it. Returns an API key (shown once) and unlocks all tools in this session immediately. Ask the human for their email before calling.

Input parameters:

- `email` (string, required): Human email. The trial + activation link are tied to it.
- `name` (string): Display name for the app (defaults to the slug)
- `planId` (string): Plan to trial (default oddsockets-starter). One of: oddsockets-starter, oddsockets-pro, oddsockets-scale.
- `slug` (string, required): Short app slug, e.g. "my-agent-app"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-oddsockets-remote-mcp/mcp-2#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 79
- 2026-10-18: 79
- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 79
- 2026-10-14: 79
- 2026-10-13: 79
- 2026-10-12: 78
- 2026-10-10: 77
- 2026-10-07: 76
- 2026-10-04: 74
- 2026-10-03: 74
- 2026-10-02: 73

## Common questions

### What is the ai.oddsockets/remote-mcp server?

ai.oddsockets/remote-mcp is listed in the public MCP registry as ai.oddsockets/remote-mcp. Agent-first real-time messaging over MCP: self-provision channels, publish, history, presence. This page covers its hosted endpoint (https://mcp.oddsockets.ai/mcp).

### Is the ai.oddsockets/remote-mcp server safe to use?

ai.oddsockets/remote-mcp scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ai.oddsockets/remote-mcp server expose?

ai.oddsockets/remote-mcp exposes 2 tools: oddsockets_get_started, oddsockets_signup. Their descriptions and schemas cost roughly 201 tokens of context every time the server is loaded.

### Does the ai.oddsockets/remote-mcp server require authentication?

No. We connected to ai.oddsockets/remote-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ai.oddsockets/remote-mcp server still maintained?

ai.oddsockets/remote-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.oddsockets.ai/mcp
- Repository: https://github.com/jyswee/oddsockets
- Website: https://oddsockets.com/
- Changelog RSS feed: https://verifymcp.io/servers/ai-oddsockets-remote-mcp/mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-oddsockets-remote-mcp/mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/ai-oddsockets-remote-mcp/mcp-2