dataproc.googleapis.com
https://dataproc.googleapis.com/mcp
active Production-safe Score 99/100 http no auth
At a glance
| Endpoint | https://dataproc.googleapis.com/mcp |
|---|---|
| Source | https://raw.githubusercontent.com/zchee/agent/main/gemini/settings.json |
| Transport | http |
| Tools | 17 |
| Auth | none |
| First seen | 2026-05-24 03:43:22 |
| Last checked | 2026-11-17 21:44:34 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 105 / 320 ms |
| Last successful check | 2026-11-17 21:44:34 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (17)
list_clusters— List Dataproc clusters in a Google Cloud projectget_cluster— Get a Dataproc cluster in a Google Cloud projectcreate_cluster— Create a Dataproc cluster in a Google Cloud projectdelete_cluster— Delete a Dataproc cluster in a Google Cloud projectlist_jobs— List Dataproc jobs in a Google Cloud projectget_job— Get a Dataproc job in a Google Cloud projectlist_batches— List Dataproc batches in a Google Cloud projectget_batch— Get a Dataproc batch in a Google Cloud projectcreate_batch— Create a Dataproc Batch in a Google Cloud projectdelete_batch— Delete a Dataproc Batch in a Google Cloud projectlist_sessions— List Dataproc Sessions in a Google Cloud projectget_session— Get a Dataproc session in a Google Cloud projectcreate_session— Create a Dataproc Session in a Google Cloud projectterminate_session— Terminate a Dataproc Session in a Google Cloud projectdelete_session— Delete a Dataproc Session in a Google Cloud projectget_operation— Gets the status of a long-running operation. ***Usage*** Some tools (for example, `create_cluster`, `create_batch`, and `create_session`) ranalyze_batch_service— Trigger automated diagnostic analysis for a Dataproc Batch.
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:44:34 | ✓ | ✓ | 237 ms | 96 | active |
| 2026-11-17 21:29:27 | ✓ | ✓ | 80 ms | 99 | active |
| 2026-11-17 21:14:16 | ✓ | ✓ | 76 ms | 99 | active |
| 2026-11-17 20:58:57 | ✓ | ✓ | 97 ms | 99 | active |
| 2026-11-17 20:43:56 | ✓ | ✓ | 76 ms | 99 | active |
| 2026-11-17 20:28:55 | ✓ | ✓ | 78 ms | 99 | active |
| 2026-11-17 20:13:54 | ✓ | ✓ | 116 ms | 96 | active |
| 2026-11-17 19:56:03 | ✓ | ✓ | 83 ms | 99 | active |
| 2026-11-17 19:40:56 | ✓ | ✓ | 73 ms | 99 | active |
| 2026-11-17 19:25:38 | ✓ | ✓ | 88 ms | 99 | active |
| 2026-11-17 19:10:34 | ✓ | ✓ | 83 ms | 99 | active |
| 2026-11-17 18:55:26 | ✓ | ✓ | 76 ms | 99 | active |
| 2026-11-17 18:40:19 | ✓ | ✓ | 92 ms | 99 | active |
| 2026-11-17 18:25:13 | ✓ | ✓ | 83 ms | 99 | active |
| 2026-11-17 18:09:57 | ✓ | ✓ | 245 ms | 96 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://dataproc.googleapis.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/dataproc-googleapis-com-mcp # JSON