io.getsales/outreach-mcp
GetSales: Outreach MCP Server
Is the GetSales MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Drive a GetSales workspace: tables, people, companies, enrichment, workflows, inbox, tasks, signals.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_request"}- Endpoint
- https://mcp2.getsales.io/mcp/public (streamable-http)
- Host
- mcp2.getsales.io
- Package
- The publisher's package npm:@getsales/outreach-mcp did not list its tools in the container: needs network, MCP error -32000: Connection closed syscall: 'getaddrinfo', hostname: 'mcp2.getsales.io' } }.
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mcp2.getsales.io/mcp/public registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server app.getsales.io, PKCE S256, grants authorization_code, refresh_token, urn:ietf:params:oauth:grant-type:token-exchange.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/getsales-io/outreach-mcp
- Website
- https://getsales.io/ai-sales-assistant/
- Registry
- active, updated 2026-11-08 · registry entry
Compare this server with others.
More servers
Servers that mention outreach.
- Getlead ad.getle/leads · alive
- BAMF.ai ai.bamf/bamf · not MCP
- MentionAgent ai.mentionagent/mentionagent · needs auth
- Onsa ai.onsa/onsa · alive
- ai.openhelm/email-outreach · needs auth
- Pro Reach LinkedIn Outreach ai.proreach/outreach · needs auth
- Lead Intelligence ai.saifs/lead-intelligence · needs auth
- Selda ai.selda/selda · 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.