Developer · Remote MCP server
Bug Bounty Intelligence
AI security scanner for Solidity + free CC0 dataset of Sherlock audit-competition acceptance rates.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.holistis/bug-bounty-intelligence-mcp- Version
- 1.0.3
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-22
- Updated
- 2026-07-22
- Publisher
- holistis (GitHub) · 3 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/holistis) · how
- Website
- github.com/holistis/bug-bounty-intelligence-mcp
- Repository
- github.com/holistis/bug-bounty-intelligence-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://wazir-x402.duckdns.org/api/bug-intel | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 402)
- Handshake
- HTTP 402
- Checked on
- 2026-10-05
How to connect Bug Bounty Intelligence
Bug Bounty Intelligence is a remote MCP server: there is nothing to install. Its endpoint is https://wazir-x402.duckdns.org/api/bug-intel, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from holistis (GitHub)
| Server | Runs |
|---|---|
| 3ilm MCPSearch 1,032 verified contract vulnerability findings from Sherlock audits by pattern. | Local · stdio |
| Capacity AttestSigned delivery claims for x402 capacity trades: GPU-hours, storage, API credits, bandwidth. | Local · stdio |
More developer servers
| Server | Runs |
|---|---|
| Browserbasehq MCP BrowserbaseProvides cloud browser automation capabilities using Stagehand and Browserbase, enabling LLMs to i… | Remote · HTTPLive check: ✗ no handshake |
| BrowserbashPlain-English browser tests for AI agents: real Chrome, deterministic verdicts. Free, no API keys. | Local · stdio |
| BrowserMeshIsolated multi-session Chromium runtime for external MCP clients over stdio. | Local · stdio |
| Bsp MCPPersistent agent memory & identity on federated beaches - one bsp() function over pscale blocks. | Remote · HTTPLive check: ✓ handshake |
| Bug DetectorAnalyzes code for bugs, security vulnerabilities, and code smells. | Local · stdio |
| bugbrain.techBugBrain QA platform for AI coding tools: autonomous exploratory testing, test plans, a11y audits. | Local · stdio |
| BugfenderAccess Bugfender logs, crashes, devices, and user feedback from MCP-enabled clients. | Local · stdio |
| Bugherd MCPBugHerd API v2 integration - 37 tools for projects, tasks, comments, and webhooks. | Local · stdio |