Evc Spark MCP vs MCP Gateway — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Evc Spark MCP vs MCP Gateway
In-depth architectural comparison of the Evc Spark MCP and MCP Gateway MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Evc Spark MCP
Aggregators · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
MCP Gateway
Aggregators · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Evc Spark MCP if you need specialized Aggregators tools running via a local process. Choose MCP Gateway if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Evc Spark MCP when:
You need dedicated capabilities in the Aggregators domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: SPARK_API_URL, SPARK_SITE_URL.
Search and discover AI agents, skills, prompts, bundles and MCP connectors from a curated catalog of 4500+ assets.
A meta-server for minimal Claude Code tool bloat with progressive disclosure and dynamic server provisioning. Exposes 9 stable meta-tools, auto-starts Playwright and Context7, and can dynamically provision 25+ MCP servers on-demand from a curated manifest.
Category & Scope
Tools & Capabilities Breakdown
Evc Spark MCP Tools (7)
search_assets
Search the Spark AI assets marketplace. Returns matching agents, skills, prompts, MCP connectors, and bundles. [Trial mode: limited to 5 results. Set SPARK_API_KEY for full access: https://spark.entire.vc/create]
get_asset
Get full details of a Spark asset by its slug. Returns description, files, outcome reports, and more.
get_asset_content
Get the raw content of a Spark asset (prompt text, skill instructions, agent config). This counts as an acquisition and ends with an application_id to report the outcome with.
list_popular
List the most popular Spark assets. Defaults to combined quality+ratings score (combo). Great for discovering top-rated AI tools.
list_categories
List available categories (domains and AI tags) in the Spark marketplace. Useful for filtering searches.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Evc Spark MCP is categorized under Aggregators and uses a local stdio subprocess. In contrast, MCP Gateway belongs to Aggregators using local stdio subprocess. Select Evc Spark MCP when you need capabilities focused on aggregators and MCP Gateway when you require tools for aggregators.
Check your Spark API key status and daily usage. Shows how many assets you've served today and your remaining quota.
report_outcome
Report what happened when you applied an asset you fetched with get_asset_content. Call it once you know: applied as is, applied with changes, broke, or not applicable. The next agent choosing this asset reads the outcomes in search results. Reports made with an API key count; anonymous ones are stored as unverified. Calling again with the same application_id updates your report.
Fields `task`, `note`, `changed_what`, `failed_at`, `expected`, `got` are shown to the asset's author. Do not include client data, private paths, keys, emails or URLs with tokens. Your identity is never shown to the author.
MCP Gateway Tools (26)
gateway.auth_connect
Store credentials for a server and make them available to provisioning. Use this when gateway.provision reports missing authentication.
gateway.cancel
Cancel a pending tool invocation. By default, refuses to cancel healthy requests (recent heartbeat). Use force=true to cancel anyway. Use gateway.list_pending first to see request IDs and health status.
gateway.catalog_search
Search for available tools across all connected MCP servers. Returns compact capability cards without full schemas. Use filters to narrow results by server, tags, or risk level. Set include_offline=True to also discover provisionable servers not yet running. This is the primary tool discovery entry point.
gateway.config_status
Show read-only effective configuration and startup policy status with source attribution and non-secret diagnostics.
gateway.connect_server
Connect or start a known downstream MCP server by name. Resolves configured, provisioned manifest, and registered discovered servers.
gateway.describe
Get detailed information about a specific tool, including its arguments and constraints. Use this before invoking a tool to understand its requirements.
gateway.disconnect_server
Disconnect a running downstream MCP server without changing persistent config. Refuses by default when that server has pending requests; set force=true to cancel them.
gateway.get_startup_policy
Return persisted autoStart and legacy disableAutoStart entries grouped by config source.
gateway.health
Get the health status of the gateway and all connected MCP servers. Shows server status, tool counts, and last refresh time.
gateway.invoke
Invoke a tool on a downstream MCP server. Arguments are validated against the tool schema before execution. Output is automatically truncated if too large.
gateway.list_pending
List all pending tool invocations with health status. Shows elapsed time, heartbeat age, and current state for each request. Use this to monitor long-running operations before deciding to cancel.
gateway.provision
Provision (install and start) a specific MCP server from the manifest. Use this after reviewing candidates from gateway.request_capability. Returns immediately with a job_id for tracking. Poll gateway.provision_status to check progress. Use gateway.request_capability instead if you don't know the exact server name.