alloydb.us-east1.rep.googleapis.com
https://alloydb.us-east1.rep.googleapis.com/mcp
active Production-safe Score 88/100 http no auth
At a glance
| Endpoint | https://alloydb.us-east1.rep.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:42:09 |
Observed reliability
| 7-day uptime | 99% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 925 / 1138 ms |
| Last successful check | 2026-11-17 21:42:09 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (17)
list_clusters— List all clusterscreate_cluster— Creates an AlloyDB cluster. ***Requirements*** * The project the cluster is being created in must exist. * The location the cluster is beiget_cluster— Get a clusterlist_instances— List all instances in a clusterrestore_cluster— Restores an AlloyDB cluster from a given backup or a source cluster and a timestamp. ***Requirements*** * Depending on the source type,create_backup— Creates a backup for an AlloyDB cluster. ***Requirements*** * The cluster that the backup is being created for must exist and be in a READcreate_instance— Creates an AlloyDB instance, which is a child resource of a cluster. ***Requirements*** * The cluster that the instance is being created iget_instance— Get an instanceupdate_instance— Updates an AlloyDB instance. ***Requirements*** * The instance that is being updated must exist and be in a READY state. You can use the `create_user— Create a new user in a given project, location, and cluster. ***Requirements*** * The cluster that the user is being created in must existget_user— Get a user in a given project, location, and clusterlist_users— List all users in a given project, location, and clusterexecute_sql— Execute a SQL query on an instance. ***Requirements*** * The cluster must exist and be in a READY state. You can use the `list_clusters`execute_sql_read_only— Execute a SQL query on an instance in read-only mode. ***Requirements*** * The cluster must exist and be in a READY state. You can use texport_data— Exports data from an AlloyDB cluster to a file in Google Cloud Storage. ***Requirements*** * The cluster and primary instance must exist aimport_data— Imports data into an AlloyDB cluster from a file stored in a Google Cloud Storage bucket. ***Requirements*** * The cluster must exist, andget_operation— Gets the status of a long-running operation. ***Usage*** Some tools (for example, `create_cluster` and `create_instance`) return a long-ru
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:42:09 | ✓ | ✓ | 960 ms | 89 | active |
| 2026-11-17 20:57:17 | ✓ | ✓ | 975 ms | 89 | active |
| 2026-11-17 20:34:15 | ✓ | ✓ | 924 ms | 89 | active |
| 2026-11-17 19:48:10 | ✓ | ✓ | 868 ms | 89 | active |
| 2026-11-17 19:25:59 | ✓ | ✓ | 1014 ms | 86 | active |
| 2026-11-17 18:42:14 | ✓ | ✓ | 870 ms | 89 | active |
| 2026-11-17 18:01:38 | ✓ | ✓ | 873 ms | 89 | active |
| 2026-11-17 17:34:27 | ✓ | ✓ | 1025 ms | 86 | active |
| 2026-11-17 16:43:23 | ✓ | ✓ | 986 ms | 89 | active |
| 2026-11-17 16:00:24 | ✓ | ✓ | 1039 ms | 86 | active |
| 2026-11-17 15:25:37 | ✓ | ✓ | 1112 ms | 86 | active |
| 2026-11-17 14:40:42 | ✓ | ✓ | 879 ms | 89 | active |
| 2026-11-17 13:56:04 | ✓ | ✓ | 883 ms | 89 | active |
| 2026-11-17 13:25:46 | ✓ | ✓ | 1024 ms | 86 | active |
| 2026-11-17 12:42:10 | ✓ | ✓ | 1024 ms | 86 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://alloydb.us-east1.rep.googleapis.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/alloydb-us-east1-rep-googleapis-com-mcp # JSON