Hunter MCP Server

Created By
help116114a year ago
An Model Context Protocol (MCP) server that provides access to Hunter API functionality, allowing AI assistants to query information about internet-connected devices and services.
Overview

what is Hunter MCP Server?

Hunter MCP Server is a Model Context Protocol (MCP) server that provides access to Hunter API functionality, enabling AI assistants to query information about internet-connected devices and services.

how to use Hunter MCP Server?

To use Hunter MCP Server, clone the repository, install dependencies, set up your Hunter API key, and start the server. Integrate it with MCP-compatible AI assistants by adding it to your MCP settings.

key features of Hunter MCP Server?

  • Search Functionality: Query Hunter's database using various search criteria such as IP, domain, and protocol/port.
  • Result Sampling: Limit response data to reduce token usage.
  • Resource Management: Access search results as resources with proper URIs.
  • CSV Export: Export search results to a CSV file for further analysis.

use cases of Hunter MCP Server?

  1. Querying information about internet-connected devices for security assessments.
  2. Analyzing large datasets of device information efficiently.
  3. Integrating with AI assistants for enhanced data querying capabilities.

FAQ from Hunter MCP Server?

  • Can I use Hunter MCP Server without an API key?

No, a valid Hunter API key is required to access the functionality.

  • Is there a limit to the number of queries I can make?

Yes, usage limits may apply based on your Hunter API plan.

  • What programming language is Hunter MCP Server built with?

Hunter MCP Server is built using JavaScript and requires Node.js.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
help116114
Star
0
Language
JavaScript
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)

a day ago