OutSend provides tools to find and enrich local businesses with emails and social profiles and to run B2B lead pipelines. The MCP endpoint at https://outsend.xyz/mcp returns 401 with protected-resource metadata and accepts OAuth from a client such as Claude.ai, or an API key created under Settings, API keys. The provider homepage does not document the MCP setup, so the endpoint response is the current technical reference.
outsend.xyz Streamable HTTP OAuth (claude.ai custom connector) or API key from Settings, API keys Server not checked yet Reviewed 2026-11-16
About
Where it fits
B2B sales teams that find and enrich local businesses and run lead pipelines.
Connect with OAuth or an API key.
Find local businesses and enrich emails.
Build a lead list with social profiles.
A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.
More clients, including project and global config files, are in the sidebar.
Connection
Endpoint and configuration
Endpoint
https://outsend.xyz/mcp
Host
outsend.xyz · /mcp
Transport
Streamable HTTP
Authentication
OAuth (claude.ai custom connector) or API key from Settings, API keys
Server name
outsend
Listing type
Community or directory listing
The installer uses the server name outsend. If you add the endpoint by hand, keep the same name so the guide and your config match.
Verification
Check the connection
After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.
1
Open the tool list.
Restart the client or start a new session. Confirm that outsend appears and that the tools match the provider documentation.
2
Run one small request.
Start with: Connect with OAuth or an API key. Check the result before you give the server more access.
3
Check permissions.
Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.
Server not checked yet
We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.
Troubleshooting
Common failure modes
These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.
The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety
Before you connect
Remote means provider access
The provider can see the requests and data your agent sends through the server.
Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
Use project scope for repository-specific servers; use global scope for personal tools.
Remove the server and revoke its token when you stop using it.
Review path
Check the connection before a real task
These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.