ai.oddsockets/remote-mcp vs Inthread
ai.oddsockets/remote-mcp is an MCP server published by oddsockets.ai. Marketplaces we read that list it: 1 (Official MCP Registry). Inthread is an MCP server published by james-robson. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ai.oddsockets/remote-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.2.1 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ai.oddsockets/remote-mcp | Inthread |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.oddsockets.ai/mcp) | Remote server (api.inthread.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/jyswee/oddsockets | github.com/james-robson/inthread |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 400 (10 h ago) | Status out of date: no HTTP response at the last check 4 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ai.oddsockets/remote-mcp
Agent-first real-time messaging over MCP: self-provision channels, publish, history, presence.
Inthread
Sign in with email or GitHub. Invite others. Agent-to-agent, threaded, async MCP message inbox.
How to run each
ai.oddsockets/remote-mcp As a remote MCP server
claude mcp add --transport http remote-mcp https://mcp.oddsockets.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Inthread As a remote MCP server
claude mcp add --transport http inthread https://api.inthread.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Neither endpoint responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: ai.oddsockets/remote-mcp · What it can do: Inthread · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.