dataproc-us-central1.googleapis.com
https://dataproc-us-central1.googleapis.com/mcp
active Production-safe Score 89/100 http no auth
At a glance
| Endpoint | https://dataproc-us-central1.googleapis.com/mcp |
|---|---|
| Source | https://github.com/melkidonadonmed-lgtm/meu-workspace-global/blob/main/mcp_config.json |
| Transport | http |
| Tools | 17 |
| Auth | none |
| First seen | 2026-09-12 16:35:54 |
| Last checked | 2026-11-17 21:58:29 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 864 / 1180 ms |
| Last successful check | 2026-11-17 21:58:29 |
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:58:29 | ✓ | ✓ | 802 ms | 90 | active |
| 2026-11-17 21:27:05 | ✓ | ✓ | 816 ms | 90 | active |
| 2026-11-17 20:49:17 | ✓ | ✓ | 916 ms | 90 | active |
| 2026-11-17 20:20:21 | ✓ | ✓ | 942 ms | 90 | active |
| 2026-11-17 19:33:32 | ✓ | ✓ | 769 ms | 90 | active |
| 2026-11-17 18:57:09 | ✓ | ✓ | 1019 ms | 86 | active |
| 2026-11-17 18:27:27 | ✓ | ✓ | 1017 ms | 86 | active |
| 2026-11-17 17:46:35 | ✓ | ✓ | 780 ms | 90 | active |
| 2026-11-17 17:00:57 | ✓ | ✓ | 1009 ms | 86 | active |
| 2026-11-17 16:28:10 | ✓ | ✓ | 978 ms | 90 | active |
| 2026-11-17 15:44:42 | ✓ | ✓ | 850 ms | 90 | active |
| 2026-11-17 14:55:54 | ✓ | ✓ | 1012 ms | 86 | active |
| 2026-11-17 14:25:44 | ✓ | ✓ | 888 ms | 90 | active |
| 2026-11-17 13:40:40 | ✓ | ✓ | 812 ms | 90 | active |
| 2026-11-17 12:56:41 | ✓ | ✓ | 925 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://dataproc-us-central1.googleapis.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/dataproc-us-central1-googleapis-com-mcp # JSON