Jid: the trust API for AI agents vs AVEL
Jid: the trust API for AI agents is an MCP server published by jid.com. Marketplaces we read that list it: 1 (Official MCP Registry). AVEL is an MCP server published by Ensi81. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  Jid: the trust API for AI agents |  AVEL |
|---|---|---|
| Official MCP Registry | Listed Version: 1.6.0 No figure published Not marked · First seen |
Listed Version: 0.1.2 Downloads/month (PyPI): 403 Downloads/week (PyPI): 47 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 | Jid: the trust API for AI agents | AVEL |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-10-13 | Not published |
| Where it runs (differs) | Remote server (jid.com/mcp) | On your machine (agent-interchange) |
| Transport (differs) | Streamable HTTP | stdio |
| 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/ensi81/avel |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 11 h ago | no remote endpoint we check |
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
Jid: the trust API for AI agents
Verify a business before an agent pays, signs or buys: registry-cited decision and signed receipt.
AVEL
Identity/reputation verification for agent-to-agent payments across x402, AP2, MPP, checkout.
How to run each
Jid: the trust API for AI agents As a remote MCP server
claude mcp add --transport http jid https://jid.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
AVEL As a local MCP server: PyPI package
claude mcp add --env "AVEL_PRIVATE_KEY=<YOUR_AVEL_PRIVATE_KEY>" --transport stdio avel -- uvx agent-interchangeRequires: AVEL_PRIVATE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Jid: the trust API for AI agents has a remote endpoint we 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 Jid: the trust API for AI agents publish no settings it asks for, so we do not compare settings.
What it can do: Jid: the trust API for AI agents · What it can do: AVEL · 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.