"Network Requests" matching MCP servers:

Enables stateless, handle-based tool interaction over the 2026-07-28 MCP protocol, supporting multi-round-trip requests, cacheable results, and an audited execution trail.

Summarizes GitHub discussions, issues, and pull requests by storing data locally for fast, token-efficient responses.

Isolated Docker sandboxes for MCP servers. Read-only root, zero capabilities, network-none by default.

Records Chrome network requests and responses for LLM knowledge bases, and exposes query and browser control capabilities via MCP tools like list_sessions, navigate, and evaluate.

Scans source code for possible Korean compliance risks (PIPA, Network Act, Credit Information Act, E-Commerce Act) and maps findings to specific legal provisions. Runs locally, exposes MCP tools for scanning and law lookup, and does not constitute legal advice. That's hedged (matches the project's "possible risk / not legal advice" rule), keyword-rich for search, and names all four laws.

A Linux system monitoring MCP server that provides real-time information on CPU, memory, disk, network, processes, Docker, security, and more via MCP tools.

A deterministic symbol oracle over a locally built index of the repository: whether a symbol exists, what a file declares, and what changed structurally since the last snapshot. It also ships a PreToolUse guard that stops an Edit/Write referencing a function, constant or type the repo does not declare, before the write lands rather than after the build fails. No LLM, no API keys, no network, no l

Self-hosted Go MCP server that crawls documentation sites into local Markdown/JSONL corpora and lets agents read pages, run crawls, check freshness, and diff changes with zero network access at read time. Single static binary, no CGO, Apache-2.0.

Self-hosted webhook relay and tunnel with Noise NK encryption. Inspect requests, replay webhooks, trace AI pipelines, connect/disconnect tunnels — 13 MCP tools. No tokens or passwords needed.

Enables natural-language interaction with self-hosted Jira and Bitbucket, providing tools for ticket management, pull requests, code review, and git context.

A Bitbucket CLI and MCP server written in Go for managing workspaces, repositories, pull requests, pipelines, issues, and source code. Supports stdio and HTTP transport.

All-in-one homelab management MCP server. Docker monitoring, volume backup/restore (with compose and env files), Wake-on-LAN, network scanning, and multi-server SSH management.

rhizome-mcp is a local-first MCP server for task tracking and coordination of autonomous AI coding agents, providing crash-safe issue claiming, durable project memory, and dependency graphs using SQLite. It enables agents from different MCP-compatible clients to share a consistent view of project work with no accounts, Docker, or network dependency.

Enables AI agents to query cluster-wide network traffic, investigate API calls, and perform root cause analysis using natural language, with access to decrypted TLS traffic and Kubernetes context.

An MCP bridge that lets Codex and Claude Code interact with OpenLinker agents, and allows the host to serve as a callable agent in the OpenLinker network.

MCP server for UniFi Network Controller enabling AI assistants to manage UniFi infrastructure via natural language. It supports firewall rules, IPv6, and uses lazy/eager tool modes to minimize context usage.

Enables interaction with Bitbucket through the Model Context Protocol, allowing users to manage pull requests, add comments, review code, create tasks, and perform other repository operations using natural language.

Enables AI assistants to interact with MAAS (Metal as a Service) infrastructure for machine management, network configuration, and storage management through a standardized JSON-RPC 2.0 interface.

Enables remote control of a Windows desktop via MCP, including screenshots, mouse and keyboard, window management, PowerShell, files, services, registry, scheduled tasks, event log, and network checks.

A policy and audit layer for Model Context Protocol (MCP). MCP Firewall sits transparently between any MCP client (Claude Desktop, Cursor, VS Code, etc.) and an upstream MCP server, allowing you to inspect, allow, block, or audit requests before they reach the server.