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
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