Side-by-side MCP server comparison
Short answer: it is close. app.mailtea/mailtea scores 92/100 and com.fnlowl/fnlowl scores 90/100 - a 2-point gap, which is inside the noise of a weekly rescore. they are close enough on every measure that the deciding factor is which upstream service you already use.
Last updated
| Metric | app.mailtea/mailtea | com.fnlowl/fnlowl |
|---|---|---|
| MCPpedia Score | 92 | 90 |
| Security Score | 30 | 30 |
| Maintenance Score | 17 | 15 |
| GitHub Stars | 0 | 0 |
| Weekly Downloads | 12.4k | 2263.3k |
| Tools | 3 | 3 |
| Est. Token Cost | 450 | 450 |
| Open CVEs | 0 | 0 |
| Health | Active | Active |
| Auth Required | No | No |
| Transport | http | http |
| License | MIT | MIT |
| API Pricing | unknown | unknown |
app.mailtea/mailtea and com.fnlowl/fnlowl are closely matched at the top with scores of 92 and 90. Check each server's detail page to decide which fits your use case.
Compare up to 4 servers: mcppedia.org/compare/server-a-vs-server-b-vs-server-c