MCP.so
ログイン

Hunter MCP Server

@help116114

基本情報

カテゴリ

その他

トランスポート

stdio

作者

help116114

Hunter MCP Server について

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.

Hunter MCP Server の設定

標準の設定はありません

このサーバーの README には解析可能な MCP 設定ブロックが含まれていません。インストール手順はリポジトリをご確認ください。

リポジトリ

Hunter MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Hunter MCP Server?

A Model Context Protocol (MCP) server that provides access to Hunter (Qianxin) API functionality, allowing AI assistants to query information about internet-connected devices and services.

How to use Hunter MCP Server?

Clone the repository, install dependencies, build the server, set the Hunter_API_KEY environment variable, and start with npm start. Integrate with Claude or other MCP-compatible assistants by adding the server to your MCP settings with the command node /path/to/build/index.js and the environment variable HUNTER_API_KEY.

Key features of Hunter MCP Server

  • Search Hunter’s database using IP, domain, header, web info, ICP, protocol/port, app components, cert, vul, AS, and TLS‑JARM.
  • Limit response data size to reduce token usage.
  • Provide search results as resources with proper URIs.
  • Export search results to a CSV file.

Use cases of Hunter MCP Server

  • AI assistants query internet‑facing device information by IP or domain.
  • Security analysts export search results to CSV for offline analysis.
  • Developers integrate device discovery into automated workflows.
  • Researchers paginate through large datasets of internet‑connected services.

よくある質問

1

What does the Hunter MCP Server do?

It wraps the Hunter API from Qianxin, enabling AI assistants to search for information about internet-connected devices and services.

2

What are the dependencies or runtime requirements?

Node.js version 14.17 or higher and a valid Hunter API key (obtainable from the Hunter platform) are required.

3

How is authentication handled?

You must set your Hunter API key via the environment variable `Hunter_API_KEY` (or `HUNTER_API_KEY` in MCP settings) before running the server.

4

Where does the data come from?

All data is retrieved live from the Hunter (Qianxin) API; the server does not store any data locally beyond caching search results as resources.

5

What transport does the server use?

The server uses standard I/O (stdio) transport, as typical for MCP servers. The command is `node` with the built `index.js` as argument.

コメント

「その他」の他のコンテンツ