Omnis Venture Intelligence MCP

io.github.HCS412Published by GitHub account HCS412v1.0.0Updated Oct 28, 2026

Venture intelligence for autonomous agents with discovery, scoring, and workspace automation.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint for venture intelligence, letting an assistant discover and score ventures and automate workspaces.

What you can do
  • Discover ventures and surface venture intelligence for agent use
  • Score ventures against the service's criteria
  • Automate workspace tasks through the Omnis platform
  • No individual tools are documented, so exact operations are not listed
When to use it
Worth considering when an assistant needs venture discovery, scoring or workspace automation from a hosted service rather than local data.
Requirements
Remote streamable HTTP endpoint at the provider's site; no local package. Requires an Omnis API key sent in the x-api-key header, described as being for shared or tenant-bound enterprise access. Network access to the provider is needed.
Before you install
The x-api-key header is a required secret; keep it out of logs and shared transcripts. The service is hosted by a third party, so requests and any venture data you submit go to that provider. Write or automation actions are implied by workspace automation but are not documented, so confirm scope before use.

Installation

In SourceWeft

  1. Open Omnis Venture Intelligence MCP in the dashboard and add it to a workspace.
  2. Connect x-api-key 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/io.github.HCS412%2Fventureautomated-omnis/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.

{
  "mcpServers": {
    "omnis-venture-intelligence": {
      "type": "http",
      "url": "https://www.bamboosnow.co/api/v1/mcp",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

35% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • 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.

  • License10 pts

    Declare a license in the repository or the registry entry.