AtlaSent MCP Server vs Execute dolby-atmos-metadata-mcp
AtlaSent MCP Server is an MCP server published by AtlaSent. Marketplaces we read that list it: 1 (Official MCP Registry). Execute dolby-atmos-metadata-mcp is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  AtlaSent MCP Server | |
|---|---|---|
| Official MCP Registry | Listed Version: 2.21.0 Downloads/month (npm): 1 481 Downloads/week (npm): 127 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.0.0 No figure published 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 | AtlaSent MCP Server | Execute dolby-atmos-metadata-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-27 | Not published |
| Where it runs (differs) | On your machine (@atlasent/mcp-server) | Remote server (api.m2mcent.com/dolby-atmos-metadata-mcp/sse) |
| Transport (differs) | stdio | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/atlasent/atlasent-mcp-server | Not stated |
| 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 402 (23 h 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
AtlaSent MCP Server
AtlaSent for AI agents: with an API key, actions wait for approval with signed proof. No key: demo.
Execute dolby-atmos-metadata-mcp
Premium agentic endpoint for dolby-atmos-metadata-mcp.
How to run each
AtlaSent MCP Server As a local MCP server: npm package
claude mcp add --env "ATLASENT_API_KEY=<YOUR_ATLASENT_API_KEY>" --transport stdio atlasent-mcp-server -- npx -y @atlasent/mcp-serverRequires: ATLASENT_API_KEY (secret)
Execute dolby-atmos-metadata-mcp As a remote MCP server
claude mcp add --transport sse dolby-atmos-metadata-mcp https://api.m2mcent.com/dolby-atmos-metadata-mcp/sse --header "Payment-Signature: <YOUR_PAYMENT_SIGNATURE>"Requires: Payment-Signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Execute dolby-atmos-metadata-mcp 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 Execute dolby-atmos-metadata-mcp publish no settings it asks for, so we do not compare settings.
What it can do: AtlaSent MCP Server · What it can do: Execute dolby-atmos-metadata-mcp · 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.