com.encompassconfirm/ec360 vs Verifa
com.encompassconfirm/ec360 is an MCP server published by encompassconfirm.com. Marketplaces we read that list it: 1 (Official MCP Registry). Verifa is an MCP server published by Verifa-Solutions. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Verifa | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.17.1 No figure published Not marked · First seen |
Listed Version: 0.1.1 Downloads/month (npm): 67 Downloads/week (npm): 19 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | com.encompassconfirm/ec360 | Verifa |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (encompass-mcp.encompassconfirm.com/mcp) | Remote server (api.withverifa.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/verifa-solutions/verifa-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 h ago, requires a key | Answered with HTTP 307 (6 days ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
com.encompassconfirm/ec360
KYC automation from authoritative public sources. Requires an Encompass licence.
Verifa
Identity verification, document checks, sanctions/PEP screening and case review as agent tools.
How to run each
com.encompassconfirm/ec360 As a remote MCP server
claude mcp add --transport http ec360 https://encompass-mcp.encompassconfirm.com/mcpVerifa As a remote MCP server
claude mcp add --transport http verifa https://api.withverifa.com/mcpRequires: VERIFA_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of com.encompassconfirm/ec360 responded at the last daily check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of com.encompassconfirm/ec360 publish no settings it asks for, so we do not compare settings.
What it can do: com.encompassconfirm/ec360 · What it can do: Verifa · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.