dataproc-us-east1.googleapis.com
https://dataproc-us-east1.googleapis.com/mcp
active Production-safe Score 89/100 http no auth
At a glance
| Endpoint | https://dataproc-us-east1.googleapis.com/mcp |
|---|---|
| Source | https://github.com/dgitman/dotfiles/blob/main/dot_gemini/config/mcp_config.json.tmpl |
| Transport | http |
| Tools | 17 |
| Auth | none |
| First seen | 2026-08-18 12:37:24 |
| Last checked | 2026-11-17 21:27:26 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 832 / 1155 ms |
| Last successful check | 2026-11-17 21:27:26 |
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:27:26 | ✓ | ✓ | 853 ms | 90 | active |
| 2026-11-17 20:51:05 | ✓ | ✓ | 1102 ms | 86 | active |
| 2026-11-17 20:21:15 | ✓ | ✓ | 927 ms | 90 | active |
| 2026-11-17 19:41:26 | ✓ | ✓ | 1121 ms | 86 | active |
| 2026-11-17 18:57:24 | ✓ | ✓ | 775 ms | 90 | active |
| 2026-11-17 18:32:18 | ✓ | ✓ | 701 ms | 90 | active |
| 2026-11-17 17:46:54 | ✓ | ✓ | 764 ms | 90 | active |
| 2026-11-17 17:26:41 | ✓ | ✓ | 710 ms | 90 | active |
| 2026-11-17 16:41:22 | ✓ | ✓ | 991 ms | 90 | active |
| 2026-11-17 15:54:58 | ✓ | ✓ | 1112 ms | 86 | active |
| 2026-11-17 14:56:14 | ✓ | ✓ | 763 ms | 90 | active |
| 2026-11-17 14:26:08 | ✓ | ✓ | 1112 ms | 86 | active |
| 2026-11-17 13:41:01 | ✓ | ✓ | 867 ms | 90 | active |
| 2026-11-17 12:57:13 | ✓ | ✓ | 760 ms | 90 | active |
| 2026-11-17 12:40:33 | ✓ | ✓ | 941 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://dataproc-us-east1.googleapis.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/dataproc-us-east1-googleapis-com-mcp # JSON