Legba

Created By
evilsocketa year ago
Legba is a multiprotocol credentials bruteforcer / password sprayer and enumerator built with Rust and the Tokio asynchronous runtime in order to achieve better performances and stability while consuming less resources than similar tools. As of version 0.11.0, Legba supports being used by an AI as an MCP server, refer to the documentation on how to configure it.
Overview

what is Legba?

Legba is a multiprotocol credentials bruteforcer and password sprayer built with Rust and the Tokio asynchronous runtime, designed for better performance and stability while consuming fewer resources than similar tools.

how to use Legba?

To use Legba, follow the building instructions and usage guidelines provided in the project Wiki. You can configure it to work as an MCP server for AI integration.

key features of Legba?

  • Supports multiple protocols including AMQP, FTP, HTTP, IMAP, LDAP, MySQL, and more.
  • High performance due to asynchronous runtime.
  • Can be used as an MCP server for AI applications.

use cases of Legba?

  1. Brute-forcing credentials for various protocols.
  2. Password spraying for user enumeration.
  3. Security testing and vulnerability assessments.

FAQ from Legba?

  • What protocols does Legba support?

Legba supports a wide range of protocols including AMQP, FTP, HTTP, IMAP, and many more.

  • Is Legba resource-efficient?

Yes! Legba is designed to consume fewer resources compared to similar tools.

  • Can Legba be integrated with AI?

Yes! As of version 0.11.0, Legba can be configured to work as an MCP server for AI.

Server Config

{
  "mcpServers": {
    "Legba": {
      "command": "npx",
      "args": [
        "-y",
        "supergateway",
        "--sse",
        "http://127.0.01:3001/sse"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
evilsocket
Star
-
Language
-
License
-
Category
security

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)

a day ago