ParseBounce
Email deliverability monitoring and sending: bounces, complaints, suppression, campaigns.
likely compatible
OAuth with discovery metadata and Dynamic Client Registration; use OAuth 2.0 → Dynamic discovery.
Rule R2c · what this means · Not tested in Copilot Studio.
| Registry name | com.parsebounce/parsebounce |
| Endpoint used for verdict | https://api.parsebounce.com/mcp |
| Transports | streamable-http |
| Auth (Copilot Studio setting) | OAuth 2.0 – Dynamic discovery |
| Last endpoint check | 2026-10-20T18:12:10Z · HTTP 401 |
| Version | 1.0.0 |
| Registry updated | 2026-06-10 |
Track changes like this weekly. New Copilot-ready MCP servers, breakages and auth changes, in one short email.
Is this wrong or out of date? Email us. Data built 2026-10-20.