Wathba vs Mossgate MCP
A side-by-side look at the Wathba and Mossgate MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
W
WathbaFinance & FintechSaudi payments, OTP/SMS, KYC, ZATCA e-invoicing and shipping for AI coding agents.36FairAuth: oauth 2.0Verdict: choose Wathba for finance & fintech work; choose Mossgate MCP for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
WChoose Wathba when
- You need dedicated capabilities in the Finance & Fintech domain.
- Its auth model fits you: OAuth 2.0.
Choose Mossgate MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: other.
- You have the keys it needs:
MOSSGATE_BUYER_PK.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | W Wathba | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 36/100 · Fair | 45/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | OAuth 2.0 | other |
| Pricing | Not declared | Paid service |
| Required env vars | None listed | MOSSGATE_BUYER_PK |
| Verified owner |
Tools & capabilities
Wathba tools
No tool names declared yet. Check the project README from the listing page.
Mossgate MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Wathba
No confirmed install command for Wathba yet — follow the setup steps linked from its listing page rather than a guessed package name.
Mossgate MCP
{
"mcpServers": {
"mossgate-mcp": {
"url": "https://api.mossgate.dev"
}
}
}
Frequently asked questions
Wathba is categorized under Finance & Fintech and uses an install path we have not confirmed yet. Mossgate MCP belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Wathba for finance & fintech work and Mossgate MCP for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Wathba has no confirmed install command yet — follow its own setup instructions.
Wathba has no declared pricing — check the project's own site. Auth: oauth 2.0. Mossgate MCP is listed as a paid service. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add wathba and mossgate-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Wathba has a quality signal of 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Mossgate MCP has 45/100 (Fair) with 6 views, 0 installs and 0 GitHub stars.