Editclips vs Whisper

A side-by-side look at the Editclips and Whisper MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

E
EditclipsSpeech-to-Text · Remote HTTP/SSE
Video, audio, and image processing for AI agents: convert, transcribe, upscale - 150+ operations.39FairAuth: no auth required
Whisper logoWhisperSpeech-to-Text · Local subprocess (stdio)Verify Whisper agent identities and look up RDAP for a routable /128 — keyless.61GoodAuth: not declared

Verdict: choose Editclips for speech-to-text work over a hosted endpoint; choose Whisper for speech-to-text as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

E
Choose Editclips when

  • You need dedicated capabilities in the Speech-to-Text domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: No auth required.
Explore Editclips

Whisper logoChoose Whisper when

  • You need dedicated capabilities in the Speech-to-Text domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like whisper_verify, whisper_rdap, whisper_identify.
Explore Whisper

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
E
Editclips
Whisper logoWhisper
CategorySpeech-to-TextSpeech-to-Text
Quality signal39/100 · Fair61/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNo auth requiredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—3
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listed5

Tools & capabilities

Editclips tools

No tool names declared yet. Check the project README from the listing page.

Whisper tools 5

  • whisper_verifyVerify whether an address or FQDN is a real Whisper agent and, if so, whose - running the full keyless trust chain (reverse-DNS + DANE-EE TLSA pin + DNSSEC + JWS identity doc). Returns the verdict as JSON. Use it to check any peer's claimed identity before trusting it. No API key needed.
  • whisper_rdapFetch the RDAP record for a Whisper IPv6 /128 (the IP-anchored registration object: who operates the agent identity, since when, under which tenant). Returns RDAP JSON. Use it to look up ownership/registration facts about an address. No API key needed.
  • whisper_identifyName the vendor and operator role behind a host or IP in one call. Resolves a host/IP to its canonical vendor, category and operator roles (DNS_OPERATOR / CDN / ORIGIN_AS / MAIL_RECEIVER) with a confidence band. No API key needed. Docs: https://www.whisper.security/docs/whisper-graph/procedures/identify
  • whisper_assessGet a labelled threat posture for a host or IP - malicious, benign, or unknown. Returns a posture label + severity band + sub-labels + coverage + evidence for an indicator; benign-allowlisted vs malicious-evidenced, never a bare score. No API key needed. Docs: https://www.whisper.security/docs/whisper-graph/procedures
  • whisper_explainScore an indicator against the threat feeds and explain exactly why. Threat-intel scorer: score + level + human explanation + the feeds it is listed in (feedId, weight, firstSeen/lastSeen). Two live forms: bare CALL explain($v) (full columns) and CALL whisper.explain($v) (restricted YIELD). No API key needed. Docs: https://www.whisper.security/docs/whisper-graph/procedures/explain

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.

Editclips

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-377": {
      "url": "https://editclips.online/docs/guides/mcp"
    }
  }
}

Whisper

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "whisper": {
      "command": "npx",
      "args": [
        "-y",
        "@whisper-security/whisper-mcp"
      ]
    }
  }
}

Frequently asked questions

Editclips is categorized under Speech-to-Text and uses a remote HTTP/SSE transport. Whisper belongs to Speech-to-Text and uses a local stdio subprocess. Pick Editclips for speech-to-text work and Whisper for speech-to-text.

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.

Editclips has no declared pricing — check the project's own site. Auth: no auth required. Whisper 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 mcp-377 and whisper as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Editclips has a quality signal of 39/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Whisper has 61/100 (Good) with 1 views, 0 installs and 3 GitHub stars.