com.usekerux/kerux
Kerux
Is the Kerux MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.
Run your LinkedIn, email and SMS outreach from your AI assistant
needs auth probed 2026-11-15 · unchanged since 2026-11-11 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32001,"message":"Sign in to Kerux (OAuth) or use a Kerux API key: - Endpoint
- https://www.usekerux.com/api/mcp (streamable-http)
- Host
- www.usekerux.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://www.usekerux.com/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server www.usekerux.com, PKCE S256, grants authorization_code, refresh_token.
Scopes leads:read leads:write workflows:read workflows:write enrollments:write senders:read senders:write inbox:read inbox:write events:write analytics:read.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://www.usekerux.com/integrations/claude-and-chatgpt
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Servers that mention linkedin or outreach.
- Adako: ad ops for AI assistants ai.adako/ads · needs auth
- Getlead ad.getle/leads · alive
- ai.adside/adside · needs auth
- Autoposting ai.autoposting/autoposting · not MCP
- BAMF.ai ai.bamf/bamf · not MCP
- Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram ai.bowmark/bowmark · alive
- LinkedIn MCP Server ai.com.mcp/linkedin · not MCP
- DataForB2B ai.dataforb2b/dataforb2b · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.