Bumblebeereceipt Mcp
Scan and judge developer HTTP endpoints from your agent with signed verdicts and usage receipts instead of ad-hoc curl checks.
Overview
Bumblebee Endpoint Receipt is a MCP server for the Ship phase that scans developer endpoints via a paid remote service and returns structured verdicts, receipts, and usage logs.
What is this MCP server?
- Remote streamable-http MCP at bumblebeereceipt.clauxel.com with Bearer token auth
- Developer endpoint scanner oriented toward structured verdicts and receipts
- Usage logs and reviewer-ready evidence alongside scan results
- Paid Clauxel remote MCP pattern (agent-tools) with server card metadata
- Open-source reference implementation on GitHub (bumblebee-endpoint-receipt-mcp)
- Server version 1.0.0 per registry metadata
- Single remote transport: streamable-http
- Authorization via Bearer token header
What problem does it solve?
Solo builders harden APIs with one-off manual requests and lose track of what was tested, what failed, and what changed between deploys.
Who is it for?
Indie devs shipping REST or webhook surfaces who want agent-driven rescans with audit-style receipts before launch or after infra changes.
Skip if: Teams that need a free, fully local SAST/DAST suite or deep pentest engagement without a paid remote dependency.
What do I get? / Deliverables
After you connect Bearer auth to the remote MCP, agents can re-run endpoint scans and pull consistent verdicts and receipts you can cite in reviews or postmortems.
- Structured endpoint scan verdicts usable in agent workflows
- Receipts and usage logs for reviewer-ready evidence
- Repeatable remote MCP connection for rescans after code or deploy changes
Recommended MCP Servers
Journey fit
Endpoint exposure and misconfiguration are caught before and after release, so the canonical shelf is Ship where security hardening lives. Automated endpoint scanning and verdict receipts map directly to security subphase work: inventory APIs, validate exposure, and keep audit evidence.
How it compares
Paid remote endpoint-scanner MCP with verdict receipts, not a local Claude skill or generic HTTP client snippet.
Common Questions / FAQ
Who is Bumblebee Endpoint Receipt for?
It is for builders and agent users who maintain HTTP endpoints and want scanner verdicts, receipts, and usage logs from a hosted MCP instead of informal manual probing.
When should I use Bumblebee Endpoint Receipt?
Use it during Ship security work when you inventory or re-check dev and staging endpoints, or after you add routes and need a documented pass-or-fail record from the agent.
How do I add Bumblebee Endpoint Receipt to my agent?
Register the remote MCP URL https://bumblebeereceipt.clauxel.com/mcp (streamable-http), set Authorization to a Bearer token from the product website, and point Claude Code, Cursor, or Codex at the server card if your client supports it.