VoiceIntel MCP Server

by evozim Your server? Claim it

answering

VoiceIntel is answering right now. Last checked 8 min ago.

Acoustic sentiment parsing and voice veracity analyzer.

Uptime history 91 days of history · worst day 0%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

110 ms

Response time

average over 24h

authentication required

Access

sse

Nothing serious here today

Today is the operative word: we check VoiceIntel every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add voice-intel --transport sse https://voice-intel-mcp.vercel.app/api/mcp

Settings → Connectors → Add custom connector, then paste this address

https://voice-intel-mcp.vercel.app/api/mcp

~/.codex/config.toml

[mcp_servers.voice-intel]
url = "https://voice-intel-mcp.vercel.app/api/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "voice-intel": {
      "url": "https://voice-intel-mcp.vercel.app/api/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "voice-intel": {
      "type": "sse",
      "url": "https://voice-intel-mcp.vercel.app/api/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://voice-intel-mcp.vercel.app/api/mcp	sse	needs auth	297 ms	8 min ago

Alternatives to VoiceIntel

same job, measured the same way

Deepfake-Sentinel

by evozim

Media forensic analyzer auditing audio and video authenticity.

1 tools answering

LaborTrends NLP

by evozim

Labor market trend analyzer utilizing advanced NLP semantic parsing.

answering

FindIP

by findip

Semantic patent search & analysis: find, compare, and analyze patents by meaning.

answering

X-Social Intel

by evozim

Real-time Twitter/X data miner and sentiment parser for autonomous bots.

answering

GoSQLX

by ajitpratap0

SQL validation, formatting, parsing, metadata extraction, linting, and security analysis.

7 tools answering

LLM Pulse

by llm-pulse

AI visibility analytics for brand mentions, citations, sentiment, and GEO reports

answering

Dependency Management MCP Server

by sonatype

Sonatype component intelligence: versions, security analysis, and Trust Score recommendations

3 tools answering

Coinintel

by cloudcorprecords

Crypto market intelligence: prices, sentiment, risk, narratives, funding and signals.

local only

VoiceIntel — questions

Answers built from our own checks of this server.

Why is there no tool list for VoiceIntel?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is VoiceIntel working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 110 ms. The bar chart above shows every period we have measured.

How do I connect VoiceIntel?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does VoiceIntel need an API key?

Yes. Every time we knock, VoiceIntel answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is VoiceIntel?

It answers our handshake in 110 ms on average, which is faster than 89% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.