Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Runway API MCP ServerJADX-AI-MCP (Part of Zin MCP Suite)

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Chrome DevTools MCPMCP100 RecommendedGoogle Search Console MCP Server for SEOsMCP100 RecommendedGhidra MCP ServerMCP100 RecommendedPlaywright MCPMCP100 RecommendedHugging Face MCPMCP100 RecommendedFramelink MCP for FigmaMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	Runway API MCP ServerShortlist candidate	JADX-AI-MCP (Part of Zin MCP Suite)MCP100 Recommended
Task fit
Best for	AI image and video generation workflows.	Navigating JADX decompilation, searching APK code, and accelerating reverse-engineering or security-analysis hypotheses
Not ideal for	Production use before the documented maturity gaps are resolved	Definitive vulnerability certification, dynamic analysis, or reviewing applications without authorization
Avoid when	The connected identity is broader than the task requires Tool calls cannot be reviewed before consequential mutations	APK contents, decompiled code, or findings cannot be shared with the connected AI client
Provenance
Provenance details	First-party MCP ecosystem:runway-api · Publisher source ↗	Community implementation github:zinja-coder · Publisher source ↗
Maintenance
Maintenance details	Repo: Aug 10, 2026 Package: Not documented	Repo: Sep 23, 2026 Package: Not documented
Popularity evidence
GitHub stars	22 GitHub stars · checked 2026-08-14T18:46:26.000Z	2,822 GitHub stars · checked 2026-09-24T04:14:47.694000Z
Package downloads / 30 days	81 package downloads / 30 days · checked 2026-09-08	No reliable download data
Client coverage
Client coverage details	Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	The official server uses a Runway API key.	The documented default is stdio with the HTTP endpoints on 127.0.0.1. The publisher explicitly warns that binding the MCP server to 0.0.0.0 or another non-localhost address exposes plain HTTP with no authentication or TLS, allowing anyone on that network to invoke all tools.
Cost	The MCP integration has no separately verified MCP100 price conclusion. Publisher subscriptions, API usage, compute, storage, and AI-client charges may apply.	The publisher distributes the project under the Apache License 2.0 and lists no MCP server usage fee. JADX, local compute, the selected MCP client, and model-provider costs can still apply.
Permissions	Runway API credentials, model access, content policy, and account quotas govern generation.	The published tools can read decompiled code for classes and methods, smali, AndroidManifest.xml, string and resource files, cross-references, and debugger frames, threads, and variables from the project open in JADX. They can also rename classes, methods, fields, packages, and variables within the JADX analysis workspace.
Data handling	Authorized service data and tool results pass through the MCP server to the connected AI client. Review the publisher and client data policies before using sensitive ai & reasoning information.	The publisher's architecture sends tool requests from the LLM client through the Python MCP server over HTTP to the JADX-GUI plugin, then returns source, resource, manifest, and debugger data to the connected client. The reviewed README does not document telemetry, retention, or model-training use, so those behaviors remain unknown.
Limitations
Tradeoffs	The repository has a short history, no strong release track record, and requires source-based setup.	JADX integration speeds static exploration, but decompilation is imperfect and AI-generated security conclusions can contain false positives or miss runtime behavior.
Risk context	The repository has a short history, no strong release track record, and requires source-based setup. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.	This server exposes sensitive reverse-engineering material and mutation tools for the APK project open in JADX. Keep both connections on 127.0.0.1 and prefer stdio; if remote access is unavoidable, use a trusted isolated network plus firewall or SSH tunnel. Treat decompiled source, resources, manifests, and debugger values as potentially confidential, and review rename operations before saving or exporting analysis artifacts.
Evidence date
Editorial review	2026-07-30	2026-08-11
Candidate evidence	2026-08-14T18:46:26.000Z	2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →