bumi company research

dev.freysa.bumiPublished by bumi.freysa.devOfficial publisherv1.0.0Updated Oct 28, 2026

Turn a company domain into a structured B2B sales brief from their public website.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that turns a company domain into a structured B2B sales brief built from the company's public website.

What you can do
  • Research a company from its domain and return a structured B2B sales brief.
  • Draw on the company's public website as the source for the brief.
  • No individual tools are listed, so the exact operations are not documented.
When to use it
Useful when you need a quick, structured profile of a prospect or company for sales, outreach or account research, starting from nothing more than a domain name.
Requirements
A remote streamable HTTP endpoint at bumi.freysa.dev; no packages, environment variables or headers are declared. The manifest declares no authentication, so no account or API key setup is described.
Before you install
The brief is generated from public website content, so its accuracy depends on what the site says and it may be incomplete or outdated. No authentication is declared, so consider what company domains you submit and whether that reveals confidential prospect lists.

Installation

In SourceWeft

  1. Open bumi company research in the dashboard and add it to a workspace.
  2. 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/dev.freysa.bumi%2Fcompany-research/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": {
    "bumi-company-research": {
      "type": "http",
      "url": "https://bumi.freysa.dev/mcp/"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

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

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

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