Google Trends MCP 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.
- Type
- Google Trends MCPMCP Server
- Beacon - verified-merchant index for AI shopping agentsMCP Server
- Category
- Google Trends MCPE-commerce
- Beacon - verified-merchant index for AI shopping agentsE-commerce
- GitHub stars
- Google Trends MCP0
- Beacon - verified-merchant index for AI shopping agents0
- Trust score
- Google Trends MCPNot yet assessed
- Beacon - verified-merchant index for AI shopping agentsNot yet assessed
- Community rating
- Google Trends MCPNo reviews yet
- Beacon - verified-merchant index for AI shopping agentsNo reviews yet
- Last commit
- Google Trends MCPUnknown
- Beacon - verified-merchant index for AI shopping agentsUnknown
- Licence
- Google Trends MCPNone declared
- Beacon - verified-merchant index for AI shopping agentsNone declared
- Official
- Google Trends MCPNo
- Beacon - verified-merchant index for AI shopping agentsNo
- Source
- Google Trends MCPNot available
- 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.