dataproc-asia-south1.googleapis.com
https://dataproc-asia-south1.googleapis.com/mcp
active Production-safe Score 77/100 http no auth
At a glance
| Endpoint | https://dataproc-asia-south1.googleapis.com/mcp |
|---|---|
| Source | https://raw.githubusercontent.com/Krishp091205/gemini-config/main/config/mcp_config.json |
| Transport | http |
| Tools | 17 |
| Auth | none |
| First seen | 2026-08-22 13:15:35 |
| Last checked | 2026-11-17 05:51:15 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 2628 / 2913 ms |
| Last successful check | 2026-11-17 05:51:15 |
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 05:51:15 | ✓ | ✓ | 2631 ms | 85 | active |
| 2026-11-17 04:47:27 | ✓ | ✓ | 6864 ms | 85 | active |
| 2026-11-17 03:49:58 | ✓ | ✓ | 2696 ms | 85 | active |
| 2026-11-17 01:53:35 | ✓ | ✓ | 2773 ms | 85 | active |
| 2026-11-17 00:27:32 | ✓ | ✓ | 2714 ms | 85 | active |
| 2026-11-16 10:26:35 | ✓ | ✓ | 2616 ms | 85 | active |
| 2026-11-16 09:59:47 | ✓ | ✓ | 2641 ms | 85 | active |
| 2026-11-16 09:41:36 | ✓ | ✓ | 2625 ms | 85 | active |
| 2026-11-16 09:23:28 | ✓ | ✓ | 2616 ms | 85 | active |
| 2026-11-16 07:23:19 | ✓ | ✓ | 4477 ms | 85 | active |
| 2026-11-16 05:22:59 | ✓ | ✓ | 2343 ms | 85 | active |
| 2026-11-16 03:22:50 | ✓ | ✓ | 2812 ms | 85 | active |
| 2026-11-16 01:22:42 | ✓ | ✓ | 2764 ms | 85 | active |
| 2026-11-15 23:22:15 | ✓ | ✓ | 2628 ms | 85 | active |
| 2026-11-15 21:21:43 | ✓ | ✓ | 2599 ms | 85 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://dataproc-asia-south1.googleapis.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/dataproc-asia-south1-googleapis-com-mcp # JSON