BinoculoMCP

Created By
girormea year ago
Banner grabbing with LLM (MCP Server)
Overview

What is BinoculoMCP?

BinoculoMCP is a Message Control Protocol (MCP) Server designed to facilitate banner-grabbing operations by interacting with the Binoculo tool.

How to use BinoculoMCP?

To use BinoculoMCP, ensure you have the prerequisites installed, including Python3 and the Binoculo server. You can run specific commands to grab banners from defined IP ranges.

Key features of BinoculoMCP?

  • Banner Grabbing: Perform operations to identify services running on specific IP addresses.
  • Customizable Queries: Tailor your banner-grabbing tasks with specific targets and filters.
  • Active Development: The project is continuously being improved with new features.

Use cases of BinoculoMCP?

  1. Identifying web servers in a network for security assessments.
  2. Gathering information for penetration testing.
  3. Assisting in bug bounty programs by automating banner grabbing tasks.

FAQ from BinoculoMCP?

  • What is banner grabbing?

Banner grabbing is a technique used to gather information about services running on a server by retrieving the banners they present.

  • Is BinoculoMCP free to use?

Yes! BinoculoMCP is open-source and available for anyone to use and contribute to.

  • How can I contribute to BinoculoMCP?

Contributions are welcome! You can open issues or submit pull requests on the project's GitHub page.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
girorme
Star
1
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago