Graviti vs Beacon verified Merchant index for AI shopping agents
A side-by-side look at the Graviti and Beacon verified Merchant index for AI shopping agents MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Graviti for e-commerce work as a local process; choose Beacon verified Merchant index for AI shopping agents for e-commerce over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Graviti when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
Choose Beacon verified Merchant index for AI shopping agents when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 37/100 · Fair | 36/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Graviti | View Beacon verified Merchant index for AI shopping agents |
Tools & capabilities
Graviti tools
No tool names declared yet. Check the project README from the listing page.
Beacon verified Merchant index for AI shopping agents tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Graviti
{
"mcpServers": {
"graviti": {
"command": "npx",
"args": [
"-y",
"graviti-mcp"
]
}
}
}
Beacon verified Merchant index for AI shopping agents
{
"mcpServers": {
"beacon-verified-merchant-index-for-ai-shopping-agents": {
"url": "https://beacon-index.onrender.com/mcp"
}
}
}
Frequently asked questions
Graviti is categorized under E-Commerce and uses a local stdio subprocess. Beacon verified Merchant index for AI shopping agents belongs to E-Commerce and uses a remote HTTP/SSE transport. Pick Graviti for e-commerce work and Beacon verified Merchant index for AI shopping agents for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Graviti has no declared pricing — check the project's own site. Beacon verified Merchant index for AI shopping agents has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add graviti and beacon-verified-merchant-index-for-ai-shopping-agents as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Graviti has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Beacon verified Merchant index for AI shopping agents has 36/100 (Fair) with 2 views, 0 installs and 0 GitHub stars.