Preface

After integrating a dozen MCP connectors, the most common issue isn’t usually “failing to connect,” but rather “silent disconnection.” For platforms like Lexiang, Tencent Docs, QQ Mail, Xiaohongshu, and GitHub, you might not realize credentials were authorized six months ago until a call returns a 401 error one day. Digging through configurations and testing connectivity client-by-client is a repetitive, low-tech task. The Connector Status Manager condenses this into a single audit: listing currently connected platforms, displaying online/offline status, checking if credentials are nearing expiration, and providing reconnection and re-authorization steps for offline or expired items. The entire process is read-only and does not modify any configurations.

What is this

The Connector Status Manager (@user_af163eaa/z-connector-health, version 1.0.0) is a diagnostic Skill for AI agent developers, published and maintained by community developer user_af163eaa, and hosted under the ai-agent category on SkillHub.

It solves the following problem: when you or a user asks, “Which platforms are currently connected?”, “Is the connection working?”, or “Are credentials about to expire?”, the Agent needs a structured, actionable list of connectivity and credential statuses, rather than requiring the user to manually check each platform’s backend.

It does not create connections, nor does it fix them. Its positioning is strictly a read-only diagnostic tool.

Core Features

  1. One-click Inventory: Scans currently connected connectors/MCPs covering common platforms like Lexiang, Tencent Docs, QQ Mail, Xiaohongshu, GitHub, etc., outputting a structured list rather than prose.
  2. Itemized Status: Displays online/offline status for each item, distinguishing between “connected but not communicating” and “not connected at all.”
  3. Credential Check: Checks if connector credentials are nearing expiration or require re-login.
  4. Actionable Guidance: Provides executable steps for reconnection and re-authorization for offline or expired items, rather than just saying “please re-authorize.”
  5. Read-Only Diagnostics: It does not write to configurations, rewrite connections, or click authorization buttons for you. This is crucial for diagnostic tools to avoid altering the environment state during the diagnostic process itself.

Installation and Activation

The official page does not provide an independent installation command, only the SkillHub coordinates:

@user_af163eaa/z-connector-health

You can obtain this Skill directly from the SkillHub page. If your client supports manual placement, simply place the SKILL.md file into the client’s Skills directory according to its specifications; directory paths vary by client, so please refer to your specific client’s documentation.

The official tag is requires_api_key=false, meaning no additional API Key application is needed to invoke this Skill—it merely reads the status of your existing connectors.

Typical Usage

The trigger scenarios are based on natural language questions; there are no parameters to memorize:

Connector status
Check what's connected
Is the connection working?
Is MCP online?
Connector health check
Credential expiration check
Which platforms are connected?
Connection diagnostics

In an Agent conversation, simply say “Help me perform a connector health check.” It will return the online status and credential status of currently connected platforms and provide next-step guidance for items that need attention.

Use Cases and Notes

Who it’s for: Developers using Cursor, Claude Code, or other Agent clients supporting MCP/Connectors who have integrated multiple third-party platforms (documents, email, social, code hosting); also for teams where configurations are maintained by multiple people and credential ownership is unclear.

Points to note:

  1. Diagnostic results depend on the connector list actually exposed by the Agent runtime. If a connector is not registered in the current session, it will not appear in the list—it’s not broken, it just isn’t connected yet.
  2. It provides steps for reconnection and re-authorization, but does not auto-fix. Authorization actions involve platform login pages and still require manual completion.
  3. The threshold for “nearing expiration” is determined by the Skill’s own logic; official documentation does not specify a number of days. If a credential appears unusable to you but isn’t marked as such, simply reconnect manually based on the actual error.
  4. Read-only does not mean risk-free: it initiates connectivity probe requests. In environments with strict egress policies, probes may be blocked by the network layer. In this case, reported offline statuses should be judged in conjunction with network logs rather than rushing to re-authorize.

Conclusion

When there are many connectors, questions like “Are they connected, communicating, and how long are credentials valid?” shift from personal memory issues to environmental state issues. The Connector Status Manager answers these three points with a single read-only audit and lists items requiring manual intervention separately.

Official Address: https://api.skillhub.cn/user_af163eaa/z-connector-health
SkillHub Page: https://www.skillhub.cn/skills/user_af163eaa/z-connector-health

Currently, SkillHub shows a rating of 100000, 1174 downloads, and 0 installations.