"Using Claude to Check the Current Weather Without an API Key" matching MCP servers:

Enables AI agents to check the live operational status of hundreds of cloud, SaaS and AI providers, returning current state, affected components and active incidents for a named stack so agents can tell a vendor outage apart from their own broken code. It answers from a continuously polled local database, so agents can query stacks, list degraded providers, and review incident history without calling vendor status pages.

MCP server that exposes 31 OSINT checks from Lissy93/web-check as tools for website analysis, including SSL, DNS, headers, WHOIS, and security presets. Enables natural-language-driven web recon and health checks.

Monitors API endpoint health by checking availability, measuring response times, and providing detailed status reports with error handling and timeout protection for the localhost:8080/api/ticket endpoint.

Provides real-time weather forecasts, severe weather alerts, and diagnostic tools from the US National Weather Service, enabling LLMs to fetch meteorological data and monitor server health.

An MCP server that exposes Claude Code's real-time rate limit usage so that an orchestrator can check remaining capacity before launching subtasks.

Reports your Claude subscription usage (5-hour and weekly limits) with a forecast and velocity recommendation, using Claude Code's existing OAuth session without requiring an API key.

Offline Python MCP server that audits Zapier, Make and n8n lead pipelines and lists where inbound leads are silently dropped.

Get information about the current operating environment

Monitor the real-time status of 200+ popular APIs and services. Check if services like GitHub, Stripe, AWS, and Slack are experiencing outages or degraded performance directly from your AI assistant.

A hosted Model Context Protocol server that lets AI agents triage review queues, investigate authors, tune policies and wordlists, respond to incidents, configure projects and webhooks, and report on moderation activity through a Moderation API account.

Provides tools for Claude to query local Claude Code token usage and cost data, enabling spend analysis and insights through natural language.

Health Check AI - MCP server providing AI-powered tools and automation by MEOK AI Labs

Provides Claude plan usage data (session and weekly percentages) as an MCP tool by reading through a logged-in browser, enabling Claude to check its own remaining usage.

Shows your current Claude Desktop activity as Discord Rich Presence, including model, status, usage, and subscription info.

Enables querying and analyzing Claude Desktop/Code conversation history across all users on a machine, including conversation search, token usage statistics, model/tool insights, and opening a web dashboard for detailed visualization.

Measure the network path quality to a voice/VoIP destination and get an estimated MOS (ITU-T G.107 E-model) plus live RTT, jitter, and packet loss. Agent-native: REST + MCP, free tier then pay-per-call via x402.

Enables a Claude Code agent to fetch remaining 5-hour and weekly subscription usage limits, reset times, and per-window breakdowns as JSON. It provides the same figures as /usage through a local, read-only tool.

Enables retrieving real Claude subscription usage statistics, including the 5-hour session window, weekly limit, and per-model limits, from the same endpoint Claude Code uses.

Lets an AI agent check its own Claude and Codex usage limits — used percentages and exact reset times for session and weekly windows — so it can plan long-running work around resets instead of dying mid-task. It reads local, credential-free sources by default, always reports which source answered, and ships a hook that pushes quota state into context automatically.

Read-only AMD GPU monitoring for Claude on Linux — VRAM, temperature, clocks, power, and running ML processes via rocm-smi.

Enables Claude to run safe, read-only diagnostics against servers and websites — certificate chains and expiry, HTTP status/redirects/security headers, DNS records, email authentication (SPF, DKIM, DMARC, MTA-STS, TLS-RPT) and sitemaps. Every check returns severity-tagged findings with concrete fixes, plus a 0-100 score and A-F grade, without any ability to modify the target.

Provides structured access to Claude Code agent log files, allowing agents to query assistant lines and tool calls without reading raw JSONL data.

Fetches and tracks Claude.ai usage data including session and weekly limits with automated daily logging and persistent session management. It allows users to monitor their usage history directly through Claude Code integrated tools.

Provides LLMs with network intelligence capabilities including PTR record lookups, ASN analysis, traceroute enrichment, and real-time network monitoring through The Aleph API.

Maintenance, recovery, and observability for Claude Code. CLI + MCP server + dashboard.

Enables measuring, comparing, and health-checking endpoint response times through natural language, using tools to probe URL latency and compare two URLs.

Manage and monitor Hadoop clusters via Apache Ambari API, enabling service operations, configuration changes, status checks, and request tracking through a unified MCP interface for simplified administration. * Guide: https://call518.medium.com/llm-based-ambari-control-via-mcp-8668a2b5ffb9

Provides comprehensive telemetry and usage analytics for Claude Code sessions, including token usage tracking, cost monitoring, and tool usage patterns. Enables users to monitor their Claude usage with detailed metrics, warnings, and trend analysis.

Bridges with an installed API monitoring application to enable launching and status checks, live background capture, process attach, filter-tree inspection, GUI actions, and opening, validating, decoding, searching, inspecting, exporting, and comparing saved captures and related metadata.

Gives the model visibility into the same 5-hour session, weekly, and per-model usage percentages shown in Claude Code, along with reset times. It also lets a project cap how much of the weekly limit may be spent via start/check/end budget tools that report OK, LOW, or OVER_BUDGET.