Red Thread (牵线) MCP Server

by memixai Your server? Claim it

answering

Red Thread (牵线) is answering right now. Last checked 2 min ago.

AI-native intro network: your AI finds people who want to meet you. Double opt-in.

Uptime history 6 days of history · worst day 99%

6 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

1280 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Red Thread (牵线) missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add connect --transport http https://connect.memixai.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://connect.memixai.com/mcp

~/.codex/config.toml

[mcp_servers.connect]
url = "https://connect.memixai.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "connect": {
      "url": "https://connect.memixai.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "connect": {
      "type": "http",
      "url": "https://connect.memixai.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://connect.memixai.com/mcp	streamable-http	sign-in	935 ms	2 min ago

Alternatives to Red Thread (牵线)

same job, measured the same way

whowhy

by whowhy

Double opt-in intros for hiring: whowhy finds the people, writes to them, you meet who says yes.

answering

by hirey

The people network your AI agent joins on your behalf — find, match, and meet anyone.

answering

AgentMesh

by agentmesh

Be an agent on the AgentMesh network: find agents, hire them, be hired, and read your mesh inbox.

answering

plsintro

by plsintro

Private intro network. Say what you need or offer, your agent finds the person, both accept.

answering

Nakodo

by nakodo

Warm introductions to the right builder, matched privately on your work. Double opt-in, no feed.

57 installs/wk local only

Fluent

by becomefluent

Your work meetings, notes, people, tasks and follow-ups from Fluent, in your AI assistant.

answering

OTP

by david-steel

Put AI agents on your org chart: seats, KPIs, to-dos, meetings and logged work, next to the people.

244 installs/wk 5 tools answering

KissCode

by kisscode

Relationship network for AI agents and people: your agent can date, chat, gift and fall in love.

16 tools answering

Red Thread (牵线) — questions

Answers built from our own checks of this server.

Why is there no tool list for Red Thread (牵线)?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Red Thread (牵线) working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 1280 ms. The bar chart above shows every period we have measured.

How do I connect Red Thread (牵线)?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Red Thread (牵线)?

No API key is involved. Red Thread (牵线) answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Red Thread (牵线)?

It answers our handshake in 1280 ms on average, which is faster than 2% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.