Ext Ops Panel
Open dashboard
Comparison

Execute cross-modal-embedding-aligner-mcp vs io.github.runapi-builder/runapi-mcp

Execute cross-modal-embedding-aligner-mcp is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.runapi-builder/runapi-mcp is an MCP server published by runapi-builder. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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

Where each is published
MarketplaceExecute cross-modal-embedding-aligner-mcpio.github.runapi-builder/runapi-mcp
Official MCP Registry Listed
Version: 2.0.0
No figure published
Not marked · First seen
Listed
Version: 0.16.0
Downloads/month (npm): 2 020
Downloads/week (npm): 139
Forks (GitHub): 0
Stars (GitHub): 56
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

Execute cross-modal-embedding-aligner-mcp vs io.github.runapi-builder/runapi-mcp
FactExecute cross-modal-embedding-aligner-mcpio.github.runapi-builder/runapi-mcp
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub56
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-10-15
Where it runs (differs)Remote server (api.m2mcent.com/cross-modal-embedding-aligner-mcp/sse)Remote server (mcp.runapi.ai/mcp)
Transport (differs)SSEStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/runapi-ai/mcp
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 402 (46 h ago)Responded 37 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

Execute cross-modal-embedding-aligner-mcp

In its own words, on Official MCP Registry:

Premium agentic endpoint for cross-modal-embedding-aligner-mcp.

io.github.runapi-builder/runapi-mcp

In its own words, on Official MCP Registry:

130+ AI models for image, video, music, and audio — 18 model families, one RunAPI account.

How to run each

Execute cross-modal-embedding-aligner-mcp As a remote MCP server

Claude Code
claude mcp add --transport sse cross-modal-embedding-aligner-mcp https://api.m2mcent.com/cross-modal-embedding-aligner-mcp/sse --header "Payment-Signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: Payment-Signature header

io.github.runapi-builder/runapi-mcp As a remote MCP server

Claude Code
claude mcp add --transport http runapi-mcp https://mcp.runapi.ai/mcp

Requires: RUNAPI_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only the endpoint of io.github.runapi-builder/runapi-mcp responded at the last daily 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 cross-modal-embedding-aligner-mcp publish no settings it asks for, so we do not compare settings.

What it can do: Execute cross-modal-embedding-aligner-mcp · What it can do: io.github.runapi-builder/runapi-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.

Where the data comes from: how the catalog is built