chronicle.northamerica-northeast2.rep.googleapis.com
https://chronicle.northamerica-northeast2.rep.googleapis.com/mcp
active Production-safe Score 86/100 http no auth
At a glance
| Endpoint | https://chronicle.northamerica-northeast2.rep.googleapis.com/mcp |
|---|---|
| Source | https://github.com/ShadowTag-v2/shadowtagai-monorepo-v2/blob/main/cline_mcp_settings.json |
| Transport | http |
| Tools | 74 |
| Auth | none |
| First seen | 2026-06-05 11:37:03 |
| Last checked | 2026-11-17 21:42:00 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 1306 / 3486 ms |
| Last successful check | 2026-11-17 21:42:00 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (74)
fetch_remediation_actions— Retrieves a filtered list of available SOAR remediation actions (lightweight summaries) for a specific SIEM alert. For each available actiofetch_remediation_actions_details— Validates and retrieves detailed AI instructions and parameter schemas for multiple SOAR remediation actions in a single batch call for a spget_case— Retrieves a single case by its resource name. Fetches all details for a specific case, including its properties (such as priority, stage, alist_case_comments— Lists all case comments for a given case in Google SecOps. Retrieves a paginated list of all comments associated with a specific SOAR case,list_cases— Lists all cases for a given Chronicle instance. Retrieves a paginated list of all cases, allowing for a comprehensive overview of securityupdate_case— Updates an existing case in Google SecOps. Modifies various properties of a specific case. Only the fields provided in the arguments will bget_case_alert— Retrieves a single alert by its resource name. Fetches all details for a specific alert within a case, including its properties (such as stlist_case_alerts— Lists all alerts within a case. This tool also provides `alert_group_identifiers` for each alert. **Workflow Integration:** - Used when anupdate_case_alert— Updates an existing case alert in Google SecOps. **Important Note:** - This tool CANNOT be used to close the *last open alert* in a case.create_case_comment— Creates a new case comment in Google SecOps. Adds a new, structured comment to an existing SOAR case, enabling analysts to log notes, updatexecute_bulk_close_case— Closes one or more cases in bulk. This is the only tool that can change the status of a case to 'CLOSED'. This tool allows for the efficienexecute_manual_action— This is the default tool to use when you are asked to perform an action for which there is no straightforward, built-in tool. The system isget_connector_event— Retrieves a specific connector event associated with a case alert in Chronicle SIEM. Provides detailed information about a single connectorlist_connector_events— Lists all connector events for a given case alert in Chronicle SIEM. Retrieves a paginated list of all connector events associated with a screate_data_table— Create a new data table in Chronicle SIEM by calling the CreateDataTable API. Creates a structured data table that can be referenced in detadd_rows_to_data_table— Add rows to an existing data table in Chronicle SIEM. Adds new data rows to an existing data table, expanding the dataset available for detlist_data_tables— List data tables in Chronicle SIEM. Retrieves a list of data tables available in the Chronicle SIEM instance. This is useful for discoverinlist_data_table_rows— List rows in a data table in Chronicle SIEM. Retrieves and displays the contents of a data table, showing all rows and their data. This isdelete_data_table_row— Delete a specific row from a data table in Chronicle SIEM. Removes a single row from a data table based on its row ID. This action cannot bgenerate_threat_detection_opportunity— Generates a Threat Detection Opportunity (TDO) for a given threat, which can be a GTI campaign, or a new threat described by the user from agenerate_synthetic_events— Generates synthetic events (both raw logs and enriched UDM) for a given Threat Detection Opportunity (TDO). This tool leverages an LLM to cevaluate_rule_coverage— Evaluates rule coverage for a given set of synthetic UDM events by checking if any existing managed rules match them. This tool is essentiaevaluate_rule_coverage_long_running— Evaluates rule coverage for a given set of synthetic UDM events by ingesting them into the customer environment and initiating evaluation.generate_rules— Generates one or more YARA-L (YL2) rules based on the provided Threat Detection Opportunity (TDO). Creates draft detection rules and initiasummarize_entity— Look up an entity (IP, domain, hash, user, etc.) in Chronicle SIEM for enrichment. Provides a comprehensive summary of an entity's activityget_involved_entity— Retrieves a specific involved entity associated with a case alert in Chronicle SIEM. Provides detailed information about a single involvedlist_involved_entities— Lists all involved entities for a given case alert in Chronicle SIEM. Retrieves a paginated list of all entities associated with a specificsearch_entity— Search for entities within the SOAR platform. Identifies the entity type and retrieves relevant data associated with a specified indicator.udm_search— Search for security events in Chronicle SIEM using a UDM query. Executes a Unified Data Model (UDM) query against Chronicle event logs withtranslate_udm_query— Translates a natural language question or statement into a Chronicle UDM search query. Use this tool to convert a human-readable search dessearch_raw_logs— Search raw telemetry or event logs that have been ingested into SecOps. Executes a raw log search query against SecOps raw logs within a spimport_logs— Ingest raw logs directly into Chronicle SIEM. Allows ingestion of raw log data in various formats (JSON, XML, CEF, etc.) into Chronicle forlist_feeds— List all feeds configured in Chronicle. Retrieves a list of all feeds that are configured in the Chronicle instance, providing details suchget_feed— Get detailed information about a specific feed. Retrieves complete configuration details for a specified feed by its ID, including connectienable_feed— Enable an inactive feed in Chronicle. Activates a feed that is currently in the INACTIVE state, allowing it to resume data ingestion. **Wodisable_feed— Disable an active feed in Chronicle. Stops data ingestion for a feed by setting its state to INACTIVE. The feed configuration remains but ndelete_feed— Delete a feed from Chronicle. Permanently removes a feed from Chronicle. This action cannot be undone and will stop any data ingestion fromcreate_feed— Create a new feed in Chronicle. Creates a new feed configuration for ingesting security data. **Agent Responsibilities:** - Construct theupdate_feed— Update an existing feed in Chronicle. Modifies the configuration of an existing feed. **Agent Responsibilities:** - Provide the `feed` obgenerate_feed_secret— Generate authentication secret for a feed. Generates a new secret for https push feeds which do not support jwt tokens. This replaces any elist_integrations— Lists all SOAR Integrations for a given Chronicle instance. The `name` field in the response contains the resource name of the integration,list_integration_actions— Lists all the actions for a given SOAR Integration. You can also list actions across *all* integrations by passing "-" as the integration_idlist_integration_instances— Lists all configured instances for a given SOAR Integration. You can also list instances across *all* integrations by passing "-" as the intget_ioc_match— Get Indicators of Compromise (IoCs) matches from Chronicle SIEM. Retrieves IoCs (e.g., malicious IPs, domains, hashes) from configured threlist_playbook_instances— Lists all execution instances of playbooks for a given case or alert. Retrieves a historical list of all playbooks that have been run on alist_playbooks— Lists all available playbooks for a given Chronicle instance. Retrieves a list of all configured playbooks (automated workflows), allowinglist_security_alerts— List security alerts directly from Chronicle SIEM. Retrieves a list of recent security alerts generated within Chronicle, based on detectioget_security_alert— Get a specific security alert by its ID directly from Chronicle SIEM. Retrieves a specific alert's details including rule name, creation tiupdate_security_alert— Update security alert attributes directly in Chronicle SIEM. Modifies specific fields of an existing security alert (status, severity, verdget_parser— Get details of a specific parser in Chronicle. Retrieves the configuration and metadata for a specific parser, including its current state,run_parser— Run a parser against sample logs to test parsing logic. Tests parser configuration against sample log entries to validate parsing logic befactivate_parser— Activate a parser for a specific log type in Chronicle. Activates a parser, making it the active parser for the specified log type. Once accreate_parser— Create a new parser for a specific log type in Chronicle. Creates a custom parser using Chronicle's parser configuration language to transfdeactivate_parser— Deactivate a parser for a specific log type in Chronicle. Deactivates a parser, stopping it from processing incoming logs of the specifiedlist_parsers— List all parsers for a given log type, returning only metadata. Retrieves a list of parser metadata for a specific log type, or for all loglist_log_types— List all log types available for a customer. Retrieves a list of all available log types for a specific customer, which is useful for discolist_rules— List security detection rules configured in Chronicle SIEM, with support for pagination and filtering. Retrieves the definitions of detectilist_rule_errors— Lists execution errors for a specific Chronicle SIEM rule. Helps in troubleshooting rules that might not be generating detections as expectcreate_rule— Create a new detection rule in Chronicle SIEM. Creates a new YARA-L 2.0 detection rule in Chronicle that can generate alerts when the ruleget_rule— Get the definition and metadata of a specific Chronicle SIEM detection rule. Retrieves the full details of a rule, including its YARA-L cod
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:42:00 | ✓ | ✓ | 1237 ms | 85 | active |
| 2026-11-17 20:57:09 | ✓ | ✓ | 1435 ms | 85 | active |
| 2026-11-17 20:33:54 | ✓ | ✓ | 1159 ms | 85 | active |
| 2026-11-17 19:43:37 | ✓ | ✓ | 2948 ms | 85 | active |
| 2026-11-17 19:18:17 | ✓ | ✓ | 1306 ms | 85 | active |
| 2026-11-17 18:42:06 | ✓ | ✓ | 1262 ms | 85 | active |
| 2026-11-17 17:57:54 | ✓ | ✓ | 4977 ms | 85 | active |
| 2026-11-17 17:31:41 | ✓ | ✓ | 1162 ms | 85 | active |
| 2026-11-17 16:42:45 | ✓ | ✓ | 1205 ms | 85 | active |
| 2026-11-17 16:00:17 | ✓ | ✓ | 1309 ms | 85 | active |
| 2026-11-17 15:25:29 | ✓ | ✓ | 1171 ms | 85 | active |
| 2026-11-17 14:40:34 | ✓ | ✓ | 1192 ms | 85 | active |
| 2026-11-17 13:43:11 | ✓ | ✓ | 1307 ms | 85 | active |
| 2026-11-17 13:25:39 | ✓ | ✓ | 1145 ms | 85 | active |
| 2026-11-17 12:42:02 | ✓ | ✓ | 1169 ms | 85 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://chronicle.northamerica-northeast2.rep.googleapis.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/chronicle-northamerica-northeast2-rep-googleapis-com-mcp # JSON