mcp-server-ntopng

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is mcp-server-ntopng?

The mcp-server-ntopng is an implementation of a Model Context Protocol (MCP) server for NTOPNG, enabling AI agents to query network monitoring data using the NTOPNG database.

How to use mcp-server-ntopng?

To use the mcp-server-ntopng, configure the server settings in the Claude Desktop application, ensuring that the NTOPNG host and database credentials are correctly set. Then, run the server using the provided commands.

Key features of mcp-server-ntopng?

  • Integration with NTOPNG for network monitoring.
  • Various tools for fetching network data, including interface IDs, host locations, and alert statistics.
  • Support for ClickHouse as a database for storing historical flows and alerts.

Use cases of mcp-server-ntopng?

  1. Monitoring network traffic and identifying top talkers.
  2. Fetching geographical data for network hosts.
  3. Analyzing alert statistics for network performance.

FAQ from mcp-server-ntopng?

  • What is NTOPNG?

NTOPNG is a network traffic analysis tool that provides insights into network performance and usage.

  • How do I configure the server?

Configuration involves editing the Claude Desktop configuration file to include the necessary NTOPNG connection details.

  • Is there support for other databases?

Currently, the server is designed to work with ClickHouse for NTOPNG.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
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.

8 hours ago