Innguma MCP Server

by innguma Your server? Claim it

answering

Innguma is answering right now. Last checked 3 min ago.

Competitive intelligence and technology monitoring: alerts, sources and news.

Uptime history 7 days of history

7 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

226 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Innguma 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 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.innguma.com/mcp

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

https://mcp.innguma.com/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.innguma.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.innguma.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://mcp.innguma.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.innguma.com/mcp	streamable-http	sign-in	221 ms	3 min ago

Alternatives to Innguma

same job, measured the same way

Intelcue MCP

by intelcue

Market & competitive intelligence for Claude & AI assistants: trends, alerts, keywords & more.

answering

Signallabs MCP

by emresemercioglu

Competitive Intelligence MCP: generate AI battlecards, track competitors, monitor market signals.

58 installs/wk local only

Compete Competitive Intelligence

by niyonzimabryan

Typed access to monitored competitive changes, evidence, dossiers, research, and collection health.

64 installs/wk local only

New Relic MCP Server

by newrelic-partners

Monitor, troubleshoot, and optimize your technology stack with Intelligent Observability.

answering

Agentic News

by agentic-news

AI-powered news intelligence — 21 tools for personalized monitoring, briefings, and semantic search

answering

Uptimely

by getuptimely

Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.

answering

Overdrive Intel

by looney-tic

AI coding ecosystem intelligence — breaking changes, tools, security alerts from 900+ sources

44 installs/wk local only

Sentinel Briefing

by sentinelbriefing

Strategic monitoring and public affairs intelligence: watches, sourced notes, analysed articles.

answering

Innguma — questions

Answers built from our own checks of this server.

Why is there no tool list for Innguma?

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 Innguma 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 226 ms. The bar chart above shows every period we have measured.

How do I connect Innguma?

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 sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Innguma?

No API key is involved. Innguma answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Innguma?

It answers our handshake in 226 ms on average, which is faster than 63% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.