trigger_test — validoria mcp MCP Tool
trigger_test
(trigger test) is one of 74 tools on the
validoria mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call trigger_test from your client
- Claude Code validoria mcp trigger_test run in your project directory
- Claude Desktop validoria mcp trigger_test ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor validoria mcp trigger_test ~/.cursor/mcp.json
- VS Code validoria mcp trigger_test .vscode/mcp.json
- Zed validoria mcp trigger_test ~/.config/zed/settings.json
- Windsurf validoria mcp trigger_test ~/.codeium/windsurf/mcp_config.json
- Cline validoria mcp trigger_test ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI validoria mcp trigger_test ~/.gemini/settings.json
- Grok validoria mcp trigger_test .mcp.json (in your project root)
- ChatGPT validoria mcp trigger_test Settings → Connectors → Advanced → Developer mode
- Claude.ai validoria mcp trigger_test Settings → Connectors → Add custom connector
- LangChain validoria mcp trigger_test pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http validoria-mcp https://api.teste.no/api/mcpOther tools on this server
- guest_start_scan
- guest_get_scan
- list_targets
- get_target
- get_target_scores
- list_findings
- get_finding
- list_incidents
- get_incident
- list_runs
- get_run
- active_runs
- team_stats
- target_stats
- daily_trends
- get_site_map
- list_maintenance_windows
- list_tests
- trigger_all_tests
- acknowledge_incident
- resolve_incident
- mute_finding
- create_maintenance_window
- delete_maintenance_window
- record_deployment
- recompute_scores
- list_automation_rules
- get_automation_rule
- create_automation_rule
- update_automation_rule
- delete_automation_rule
- list_journeys
- get_journey
- create_journey
- update_journey
- delete_journey
- trigger_journey
- list_scheduled_reports
- create_scheduled_report
- update_scheduled_report
- delete_scheduled_report
- get_team_settings
- update_team_settings
- list_notification_rules
- create_notification_rule
- update_notification_rule
- delete_notification_rule
- list_notification_channels
- list_keywords
- add_keyword
- remove_keyword
- start_load_test
- cancel_load_test
- get_load_test
- list_load_tests
- list_secrets
- store_secret
- rotate_secret
- delete_secret
- list_page_fragments
- create_page_fragment
- update_page_fragment
- delete_page_fragment
- create_target
- update_target
- delete_target
- analyze_target
- import_targets
- create_muting_rule
- system_health
- update_test
- enable_all_tests
- disable_all_tests
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.