mcp-ntopng

Created By
marcoega year ago
An MCP server for network monitoring software ntopng
Overview

what is mcp-ntopng?

mcp-ntopng is an MCP server designed for the network monitoring software ntopng, which provides insights into network traffic and performance.

how to use mcp-ntopng?

To use mcp-ntopng, set up the MCP server and configure it to work with ntopng to monitor your network traffic effectively.

key features of mcp-ntopng?

  • Integration with ntopng for real-time network monitoring
  • User-friendly interface for monitoring network performance
  • Support for various network protocols and traffic analysis

use cases of mcp-ntopng?

  1. Monitoring network traffic in real-time for performance optimization
  2. Analyzing network usage patterns to identify bottlenecks
  3. Providing insights for network security assessments

FAQ from mcp-ntopng?

  • What is ntopng?

ntopng is a network traffic monitoring tool that provides insights into network usage and performance.

  • Is mcp-ntopng free to use?

Yes! mcp-ntopng is open-source and available under the MIT license.

  • How can I contribute to mcp-ntopng?

You can contribute by reporting issues, submitting pull requests, or improving documentation on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
marcoeg
Star
0
Language
Python
License
MIT license
Category
monitoring
Tags

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.

24 minutes ago