Bloodhound-MCP

Created By
tac01337a year ago
MCP server for bloodhound's api
Overview

what is Bloodhound-MCP?

Bloodhound-MCP is a server implementation for Bloodhound's API, providing a backend service to handle requests and manage data for the Bloodhound application.

how to use Bloodhound-MCP?

To use Bloodhound-MCP, clone the repository, navigate to the project directory, install the dependencies, and run the server using the command python bloodhound_server.py.

key features of Bloodhound-MCP?

  • Implements the API for Bloodhound.
  • Handles data management and request processing.
  • Designed for scalability and reliability.

use cases of Bloodhound-MCP?

  1. Serving as a backend for applications that require Bloodhound's data.
  2. Managing requests and responses for data processing in Bloodhound.
  3. Supporting scalable applications that utilize Bloodhound's API.

FAQ from Bloodhound-MCP?

  • What are the system requirements for Bloodhound-MCP?

Bloodhound-MCP requires a Linux operating system and Python 3.6 or higher.

  • How can I contribute to Bloodhound-MCP?

Contributions are welcome! You can fork the repository, create a new branch for your feature or bugfix, and submit a pull request with a detailed description of your changes.

  • What license is Bloodhound-MCP under?

This project is licensed under the terms of the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tac01337
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago