check_ai_site_status — QuintaDB MCP Tool Read-only
check_ai_site_status
(check ai site status) is one of 125 tools on the
QuintaDB
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_ai_site_status from your client
- Claude Code QuintaDB check_ai_site_status run in your project directory
- Claude Desktop QuintaDB check_ai_site_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor QuintaDB check_ai_site_status ~/.cursor/mcp.json
- VS Code QuintaDB check_ai_site_status .vscode/mcp.json
- Zed QuintaDB check_ai_site_status ~/.config/zed/settings.json
- Windsurf QuintaDB check_ai_site_status ~/.codeium/windsurf/mcp_config.json
- Cline QuintaDB check_ai_site_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI QuintaDB check_ai_site_status ~/.gemini/settings.json
- Grok QuintaDB check_ai_site_status .mcp.json (in your project root)
- ChatGPT QuintaDB check_ai_site_status Settings → Connectors → Advanced → Developer mode
- Claude.ai QuintaDB check_ai_site_status Settings → Connectors → Add custom connector
- LangChain QuintaDB check_ai_site_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://quintadb.com.ua/mcpOther tools on this server
- list_projects
- list_forms
- get_form_fields
- get_records
- get_record
- get_rel_id
- create_record
- update_record
- delete_record
- delete_few_records
- bulk_update_records
- update_cell
- upload_file_to_record
- attach_media_to_record
- import_records
- search_records
- get_column_total
- get_metric
- run_action
- get_reports
- get_report_data
- seed_records
- remove_example_records
- create_record_template
- update_record_template
- create_email_template
- create_sms_template
- create_telegram_template
- create_whatsapp_template
- create_formatting
- create_team_group
- list_team_groups
- add_user_to_team_group
- remove_user_from_team_group
- update_team_group
- delete_team_group
- list_portal_groups
- add_user_to_portal_group
- remove_user_from_portal_group
- delete_portal_group
- set_table_permission
- create_action_rule
- create_report
- create_project
- create_form
- create_field
- update_field
- get_field_types
- get_quickstart_guide
- describe_project
- create_portal_group
- configure_chat
- create_portal
- add_portal_menu_item
- list_portal_menu_items
- update_portal_menu_item
- delete_portal_menu_item
- list_dashboard_items
- update_dashboard_item
- add_dashboard_item
- list_portal_users
- invite_portal_user
- delete_portal_user
- list_charts
- create_chart
- list_maps
- create_map
- list_calendars
- create_calendar
- list_portal_pages
- get_portal_page
- generate_ai_site
- generate_ai_project
- delete_field
- list_action_rules
- update_action_rule
- delete_records_by_filter
- update_form
- delete_form
- duplicate_form
- export_records
- list_record_comments
- add_record_comment
- list_webhooks
- create_webhook
- delete_webhook
- list_schedules
- create_schedule
- delete_schedule
- list_reminders
- create_reminder
- delete_reminder
- list_site_blocks
- edit_site_block
- place_media_on_site
- update_portal_page
- update_portal_settings
- set_module_permission
- get_user_info
- list_portals
- delete_project
- reorder_fields
- get_form_settings
- set_column_size
- update_form_settings
- set_field_visibility_rule
- get_relationship
- update_relationship
- list_folders
- create_folder
- duplicate_record
- get_usage_stats
- update_project
- list_saved_views
- create_saved_view
- delete_saved_view
- list_templates
- delete_template
- list_user_roles
- set_user_role
- get_project
- search_image
- web_search
- fetch_url
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.