SendPulse MCP server
Checked 2026-09-07. Alive: no. Handshake: unknown.
Category: communication. API and field schema.
Facts
| id | sendpulse--mcp-server |
| name | SendPulse |
| registry_name | com.sendpulse.mcp/mcp-server |
| repo_url | https://github.com/sendpulse/mcp-server |
| endpoint_url | https://mcp.sendpulse.com/mcp |
| transport | streamable-http |
| alive | no |
| liveness_reason | stale |
| check_reachable | yes |
| check_recent_commit | no |
| check_installable | yes |
| handshake_status | unknown |
| handshake_checked_at | 2026-09-07T18:58:57Z |
| handshake_protocol_version | not available |
| handshake_auth_hint | http:401 |
| handshake_auth_discoverable | not available |
| handshake_failure_layer | jsonrpc |
| handshake_latency_ms | 1519 |
| handshake_tools_state | not available |
| handshake_tool_count | not available |
| maintenance_status | dormant |
| last_commit_at | 2025-11-05T13:41:32Z |
| category | communication |
| license_spdx | not available |
How to install or connect
Connect your MCP client to https://mcp.sendpulse.com/mcp.
What the checks mean
alive combines the applicable repository, package, and endpoint checks. A null result is not verifiable, not a failure. The MCP handshake is a separate structural probe and is not a security audit. Read the methodology.