Bumblebeereceipt Mcp

com.clauxel.bumblebeereceiptPublished by bumblebeereceipt.clauxel.comOfficial publisherv1.0.0Updated Oct 24, 2026

A paid remote MCP for developer endpoint scanner MCP, built to return verdicts, receipts, usage logs

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Paid hosted MCP endpoint that lets an assistant scan developer endpoint exposure, explain package hits, and issue release receipts.

What you can do
  • Scan developer endpoints for exposure and review the results
  • Explain why a particular package was flagged in a scan
  • Issue release receipts as audit-ready evidence of a scan workflow
  • Read past scan history and usage records
When to use it
Useful for coding teams and AI agents that need repeatable endpoint exposure checks plus receipts and audit evidence for releases. Consider it when you want scan results and history delivered through an MCP client rather than a separate dashboard.
Requirements
A remote Streamable HTTP endpoint; no local package or runtime is needed. A paid plan chosen on the product website and a bearer token sent in the Authorization header are required for production calls. The README notes the public repository holds only documentation, not the production source.
Before you install
It is a paid service, so using it involves a plan and likely spending. The bearer token is a credential and must be kept private; anyone holding it can make calls on your behalf. Scan and receipt tools act on your endpoint data and history, and requests go to a third-party hosted service.

Installation

In SourceWeft

  1. Open Bumblebeereceipt Mcp 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/com.clauxel.bumblebeereceipt%2Fbumblebeereceipt-mcp/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": {
    "bumblebeereceipt": {
      "type": "http",
      "url": "https://bumblebeereceipt.clauxel.com/mcp"
    }
  }
}

README

Bumblebee Endpoint Receipt

Hosted MCP for developer endpoint scanner MCP.

Bumblebee Endpoint Receipt is a paid remote MCP endpoint for developer endpoint scanner MCP. It exposes structured JSON tools, a public server card, token-based access, usage receipts, and audit-ready workflow evidence for AI agents and coding teams.

Public Endpoints

Access

This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website.

http
Authorization: Bearer <token>

Unauthenticated browser visits to /mcp return a clear JSON error instead of internal details.

Tools

  • scan_endpoint_exposure
  • explain_package_hit
  • issue_release_receipt
  • read_scan_history

Quick Start

  1. Open the website and choose a plan.
  2. Create or request an API token.
  3. Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
  4. Send JSON-RPC requests with the bearer token.

Useful Links

Status

This repository is a public documentation and directory-submission reference for the hosted service. It does not contain the private production source code.

Source: README.md at commit f5b414c

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% 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
  • License10 pts

    Declare a license in the repository or the registry entry.