helm-watchdog-dify-ai-api-v1-mcp
https://helm-watchdog.dify.ai/api/v1/mcp
active Production-safe Score 90/100 http no auth
At a glance
| Endpoint | https://helm-watchdog.dify.ai/api/v1/mcp |
|---|---|
| Source | https://github.com/sorphwer/dify-helm-watchdog |
| Transport | http |
| Tools | 7 |
| Auth | none |
| First seen | 2026-07-08 07:07:41 |
| Last checked | 2026-11-17 22:00:59 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 789 / 1410 ms |
| Last successful check | 2026-11-17 22:00:59 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (7)
list_versions— Lists all available Dify Helm chart versions with optional validation statistics. Returns version numbers, app versions, creation times, andget_latest_version— Returns information about the most recent Dify Helm chart version, including version number, app version, creation time, and available resouget_version_details— Returns detailed metadata for a specific Helm chart version, including chart URL, digest, and asset locations for values.yaml, images, and vlist_images— Lists all container images declared in a Helm chart version's values.yaml. Optionally includes validation status for each image. For versionget_version_release_notes— Returns the release notes (Details tab content) for a specific Helm chart version as Markdown. For versions >= 3.9.0 the content comes fromvalidate_images— Returns the image validation report for a specific Helm chart version. Shows which images exist in the target registry and their availabilitcompute_upgrade_path— Compute the Dify Enterprise upgrade path between two versions: ordered unskippable versions with stop kinds, summaries, release-note and ver
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 22:00:59 | ✓ | ✓ | 559 ms | 89 | active |
| 2026-11-17 21:45:53 | ✓ | ✓ | 557 ms | 89 | active |
| 2026-11-17 21:30:47 | ✓ | ✓ | 894 ms | 89 | active |
| 2026-11-17 21:15:37 | ✓ | ✓ | 1090 ms | 86 | active |
| 2026-11-17 21:00:09 | ✓ | ✓ | 857 ms | 89 | active |
| 2026-11-17 20:45:05 | ✓ | ✓ | 1098 ms | 86 | active |
| 2026-11-17 20:30:01 | ✓ | ✓ | 731 ms | 89 | active |
| 2026-11-17 20:14:59 | ✓ | ✓ | 677 ms | 89 | active |
| 2026-11-17 19:59:07 | ✓ | ✓ | 832 ms | 89 | active |
| 2026-11-17 19:43:58 | ✓ | ✓ | 954 ms | 89 | active |
| 2026-11-17 19:28:56 | ✓ | ✓ | 1394 ms | 86 | active |
| 2026-11-17 19:13:53 | ✓ | ✓ | 733 ms | 89 | active |
| 2026-11-17 18:57:38 | ✓ | ✓ | 646 ms | 89 | active |
| 2026-11-17 18:42:37 | ✓ | ✓ | 1208 ms | 86 | active |
| 2026-11-17 18:27:35 | ✓ | ✓ | 916 ms | 89 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://helm-watchdog.dify.ai/api/v1/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/helm-watchdog-dify-ai-api-v1-mcp # JSON