Unified Offer Protocol MCP Server vs Beacon - verified-merchant index for AI shopping agents
Side by side on the facts. GitHub figures come straight from each repository; ratings come from signed-in reviewers here.
MetricUnified Offer Protocol MCP ServerMCP ServerBeacon - verified-merchant index for AI shopping agentsMCP Server
- Type
- Unified Offer Protocol MCP ServerMCP Server
- Beacon - verified-merchant index for AI shopping agentsMCP Server
- Category
- Unified Offer Protocol MCP ServerE-commerce
- Beacon - verified-merchant index for AI shopping agentsE-commerce
- GitHub stars
- Unified Offer Protocol MCP Server0
- Beacon - verified-merchant index for AI shopping agents0
- Trust score
- Unified Offer Protocol MCP ServerNot yet assessed
- Beacon - verified-merchant index for AI shopping agentsNot yet assessed
- Community rating
- Unified Offer Protocol MCP ServerNo reviews yet
- Beacon - verified-merchant index for AI shopping agentsNo reviews yet
- Last commit
- Unified Offer Protocol MCP ServerUnknown
- Beacon - verified-merchant index for AI shopping agentsUnknown
- Licence
- Unified Offer Protocol MCP ServerNone declared
- Beacon - verified-merchant index for AI shopping agentsNone declared
- Official
- Unified Offer Protocol MCP ServerNo
- Beacon - verified-merchant index for AI shopping agentsNo
- Source
- Unified Offer Protocol MCP Server Repository
- Beacon - verified-merchant index for AI shopping agents Repository
Highlighted cells win that row on an objective measure. Rows without a clear winner — category, licence, source — are left unmarked. A higher trust score means better auditability and maintenance, not safer code.