Auth is handled by a connector platform sitting between the agent and the vendor, so the credential lives with the platform rather than with either end. The bucket is a keyword match over the mcp_auth field, run at build time, and the verbatim field ships in the row beside it so you can check the parse yourself. Where the two disagree, the verbatim field is the fact and the bucket is the convenience.
| Tool | MCP status | Server URL | mcp_auth, verbatim | Gate |
|---|---|---|---|---|
| Sendspark sendspark.com | Community MCP | https://composio.dev/toolkits/sendspark | API-key based - Composio's page states Sendspark requires the user's own API key, which Composio then stores/manages. | Paid, self-serve |
| Vidyard vidyard.com | Community MCP | https://viasocket.com/mcp/vidyard | Not documented in technical detail on the viaSocket listing ("built-in authentication"). Vidyard's own Video Agent REST API (separate from any MCP)... | Paid, self-serve |
| Weezly weezly.com | Community MCP | https://zapier.com/mcp/weezly | Zapier-mediated connection. | Gate unknown |
| WorkRamp workramp.com | Community MCP | https://zapier.com/mcp/workramp +1 more | Rides Zapier's/viaSocket's own hosted-connector auth (their MCP gateway at mcp.zapier.com), not a WorkRamp-issued credential. | Gate unknown |
Counted 2026-08-25 from directory.json and reconciled against tools_recount.py. Nothing on this page is hand maintained: it is a filter over the same 293 entries the rest of the site is built from. Ordered by the published rule: official MCP first, then community, then unknown, then n/a, then none-found; within each band gate order is free, paid, enterprise-leaning, enterprise-only, unknown; then alphabetical by name. Computed, never curated, never purchasable.