com.linqsender/linqsender
LinqSender
Is the LinqSender MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.
Check LinkedIn campaign status, results and replies. A person confirms every campaign.
needs auth probed 2026-11-14 · unchanged since 2026-11-11 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32004,"message":"This connection is not signed in to LinqSender yet, so noth- Endpoint
- https://mcp.linqsender.com/mcp (streamable-http)
- Host
- mcp.linqsender.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp.linqsender.com/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 app.linqsender.com, PKCE S256, grants authorization_code, refresh_token.
Scopes campaigns:read campaigns:write prospects:read prospects:write enrollments:write linkedin:read linkedin:write suppressions:read suppressions:write jobs:read.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://linqsender.com/docs/agents
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Servers that mention campaign or confirms.
- UGC, the Human Ad Network africa.ugc/ugc · needs auth
- AdAdvisor MCP Server ai.adadvisor/mcp-server · needs auth
- ai.adramp/google-ads · needs auth
- Inside Ads ad.inside/inside-ads · alive
- AdWeave — Meta Ads MCP Server ai.adweave/meta-ads-mcp · needs auth
- AgentRoam ai.agentroam/agentroam · alive
- Apple Search Ads ai.b77/apple-search-ads · needs auth
- Clearvoyance ai.clearvoyance/clearvoyance · alive
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.