Innguma

com.inngumaPublished by innguma.comOfficial publisherv0.23.0Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Innguma is a remote MCP server for competitive intelligence and technology monitoring, giving an assistant access to alerts, sources and news.

What you can do
  • Work with competitive intelligence and technology monitoring data: alerts, monitored sources and news.
  • The manifest lists no individual tools, so the exact operations are not documented; expect read-oriented access to alerts, sources and news items.
  • Connects over streamable HTTP to a hosted endpoint, so no local install is needed.
When to use it
Useful when you want an assistant to pull in competitive intelligence or technology monitoring signals — alerts, tracked sources and news — while researching competitors or market developments.
Requirements
A remote MCP endpoint at mcp.innguma.com over streamable HTTP. Authentication is required via OAuth; no environment variables or headers are declared. An Innguma account is presumably needed to authorize, and network access to the endpoint is required.
Before you install
OAuth grants the server access to your Innguma account, so review the scopes requested during authorization. The server handles third-party news and source data, and the specific tools and any write actions are not documented, so verify behavior before relying on it.

Installation

In SourceWeft

  1. Open Innguma in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.innguma%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.23.0LatestOct 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.