XAPS MCP Server vs XGuard — Agent Execution Gateway
XAPS MCP Server is an MCP server published by APMC1. Marketplaces we read that list it: 1 (Official MCP Registry). XGuard — Agent Execution Gateway is an MCP server published by moelayyan90. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Downloads/month (PyPI): 159 Downloads/week (PyPI): 55 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 5.2.0 Forks (GitHub): 1 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 | XAPS MCP Server | XGuard — Agent Execution Gateway |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (xaps-sdk) | Remote server (api.xguardgate.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/apmc1/xaps-sdk | github.com/moelayyan90/xguard |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 308 (5 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
XAPS MCP Server
Pre-execution audit for autonomous agents. Independent receipt before irreversible actions.
XGuard — Agent Execution Gateway
Scoped agent execution. Server-side credentials, policy, budgets and verifiable receipts.
How to run each
XAPS MCP Server As a local MCP server: PyPI package
claude mcp add --env "XAPS_AGENT_KEY=<YOUR_XAPS_AGENT_KEY>" --transport stdio xaps -- uvx xaps-sdk
Requires: XAPS_AGENT_KEY (secret)
XGuard — Agent Execution Gateway As a remote MCP server
claude mcp add --transport http xguard-control-plane https://api.xguardgate.com/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only XGuard — Agent Execution Gateway 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 XGuard — Agent Execution Gateway publish no settings it asks for, so we do not compare settings.
What it can do: XAPS MCP Server · What it can do: XGuard — Agent Execution Gateway · 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.