"Implementing the functionality of the akshare library" matching MCP servers:

A verifying MCP gateway that pins approved tool manifests and skill files to content addresses, blocking tampered descriptions before they reach model context.

Read-only MCP server that surfaces UniFi network data from a UCG-Fiber console to Claude, enabling monitoring of hosts, sites, devices, clients, ISP metrics, and device stats via read-only API tools.

Enables natural language interaction with Plausible Analytics data to query traffic, visitors, engagement, and more using conversational questions.

MITM proxy MCP server that intercepts and verifies AI agent tool calls, detecting fabrication, tracking costs, verifying outcomes, and inferring user satisfaction.

Provides MCP tools to create and query SigNoz trace funnels, enabling agents to measure their own step conversion rates from within the agent loop.

Enables measuring the cost of completed agent workflows from runtime session logs and submitting results to the AMI survey.

An MCP server with bearer token authentication implementing tools, resources, and prompts for a mock developer platform API, supporting both stdio and Streamable HTTP transports.

A specialized diagnostic framework that enables AI models to self-diagnose and fix MCP-related issues by analyzing logs, validating configurations, testing connections, and implementing solutions.

Exposes the complete Zabbix API functionality through the Model Context Protocol, mapping API methods to tools for managing hosts, triggers, and monitoring data. It enables seamless integration and control of Zabbix monitoring environments via natural language interfaces.

Ships only the MCP server, not the recorder. Recording works by wrapping a process on the host — a local proxy, a PATH shim, a shadow git index. None of that survives a container boundary, so orca record inside here would watch an empty namespace. What does travel is the read side: the six MCP tools serve runs that already exist on disk, so a client mounts its .orca directory and r

Exposes the LogicMonitor REST API as MCP tools with per-request LMv1 authentication, enabling querying of devices, alerts, reports, and more.

The implementation of Model Context Protocol (MCP) server for VictoriaLogs.

The implementation of Model Context Protocol (MCP) server for VictoriaMetrics

The MCP server provides an interface to the Datadog API, enabling seamless management of incidents, monitoring, logs, dashboards, metrics, traces, and hosts. Its extensible design allows easy integration of additional Datadog APIs for future expansions.

An MCP server that records agent execution metrics and exposes a Context Window Explorer to visualize exactly what entered the model's context window across sessions, tokens, and tool calls.

Provides cryptographically signed, tamper-evident compute usage receipts via a Model Context Protocol server, exposing tools to record usage, verify receipts, list the ledger, and verify ledger integrity without requiring any account, API key, or single cloud provider.

Enables classification of GPU workloads as training, inference, or idle from telemetry data, with tools for one-shot classification, benchmarking, and audit log verification.

Web analytics and AI session replay for agents: visitors, breakdowns, funnels, goals, revenue attribution, and AI-found site issues. Connects to the hosted Flowsery MCP server.

Relays error logs from other MCP servers when an LLM call fails and the returned error message is unclear, helping the model handle errors more intelligently.

Enables systematic investigation of VMware errors and events by correlating event timelines, ranking root-cause hypotheses, and suggesting next diagnostic steps.