Both servers below are listed under the same category in the WingMan Protocol MCP server directory, sourced from registry.modelcontextprotocol.io. Every field in the table comes directly from each server's own registry entry - transport, install method, authentication signal, category tags, and whether a source repository or homepage is published. This page makes no performance, quality, or popularity claims about either server; it compares what each listing declares, nothing else.
| Server | Transport | Install method | Auth signal | Categories | Repo published | Homepage | Full listing |
|---|---|---|---|---|---|---|---|
| Attrove | http | Remote endpoint (mcp-remote bridge for older clients) | Vendor-managed auth (API key/OAuth) - not itemized in registry | search-web, communication, productivity | yes | yes | detail page |
| EZTexting MCP | http | Remote endpoint (mcp-remote bridge for older clients) | Vendor-managed auth (API key/OAuth) - not itemized in registry | communication | yes | yes | detail page |
Both are independent, third-party MCP servers - installing either connects your agent directly to that vendor, not through WingMan.