Integration Health Monitor

OAuth integrations break silently. A user revokes access in their Google account, an admin rotates a client secret, a refresh token expires after 6 months of inactivity — and the first time you notice is when an MCP call fails in production.

MCP Factory watches every integration.

What gets monitored

• Refresh-token validity (test refresh on a schedule)
• Last successful token exchange per user, per integration
• Scope drift (provider revokes scopes the user previously granted)
• Rate-limit headroom from each provider
• Credential expiration windows (where the provider tells us)

How alerts work

Dashboard surfaces broken integrations with a red badge and a clear next action (“Reconnect Google”). Webhooks fire on state change — wire them to Slack, Discord, PagerDuty, whatever.

Why this is in the factory, not your MCP server

You don’t want every MCP server doing its own health checks. The factory is already exchanging tokens — it’s the right place to notice when one stops working.