looker.viganoaltostrat.com
https://looker.viganoaltostrat.com/mcp
active Production-safe Score 95/100 http no auth
At a glance
| Endpoint | https://looker.viganoaltostrat.com/mcp |
|---|---|
| Source | https://raw.githubusercontent.com/francescoviganogoogle/looker-plugin/main/looker-plugin/mcp_config.json |
| Transport | http |
| Tools | 42 |
| Auth | none |
| First seen | 2026-08-18 13:24:47 |
| Last checked | 2026-11-17 22:00:02 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 308 / 629 ms |
| Last successful check | 2026-11-17 22:00:02 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (42)
add_dashboard_element— This tool creates a new tile (element) within an existing Looker dashboard. Tiles are added in the order this tool is called for a given `daadd_dashboard_filter— This tool adds a filter to a Looker dashboard. CRITICAL ORDER OF OPERATIONS: 1. Create a dashboard using `make_dashboard`. 2. Add all desircreate_project_directory— This tool creates a new directory within a specified LookML project. Prerequisite: The Looker session must be in Development Mode. Use `devcreate_project_file— This tool creates a new LookML file within a specified project, populating it with the provided content. Prerequisite: The Looker session mcreate_view_from_table— This tool generates boilerplate LookML views directly from the database schema. It does not create model or explore files, only view files idelete_project_directory— This tool permanently deletes a specified directory within a LookML project. Prerequisite: The Looker session must be in Development Mode.delete_project_file— This tool permanently deletes a specified LookML file from within a project. Use with caution, as this action cannot be undone through the Adev_mode— This tool allows toggling the Looker IDE session between Development Mode and Production Mode. Development Mode enables making and testing cgenerate_embed_url— This tool generates a signed, private embed URL for specific Looker content, allowing users to access it directly. Parameters: - type (requget_connection_databases— This tool retrieves a list of databases available through a specified Looker connection. This is only applicable for connections that supporget_connection_schemas— This tool retrieves a list of database schemas available through a specified Looker connection. Parameters: - connection_name (required): Tget_connection_table_columns— This tool retrieves a list of columns for one or more specified tables within a given database schema and connection. Parameters: - connectget_connection_tables— This tool retrieves a list of tables available within a specified database schema through a Looker connection. Parameters: - connection_namget_connections— This tool retrieves a list of all database connections configured in the Looker system. Parameters: This tool takes no parameters. Output:get_dashboards— This tool searches for saved dashboards in a Looker instance. It returns a list of JSON objects, each representing a dashboard. Search Paraget_dimensions— This tool retrieves a list of dimensions defined within a specific Looker explore. Dimensions are non-aggregatable attributes or characterisget_explore— This tool retrieves detailed metadata about a specific Looker explore, including its constraints and rules (e.g., `always_filter`, `conditioget_explores— This tool retrieves a list of explores defined within a specific LookML model. Explores represent a curated view of your data, typically joiget_field_value_suggestions— This tool retrieves distinct value suggestions for a field, facilitating accurate filtering in downstream queries. Required Parameters: - mget_filters— This tool retrieves a list of "filter-only fields" defined within a specific Looker explore. These are special fields defined in LookML specget_lookml_tests— Returns a list of tests which can be run to validate a project's LookML code and/or the underlying data, optionally filtered by the file id.get_looks— This tool searches for saved Looks (pre-defined queries and visualizations) in a Looker instance. It returns a list of JSON objects, each reget_measures— This tool retrieves a list of measures defined within a specific Looker explore. Measures are aggregatable metrics (e.g., total sales, averaget_models— This tool retrieves a list of available LookML models in the Looker instance. LookML models define the data structure and relationships thatget_parameters— This tool retrieves a list of parameters defined within a specific Looker explore. LookML parameters are dynamic input fields that allow useget_project_directories— This tool retrieves the list of directories within a specified LookML project. Parameters: - project_id (required): The unique ID of the Loget_project_file— This tool retrieves the raw content of a specific LookML file from within a project. Parameters: - project_id (required): The unique ID ofget_project_files— This tool retrieves a list of all LookML files within a specified project, providing details about each file. Parameters: - project_id (reqget_projects— This tool retrieves a list of all LookML projects available on the Looker instance. It is useful for identifying projects before performinghealth_analyze— This tool calculates the usage statistics for Looker projects, models, and explores. Parameters: - action (required): The type of resourcehealth_pulse— This tool performs various health checks on a Looker instance. Parameters: - action (required): Specifies the type of health check to perfohealth_vacuum— This tool identifies and suggests LookML models or explores that can be safely removed due to inactivity or low usage. Parameters: - actionmake_dashboard— This tool creates a new, empty dashboard in Looker. Dashboards are stored in the user's personal folder, and the dashboard name must be uniqmake_look— This tool creates a new Look (saved query with visualization) in Looker. The Look will be saved in the user's personal folder, and its namequery— This tool runs a query against a LookML model or executes a saved query by ID/slug and returns the results in JSON format. Parameters (provquery_sql— This tool generates the underlying SQL query that Looker would execute against the database for a given set of parameters. It is useful forquery_url— This tool generates a shareable URL for a Looker query, allowing users to explore the query further within the Looker UI. It returns the genrun_dashboard— This tool executes the queries associated with each tile in a specified dashboard and returns the aggregated data in a JSON structure. Pararun_look— This tool executes the query associated with a saved Look and returns the resulting data in a JSON structure. Parameters: - look_id (requirrun_lookml_tests— This tool runs LookML tests in the project, filtered by file, test, and/or model. These filters work in conjunction (logical AND). Prerequiupdate_project_file— This tool modifies the content of an existing LookML file within a specified project. Prerequisite: The Looker session must be in Developmevalidate_project— This tool checks a LookML project for syntax errors. Prerequisite: The Looker session must be in Development Mode. Use `dev_mode: true` fir
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 22:00:02 | ✓ | ✓ | 230 ms | 94 | active |
| 2026-11-17 21:44:56 | ✓ | ✓ | 143 ms | 94 | active |
| 2026-11-17 21:29:51 | ✓ | ✓ | 154 ms | 94 | active |
| 2026-11-17 21:14:38 | ✓ | ✓ | 158 ms | 94 | active |
| 2026-11-17 20:59:19 | ✓ | ✓ | 154 ms | 94 | active |
| 2026-11-17 20:44:19 | ✓ | ✓ | 161 ms | 94 | active |
| 2026-11-17 20:29:18 | ✓ | ✓ | 309 ms | 91 | active |
| 2026-11-17 20:14:13 | ✓ | ✓ | 195 ms | 94 | active |
| 2026-11-17 19:57:36 | ✓ | ✓ | 186 ms | 94 | active |
| 2026-11-17 19:42:36 | ✓ | ✓ | 185 ms | 94 | active |
| 2026-11-17 19:27:36 | ✓ | ✓ | 314 ms | 91 | active |
| 2026-11-17 19:12:36 | ✓ | ✓ | 240 ms | 94 | active |
| 2026-11-17 18:55:44 | ✓ | ✓ | 153 ms | 95 | active |
| 2026-11-17 18:40:38 | ✓ | ✓ | 322 ms | 91 | active |
| 2026-11-17 18:25:31 | ✓ | ✓ | 304 ms | 91 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://looker.viganoaltostrat.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/looker-viganoaltostrat-com-mcp # JSON