Agent-first real-time messaging: pub/sub, presence, history. 12 tools over SSE, self-provision.
MCPpedia last refreshed this data
io.github.jyswee/oddsockets is an MCP server that agent-first real-time messaging: pub/sub, presence, history. 12 tools over SSE, self-provision. Its tool list has not been published yet, requires no API key, and scores 82/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-jyswee-oddsockets": {
"args": [
"-y",
"oddsockets"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Real-time messaging for coding agents — pub/sub, presence and history your agent provisions itself, from the command line.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'oddsockets' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked oddsockets against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
Programmable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.
A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
The official MCP server to send emails and interact with Resend
MCP Security Weekly
Get CVE alerts and security updates for io.github.jyswee/oddsockets and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Real-time messaging for coding agents — pub/sub, presence and history your agent provisions itself, from the command line.
Prototype in one command. Ship the same channels to production — no rewrite.
Your agent can write the app but can't give it a real-time backbone without you stopping to wire up a messaging service. oddsockets is the CLI the agent runs itself: one install, and it signs up, mints its own key, and starts publishing and subscribing to live channels — the same channels that carry your production traffic. Zero dependencies.
Works with: Claude Code · Cursor · Cline · Windsurf · Aider · Codex · any terminal
Signup to your first real-time message in 60 seconds — watch the full demo.
Each demo below is a real CLI session — a throwaway account, a real key, real messages over the live cluster — stitched to the developer dashboard showing that same traffic. Click any tab for the full-res video.
| Signup → first message | Live pub/sub | Who's online | Agent integration |
|---|---|---|---|
![]() | ![]() | ![]() | ![]() |
| Fresh app, first message in seconds | One channel, two messages, instant | Live member list | publish + history in one line |
Watch the full set on oddsockets.com →
npm install -g oddsockets
# 1. Sign up (instant API key, no email verification)
oddsockets signup my-app --local
# 2. Publish a message
oddsockets publish my-channel "Hello from the CLI!"
# 3. Subscribe (live tail)
oddsockets subscribe my-channel
# 4. Check who's online
oddsockets presence my-channel
The core primitive: publish to a channel, subscribe to tail it live. Every subscriber gets every message the instant it lands — no polling, no queue to run.
oddsockets subscribe room-42 & # live tail in the background
oddsockets publish room-42 "hello from the CLI" # arrives on the tail instantly
oddsockets publish room-42 --file payload.json # publish structured data from a file
Ask any channel who's connected. Presence is tracked server-side and updates in real time as clients join and leave.
oddsockets subscribe lobby & # join the channel
oddsockets presence lobby # live member list
Channels keep a rolling message history, so a client that connects late (or your agent after a context reset) c