QuintaDB
REMOTE · QUINTADB.COM.UA
No-code databases, forms, portals and AI sites. Manage records and automation via natural language.
Available components
Last scanned (2 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Databases
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_record). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 31312 tokens (~196/item across 159 items; 159 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management99
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 13 additions. See how to fix → Fail
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 32 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 160 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Tool “delete_dashboard_item” rewrote its description, which is the text the model reads security
- “delete_dashboard_item” added an optional parameter “item_ids” cosmetic
- “delete_dashboard_item” reworded the description of “item_id” cosmetic
- “delete_dashboard_item” made “item_id” optional cosmetic
- 27 Oct 26 0
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- Tool “update_project” rewrote its description, which is the text the model reads security
- Tool “list_saved_views” rewrote its description, which is the text the model reads security
- Tool “create_field” rewrote its description, which is the text the model reads security
- Tool “update_dashboard_item” rewrote its description, which is the text the model reads security
- Tool “get_portal_page” rewrote its description, which is the text the model reads security
- Tool “create_report” rewrote its description, which is the text the model reads security
- Tool “get_record” rewrote its description, which is the text the model reads security
- Tool “import_records” rewrote its description, which is the text the model reads security
- Tool “list_site_blocks” rewrote its description, which is the text the model reads security
- Tool “export_records” rewrote its description, which is the text the model reads security
- Tool “run_action” rewrote its description, which is the text the model reads security
- Tool “delete_team_group” rewrote its description, which is the text the model reads security
- Tool “create_telegram_template” rewrote its description, which is the text the model reads security
- Tool “configure_chat” rewrote its description, which is the text the model reads security
- Tool “generate_ai_site” rewrote its description, which is the text the model reads security
- Tool “delete_template” rewrote its description, which is the text the model reads security
- Tool “create_whatsapp_template” rewrote its description, which is the text the model reads security
- Tool “delete_few_records” rewrote its description, which is the text the model reads security
- Tool “delete_form” rewrote its description, which is the text the model reads security
- Tool “list_portal_pages” rewrote its description, which is the text the model reads security
- Tool “seed_records” rewrote its description, which is the text the model reads security
- Tool “check_ai_site_status” rewrote its description, which is the text the model reads security
- Tool “get_rel_id” rewrote its description, which is the text the model reads security
- Tool “create_map” rewrote its description, which is the text the model reads security
- Tool “reorder_fields” rewrote its description, which is the text the model reads security
- Tool “create_project” rewrote its description, which is the text the model reads security
- Tool “generate_ai_project” rewrote its description, which is the text the model reads security
- Tool “update_field” rewrote its description, which is the text the model reads security
- Tool “create_portal_group” rewrote its description, which is the text the model reads security
- Tool “list_portal_users” rewrote its description, which is the text the model reads security
- Tool “create_record_template” rewrote its description, which is the text the model reads security
- Tool “delete_saved_view” rewrote its description, which is the text the model reads security
- Tool “update_cell” rewrote its description, which is the text the model reads security
- Tool “delete_project” rewrote its description, which is the text the model reads security
- Tool “get_metric” rewrote its description, which is the text the model reads security
- Tool “create_saved_view” rewrote its description, which is the text the model reads security
- Tool “bulk_update_records” rewrote its description, which is the text the model reads security
- Tool “update_portal_page” rewrote its description, which is the text the model reads security
- Tool “set_column_size” rewrote its description, which is the text the model reads security
- Tool “edit_site_block” rewrote its description, which is the text the model reads security
- Tool “duplicate_record” rewrote its description, which is the text the model reads security
- Tool “upload_file_to_record” rewrote its description, which is the text the model reads security
- Tool “get_field_types” rewrote its description, which is the text the model reads security
- Tool “get_relationship” rewrote its description, which is the text the model reads security
- Tool “list_projects” rewrote its description, which is the text the model reads security
- Tool “list_portals” rewrote its description, which is the text the model reads security
- Tool “list_schedules” rewrote its description, which is the text the model reads security
- Tool “list_forms” rewrote its description, which is the text the model reads security
- Tool “update_form_settings” rewrote its description, which is the text the model reads security
- Tool “create_portal” rewrote its description, which is the text the model reads security
- Tool “remove_user_from_portal_group” rewrote its description, which is the text the model reads security
- Tool “get_form_settings” rewrote its description, which is the text the model reads security
- Tool “search_records” rewrote its description, which is the text the model reads security
- Tool “delete_records_by_filter” rewrote its description, which is the text the model reads security
- Tool “update_relationship” rewrote its description, which is the text the model reads security
- Tool “list_dashboard_items” rewrote its description, which is the text the model reads security
- Tool “list_action_rules” rewrote its description, which is the text the model reads security
- Tool “get_report_data” rewrote its description, which is the text the model reads security
- Tool “duplicate_form” rewrote its description, which is the text the model reads security
- Tool “delete_portal_user” rewrote its description, which is the text the model reads security
- Tool “web_search” rewrote its description, which is the text the model reads security
- Tool “update_team_group” rewrote its description, which is the text the model reads security
- Tool “get_usage_stats” rewrote its description, which is the text the model reads security
- Tool “update_record_template” rewrote its description, which is the text the model reads security
- Tool “set_user_role” rewrote its description, which is the text the model reads security
- Tool “update_action_rule” rewrote its description, which is the text the model reads security
- Tool “delete_portal_group” rewrote its description, which is the text the model reads security
- Tool “search_image” rewrote its description, which is the text the model reads security
- Tool “delete_schedule” rewrote its description, which is the text the model reads security
- Tool “delete_reminder” rewrote its description, which is the text the model reads security
- Tool “add_record_comment” rewrote its description, which is the text the model reads security
- Tool “create_email_template” rewrote its description, which is the text the model reads security
- Tool “place_media_on_site” rewrote its description, which is the text the model reads security
- Tool “delete_portal_menu_item” rewrote its description, which is the text the model reads security
- Tool “update_form” rewrote its description, which is the text the model reads security
- Tool “get_records” rewrote its description, which is the text the model reads security
- Tool “list_user_roles” rewrote its description, which is the text the model reads security
- Tool “get_user_info” rewrote its description, which is the text the model reads security
- Tool “delete_record” rewrote its description, which is the text the model reads security
- Tool “remove_user_from_team_group” rewrote its description, which is the text the model reads security
- Tool “attach_media_to_record” rewrote its description, which is the text the model reads security
- Tool “list_webhooks” rewrote its description, which is the text the model reads security
- Tool “fetch_url” rewrote its description, which is the text the model reads security
- Tool “get_project” rewrote its description, which is the text the model reads security
- Tool “create_sms_template” rewrote its description, which is the text the model reads security
- Schema quality: excellent → good functional
- “add_dashboard_item” reworded the description of “first_widget_id” cosmetic
- “delete_records_by_filter” reworded the description of “entity_id” cosmetic
- “create_action_rule” reworded the description of “on_create” cosmetic
- “create_field” reworded the description of “allow_new_values” cosmetic
- “edit_site_block” reworded the description of “html” cosmetic
- “create_field” reworded the description of “entries_num” cosmetic
- “upload_file_to_record” reworded the description of “record_id” cosmetic
- “add_dashboard_item” reworded the description of “second_widget_id” cosmetic
- “configure_chat” reworded the description of “portal_id” cosmetic
- “create_field” reworded the description of “name” cosmetic
- “get_records” reworded the description of “search” cosmetic
- “bulk_update_records” reworded the description of “record_ids” cosmetic
- “update_portal_page” reworded the description of “must_contain” cosmetic
- “set_table_permission” reworded the description of “entity_id” cosmetic
- “create_report” reworded the description of “total_by_group” cosmetic
- “list_dashboard_items” reworded the description of “portal_id” cosmetic
- “update_action_rule” reworded the description of “action_id” cosmetic
- “web_search” reworded the description of “query” cosmetic
- “export_records” reworded the description of “email” cosmetic
- “update_dashboard_item” reworded the description of “item_id” cosmetic
- “set_user_role” reworded the description of “email” cosmetic
- “create_field” reworded the description of “app_id” cosmetic
- “update_cell” reworded the description of “value” cosmetic
- “update_field” reworded the description of “script_body” cosmetic
- “update_field” reworded the description of “separator” cosmetic
- “create_saved_view” reworded the description of “sort_by” cosmetic
- “create_record_template” reworded the description of “name” cosmetic
- “set_user_role” reworded the description of “entity_id” cosmetic
- “create_report” reworded the description of “group_field_ids” cosmetic
- “import_records” reworded the description of “csv_text” cosmetic
- “get_report_data” reworded the description of “report_id” cosmetic
- “bulk_update_records” reworded the description of “filter” cosmetic
- “get_metric” reworded the description of “date_field” cosmetic
- “add_user_to_team_group” reworded the description of “move_from_other_groups” cosmetic
- “update_relationship” reworded the description of “show_column_id” cosmetic
- “create_field” reworded the description of “delimiter” cosmetic
- “update_action_rule” reworded the description of “app_id” cosmetic
- “update_form_settings” reworded the description of “dtype_added_text” cosmetic
- “create_field” reworded the description of “ampm” cosmetic
- “bulk_update_records” reworded the description of “report_id” cosmetic
- “create_field” reworded the description of “choices” cosmetic
- “update_field” reworded the description of “formula_type” cosmetic
- “update_portal_page” reworded the description of “embed_form” cosmetic
- “list_portal_users” reworded the description of “per_page” cosmetic
- “upload_file_to_record” reworded the description of “file_content” cosmetic
- “create_field” reworded the description of “func_fields” cosmetic
- “get_relationship” reworded the description of “field_id” cosmetic
- “set_table_permission” reworded the description of “view_record_history” cosmetic
- “update_action_rule” reworded the description of “entity_id” cosmetic
- “add_dashboard_item” reworded the description of “block_width” cosmetic
- “update_record” reworded the description of “subforms” cosmetic
- “create_field” reworded the description of “uniqueness” cosmetic
- “delete_field” reworded the description of “entity_id” cosmetic
- “create_field” reworded the description of “vertical_align” cosmetic
- “create_field” reworded the description of “icon” cosmetic
- “list_portal_users” reworded the description of “portal_id” cosmetic
- “add_user_to_team_group” reworded the description of “user_group_id” cosmetic
- “delete_field” reworded the description of “field_name” cosmetic
- “set_table_permission” reworded the description of “show_related_records” cosmetic
- “update_field” reworded the description of “precision” cosmetic
- “create_form” reworded the description of “name” cosmetic
- “create_portal_group” reworded the description of “tables_permissions” cosmetic
- “create_field” reworded the description of “entity_id” cosmetic
- “update_field” reworded the description of “position” cosmetic
- “add_user_to_portal_group” reworded the description of “move_from_other_groups” cosmetic
- “update_portal_page” reworded the description of “name” cosmetic
- “update_field” reworded the description of “cols” cosmetic
- “create_field” reworded the description of “matrix_rows” cosmetic
- “create_email_template” reworded the description of “from” cosmetic
- “import_records” reworded the description of “records” cosmetic
- “upload_file_to_record” reworded the description of “file_name” cosmetic
- “set_column_size” reworded the description of “size” cosmetic
- “create_report” reworded the description of “order” cosmetic
- “list_webhooks” reworded the description of “entity_id” cosmetic
- “update_form” reworded the description of “per_page” cosmetic
- “create_action_rule” reworded the description of “email_column” cosmetic
- “export_records” reworded the description of “report_id” cosmetic
- “update_action_rule” reworded the description of “new_name” cosmetic
- “update_action_rule” reworded the description of “update_fields” cosmetic
- “create_field” reworded the description of “linked_records_count_form_id” cosmetic
- “update_field” reworded the description of “currency_unit” cosmetic
- “create_record” reworded the description of “rels” cosmetic
- “create_field” reworded the description of “text_align” cosmetic
- “create_action_rule” reworded the description of “subject” cosmetic
- “set_table_permission” reworded the description of “revoke” cosmetic
- “update_field” reworded the description of “func” cosmetic
- “seed_records” reworded the description of “subforms” cosmetic
- “create_action_rule” reworded the description of “email_body” cosmetic
- “invite_portal_user” reworded the description of “login” cosmetic
- “create_report” reworded the description of “average_by_group_column_id” cosmetic
- “delete_few_records” reworded the description of “record_ids” cosmetic
- “create_field” reworded the description of “operation” cosmetic
- “add_portal_menu_item” reworded the description of “name” cosmetic
- “place_media_on_site” reworded the description of “page_checksum” cosmetic
- “update_field” reworded the description of “formula_link_column” cosmetic
- “create_report” reworded the description of “total_by_group_column_id” cosmetic
- “add_portal_menu_item” reworded the description of “position” cosmetic
- “delete_records_by_filter” reworded the description of “filter” cosmetic
- “update_portal_page” reworded the description of “page_checksum” cosmetic
- “create_team_group” reworded the description of “tables_permissions” cosmetic
- “create_field” reworded the description of “field” cosmetic
- “create_report” reworded the description of “only_groupname_and_count” cosmetic
- “delete_records_by_filter” reworded the description of “record_ids” cosmetic
- “create_field” reworded the description of “operand_is” cosmetic
- “update_portal_menu_item” reworded the description of “section_id” cosmetic
- “add_record_comment” reworded the description of “body” cosmetic
- “update_field” reworded the description of “field” cosmetic
- “create_field” reworded the description of “formula_link_to” cosmetic
- “update_field” reworded the description of “step” cosmetic
- “update_field” reworded the description of “func_fields” cosmetic
- 2 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://quintadb.com.ua/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.quintadb.com.ua | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 10 May 2026 | 24 Nov 2026 | RSA 2048 | SHA256-RSA | b2830a7a4c13d5dc8cb1751d27ee232e |
| SANs: *.quintadb.com.ua, quintadb.com.ua | ||||||
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of quintadb.com.ua. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ua. | present | 51024, 51024 | 13, 13 | Verified |
| com.ua. | present | 43285 | 13 | Verified |
| quintadb.com.ua. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | ALLOWALL |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://quintadb.com.ua/mcp | Verified | 200 | |
| http (plaintext) | http://quintadb.com.ua/mcp | HTTPS enforced | 301 | https://quintadb.com.ua/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_forms ~42
List all forms (tables) in a project. List all forms, tables, entities in a project.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID from list_projects |
No output schema declared.
No examples provided.
list_maps ~40
The project's maps, each with its sources of markers and their ids (for update_map)
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
No output schema declared.
No examples provided.
list_portal_groups ~102
List a portal's user groups: members, and for each table or report the group has rights on — its role and whether the group sees only its own records (`tables`). Read it before changing who sees what: the group you need usually exists already. (get portal groups, show client groups)
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
No output schema declared.
No examples provided.
list_portal_menu_items ~115
The portal's menu: its top-level items, each with the items inside it (`submenu_items`) — a top-level item may open a table AND hold items. `position` is the place in the list, 0 = first. Call it before a rename, a move, a delete or a module change, to get section_id or item_id.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
No output schema declared.
No examples provided.
list_portal_pages ~63
List of the portal's HTML pages (landing pages, AI pages). Shows which one is the default.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
No output schema declared.
No examples provided.
list_portal_users ~80
List of the portal's users (clients registered in the portal)
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| page | number | – | Page number for pagination (starts at 1) |
| per_page | number | – | Max 200 |
| portal_id | string | yes | Portal ID from describe_project or list_projects |
No output schema declared.
No examples provided.
list_portals ~36
List of the project's portals with their URLs and number of pages.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
No output schema declared.
No examples provided.
list_projects ~34
List all projects (databases) in the QuintaDB account
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page (20 projects per page) |
No output schema declared.
No examples provided.
list_record_comments ~80
The comments on one record, oldest first: each with its id, its text, who wrote it and `yours` — whether the person you are talking to wrote it (only then can it be changed or removed).
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| record_id | string | yes | Record ID (dtype) |
No output schema declared.
No examples provided.
list_record_templates ~117
The record templates of a project or one table — the layouts ONE record is shown or printed with: each with its name, whether it is a record's page or a tile, and where it is in use now. Call it before update_record_template / delete_record_template to find the template_id, and to answer «which layouts does this table have?».
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | – | Optional: one table. Without it, every table that has a template. |
No output schema declared.
No examples provided.
list_reminders ~96
The reminders of a project or of one table: for each, the date field, who gets it, when (once or repeating) and which records it reads. It also answers where the project's date fields are: a reminder is made on the table that HOLDS its date.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | – | Form ID (from list_forms or describe_project) |
No output schema declared.
No examples provided.
list_saved_views ~57
List of a table's saved filters/views (SearchResult). Lets the agent learn which views already exist.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | – | Optional — filter by form |
No output schema declared.
No examples provided.
list_schedules ~53
List of the schedules that send data automatically (email/ftp).
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | – | Form ID (from list_forms or describe_project) |
No output schema declared.
No examples provided.
list_site_blocks ~136
Show the blocks (sections) of a site page with their captions — the FIRST step of a targeted site edit. The user picks a block from the LIST (there are 6-8). If editable=false, the page CANNOT be edited this way — tell the user so honestly and offer a regeneration; do NOT pretend the change happened. Returns page_checksum — pass it to edit_site_block.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| page_id | string | – | Optional — the site's home page is taken |
| portal_id | string | – | Optional — the portal with the site is taken |
No output schema declared.
No examples provided.
list_team_groups ~44
List back-office team groups (roles, members, permissions). (get team groups, show staff groups)
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
No output schema declared.
No examples provided.
list_templates ~107
The templates of a project: record, email, sms, telegram (no kind = all, names only). With kind and template_id: that one template in full, with its text.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | – | Optional — filter by form |
| kind | string | – | record | email | sms | telegram (default: all) |
| template_id | string | – | With kind: return this one in full |
No output schema declared.
No examples provided.
list_user_roles ~39
List of the users' individual roles in the project (apart from group rights).
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
No output schema declared.
No examples provided.
list_webhooks ~49
List of the webhooks of the project or of one form.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | – | Optional — filter by form |
No output schema declared.
No examples provided.
place_media_on_site ~214
Put an uploaded file (an image) in a particular place of the site — replaces src in the <img> tag found. A safe operation: checksum, lock, an Undo-compatible checkpoint. Use it instead of update_portal_page when only one image must be replaced.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| css_selector | string | – | CSS selector to find the img element (an alternative to current_src) |
| current_src | string | – | The current src of the image to replace (URL or relative path) |
| media_id | string | yes | File ID from MyFile (from diamant_upload or the media library) |
| page_checksum | string | yes | SHA256 of the page's current HTML — taken from the checksum field of get_portal_page's answer. Required, to guard against parallel changes. |
| page_id | string | yes | Portal page ID (from list_portal_pages) |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
No output schema declared.
No examples provided.
remove_example_records ~140
Remove the sample records that project generation added — what the person calls «the examples», «les exemples», «приклади», «примеры», sample, demo or test data. Deletes ONLY the records the generator registered as examples; records the person entered are never touched. Without entity_id it clears every table of the project; with entity_id only that table. When the person asks to delete, clear or remove the examples, call it — do not ask which table first.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | – | Only this table's examples. Omit for the whole project. |
No output schema declared.
No examples provided.
remove_user_from_portal_group ~101
Remove a user from a portal group. Pass user_id or email.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| string | – | User email address | |
| portal_group_id | string | yes | Portal group ID (from list_portal_groups or create_portal_group) |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
| user_id | string | – | User ID |
No output schema declared.
No examples provided.
remove_user_from_team_group ~81
Remove a user from a team group. Pass user_id or email.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| string | – | Or the user's email | |
| user_group_id | string | yes | Team group ID (from list_team_groups or create_team_group) |
| user_id | string | – | User ID |
No output schema declared.
No examples provided.
reorder_fields ~87
Change the order of the fields in a form. Pass an array of field_id or field_name in the wanted order.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| order | array | yes | Array of field_id or field_name in the new order (starting from position 0) |
No output schema declared.
No examples provided.
run_action ~78
Run an automation (action rule) for a record — send an email, trigger a webhook and so on. action_id is the ID of the action button field
| Name | Type | Req | Description |
|---|---|---|---|
| action_id | string | yes | ID of the field of type 'action' (the automation button) |
| record_id | string | yes | ID of the record the action runs for |
No output schema declared.
No examples provided.
search_image ~102
Find a free stock photo by a keyword (Unsplash). Returns the image's URL and the author's metadata. Use it before update_cell to fill a url field with the 'display_as_image' option. Never call it automatically for all records — only on an explicit request, or with the user's confirmation for bulk.
| Name | Type | Req | Description |
|---|---|---|---|
| orientation | string | – | Photo orientation (default landscape) |
| query | string | yes | Search query in English, e.g. 'red leather chair' |
No output schema declared.
No examples provided.
search_records ~90
Search/filter records (filter records, find entries, query data). Operators: is, is_not, contains, not_contains, starts_with, ends_with, is_empty, is_not_empty, gt, lt
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| conditions | array | yes | Search conditions |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
No output schema declared.
No examples provided.
seed_records ~125
Seed a form with initial records in bulk. Use it to fill a form with test or reference data. For one record create_record is better. Supports subforms through subforms.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| records | array | yes | Array of records. Each record is a hash {field_name: value} |
| subforms | array | – | Subform links [{property_id, dtype_id, subform_dtype_id}]. Rarely needed by hand. |
No output schema declared.
No examples provided.
send_portal_user_password_letter ~131
Mail a person in a portal the portal's own letter with a link where they set a new password themselves (the link works for one day; their present password keeps working until then). For «reset X's password», «X forgot the password», «X cannot sign in». Never ask the owner for a password and never write one in the chat.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
| user_id | string | yes | The person's id from list_portal_users |
No output schema declared.
No examples provided.
set_column_size ~160
Change the width of a column in the table or inside a subform/linked_records. Use it when the user asks to make a column wider/narrower, to enlarge/shrink a column in the table view.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID |
| entity_id | string | yes | ID of the form whose table changes |
| field_id | string | yes | ID of the column field whose width changes |
| size | integer | yes | New width in pixels (for example 200) |
| subform_field_id | string | – | If the column changed is INSIDE a subform or linked_records, pass the ID of the subform field (linked_records/subform) here. Without this parameter the column of the main table changes. |
No output schema declared.
No examples provided.
set_field_visibility_rule ~431
A field rule: show or hide fields of a form depending on the value of another field of the SAME form. Example: when «Status» is «in progress», show «What is missing» and «Call back on». It works in the FORM a record is added or edited in — inside the product and the public form — and nowhere else: it never hides, shows or swaps a COLUMN of a table, a report or a dashboard. When the condition's field is a link to another table («when Client is Anna Rossi»), the rule is about ONE RECORD of that table: find the record first and pass its id as when_record_id — a text is refused there.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| condition | string | – | How the value is compared; «is» when left out. One of: is, is_not, contains, not_contains, starts_with, ends_with, is_empty, is_not_empty, greater_than, less_than, greater_than_or_equal_to, less_than… |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| hide_field_ids | array | – | Ids of the fields to HIDE. Never together with show_field_ids. |
| show_field_ids | array | – | Ids of the fields to SHOW |
| when_field_id | string | yes | The id of the field the rule looks at: a status, a list, a checkbox, a number, a date — or a link to another table (then say the record with when_record_id) |
| when_record_id | string | – | Only when when_field_id is a link to another table: the id of the ONE record of THAT table at which the rule fires («when Client is Anna Rossi» = Anna Rossi's record id in Clients, from search_record… |
| when_value | string | – | The value at which the rule fires — for a list, exactly as the option is written. Not for a link to another table. |
No output schema declared.
No examples provided.
set_module_permission ~186
Give a group access to a module (forms, charts, maps, …). A PORTAL group gets one chart, map or calendar per call, by its id; its tables, forms and reports are set_table_permission.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| can_delete | boolean | – | – |
| can_edit | boolean | – | – |
| module | string | yes | forms, charts, maps, calendars, files, team, portals, reports, table; for a portal group only charts, maps, calendars |
| module_id | string | – | ID of the one module (entity/widget/chart/map…); required for a portal group |
| portal_group_id | string | – | Portal group ID (from list_portal_groups or create_portal_group) |
| user_group_id | string | – | ID of a team group (or portal_group_id) |
No output schema declared.
No examples provided.
set_table_permission ~936
What a group (team or portal) may do on a table or report, and whether its people see ONLY THEIR OWN records there. For a group that already has rights on the table pass ONLY what the person asked to change: «technicians see only their own orders» is only_own_records: true with NO role — a role you pass replaces the group's present one. The answer says CHANGED / UNCHANGED for the role and for only_own_records, and what «own» means: repeat that meaning, never «assigned to them». Sets the rights of a group (team or portal) on a form or report. role: 1=administrator: everything, as the owner; 2=read only; 3=read, write and DELETE records; 4=read, write and DELETE records, and build forms; 5=read and write records, NO delete; 6=read, edit and DELETE records; 7=read and edit records, NO delete. When the person asked that these people cannot delete, pass only a role that says NO delete (or read only), never one that says DELETE; and tell the person what the role lets them do in these words. «Make them an admin / let them see everything, as I do» is role 1 («Admin» on the screen). Pass either user_group_id (team) or portal_group_id (portal).
| Name | Type | Req | Description |
|---|---|---|---|
| add_related_records | boolean | – | The «add a linked record» button in the card (works together with show_related_records). |
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | yes | Form or report ID |
| hidden_columns | array | – | Fields (names or IDs) this group does NOT see in the TABLE (the list of records). Independent of hidden_fields: a field can stay in the form but be removed from the table. The same list-replacing sem… |
| hidden_fields | array | – | Fields (names or IDs) this group does NOT see in the record FORM. This is how a form is narrowed: e.g. a rank-and-file employee fills in seven fields of a lead instead of all thirty-three. Pass the f… |
| only_own_records | boolean | – | true: people of this group see only the records they added or were made owner of. false: they see everyone's. For a group of people from OUTSIDE the owner's business — clients, tenants, students, pat… |
| portal_group_id | string | – | Portal group ID |
| revoke | boolean | – | true — TAKE AWAY this group's right on this form/report (the rule is removed). Roles 1..7 have no «no access» value, so this is the only way to revoke. role is not needed with revoke. If there was no… |
| role | integer | – | 1=administrator: everything, as the owner; 2=read only; 3=read, write and DELETE records; 4=read, write and DELETE records, and build forms; 5=read and write records, NO delete; 6=read, edit and DELE… |
| show_related_records | boolean | – | Show in the record's card the block of linked records from other tables (e.g. an employee's salary rows in the employee's card). Without it the group sees only the card itself, even with a right on t… |
| user_group_id | string | – | Team group ID (from create_team_group) |
| view_record_history | boolean | – | Let this group see the record's «History» tab (who changed what, when, what it was → what it became). Off by default: the history shows fields' old values. |
No output schema declared.
No examples provided.
set_user_role ~204
Give a user an individual role on the project or a form (separately from groups). THE ROLES AND WHAT THEY MEAN (as a person sees them in the interface): owner = «Admin» — full access, like the owner's, rights and structure included; member = «Read only»; writer = «Read and write»; writer_not_delete = «Read and write without delete»; read_edit_delete = «Read, edit, delete»; read_and_edit = «Read and edit»; creator = «Read, write, create forms». When the person says «make her an admin», that is owner.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| string | yes | User's email | |
| entity_id | string | – | Optional — limit the role to a particular form |
| role | string | yes | owner | member | writer | creator | writer_not_delete | read_edit_delete | read_and_edit |
No output schema declared.
No examples provided.
split_column_into_table ~354
Move what a column repeats into a table of its own: ONE record of a new table per different value of the column (a supplier, a client, a category named on many rows), made from the values the table already holds — never invented — and a link field added to the table, filled for every row. Use it for «split X into their own table», «make suppliers a separate table», «normalise». The old columns stay as they are; the answer says what to tell the person about them. Do NOT use create_form for this: it makes an empty table. It is also the FIRST step of a list that depends on another field when that field is a plain dropdown (Stage → Check point): split the dropdown — its options become the parents' table — then link the children's column to it with into_table.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| column | string | yes | The field (name or id) whose values name the things — «Supplier» |
| entity_id | string | yes | The table that holds the column now |
| into_table | string | – | A table the project ALREADY has (name or id) whose rows the column names: no table is made, the column is linked to that table's rows with the same values — e.g. the stage dropdown of «Check points»… |
| table_name | string | – | The new table's name, in the person's language — «Suppliers» |
| with_columns | array | – | Other fields of the same table that describe the same thing and go with it — «Supplier email», «Supplier phone» |
No output schema declared.
No examples provided.
update_action_rule ~633
Change an existing automation rule of a form: the trigger (on_create/on_update), the actions (send_email/update_record/…), the email, and above all the CONDITIONS and the UPDATE FIELDS (update_fields). A conditions/update_fields list that is passed REPLACES the existing one whole; one not passed is not touched. The answer holds the rule's resulting structure — show the person that, from the answer, not from your own request.
| Name | Type | Req | Description |
|---|---|---|---|
| action_id | string | – | Rule ID from list_action_rules — as a string, as returned (takes priority over name) |
| app_id | string | yes | Project ID |
| conditions | array | – | The FULL new list of conditions under which it fires (replaces the old one) |
| do_not_send_data_if_criteria_matches | boolean | – | true = when the conditions match, the record is NOT saved and the person reads `message` instead; false = the record is saved as usual |
| email_body | string | – | – |
| email_column | string | – | Name or ID of the field with the recipient's email |
| email_recipient_source | integer | – | 0 = the given addresses, 1 = from a field of the form, 2 = the record's owners |
| emails | string | – | Addresses the mail always goes to, comma-separated. "me" = the person you are talking to (their own account's address): «email me», «notify me», «let me know» — never ask them for it. The answer's em… |
| entity_id | string | yes | ID of the form the rule lives in |
| message | string | – | The text the person reads: after the save (show_message) or instead of it (do_not_send_data_if_criteria_matches) |
| name | string | – | Rule name to search by (if action_id is not passed) |
| new_name | string | – | New rule name |
| numbers | string | – | Written phone numbers, comma-separated — when it is not a number from the record |
| on_create | boolean | – | – |
| on_update | boolean | – | – |
| redirect | boolean | – | – |
| run_webhook | boolean | – | false stops the automation calling its webhook (the webhook is kept); true only for an automation that has one — make it with create_webhook |
| send_email | boolean | – | – |
| send_sms | boolean | – | – |
| settings | object | – | Deprecated: the same simple attributes as a hash. An unknown key is an error. |
| show_message | boolean | – | Show `message` AFTER the record is saved. It refuses nothing. |
| sms_body | string | – | – |
| sms_column | string | – | The field of this form that holds the phone the text goes to (name or id) |
| subject | string | – | – |
| update_fields | array | – | The FULL new list of fields the rule sets in the record (replaces the old one; switches update_record on) |
| update_record | boolean | – | – |
| url | string | – | – |
No output schema declared.
No examples provided.
update_calendar ~163
Change a calendar: its name, or whether it shows Saturdays and Sundays (weekends). Pass only what changes. `add_data_sources` adds sources of events and `remove_data_source_ids` removes sources by the ids list_calendars shows (798); every other source stays as it is. Ids come from list_calendars.
| Name | Type | Req | Description |
|---|---|---|---|
| add_data_sources | array | – | Sources of events to ADD to the ones the calendar has, each with date_field_id. |
| app_id | string | yes | Project ID (from list_projects) |
| calendar_id | string | yes | – |
| new_name | string | – | – |
| remove_data_source_ids | array | – | Ids of the sources to remove, from list_calendars |
| weekends | boolean | – | – |
No output schema declared.
No examples provided.
update_cell ~127
Update the value of one field in a record without overwriting the other fields. ALWAYS use the field's ID, not its name.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| field_name | string | yes | Field ID (for example 'dcTrJdP1bppyk3vCkKvCoN'). NOT THE FIELD NAME! |
| record_id | string | yes | Record ID (from get_records or search_records) |
| value | string | yes | New value |
No output schema declared.
No examples provided.
update_chart ~240
Change a chart: its name, its type (pie, doughnut, line, area, bar, column, scatter) or the title of its vertical axis. Pass only what changes. `add_data_sources` adds series and `remove_data_source_ids` removes series by the ids list_charts shows (798); every other series stays as it is. To change one series: remove it and add the new one in the same call. It does NOT change the horizontal axis (what the values are grouped by): for that create the chart you want with create_chart, then remove this one with delete_chart. Ids come from list_charts.
| Name | Type | Req | Description |
|---|---|---|---|
| add_data_sources | array | – | Series to ADD to the ones the chart has |
| app_id | string | yes | Project ID (from list_projects) |
| chart_id | string | yes | – |
| new_name | string | – | – |
| remove_data_source_ids | array | – | Ids of the series to remove, from list_charts |
| type_code | string | – | pie, doughnut, line, area, bar, column, scatter |
| y_axis_title | string | – | – |
No output schema declared.
No examples provided.
update_dashboard_item ~154
Change the NAME (the card's caption), the icon or the position of a dashboard widget. ⚠️ Dashboard captions are separate from table names: renaming forms does NOT touch them, so when the project's interface is translated the dashboard must be updated with this tool separately, or it stays in the previous language.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| icon | string | – | The icon's FontAwesome class (optional) |
| item_id | string | yes | Widget ID from list_dashboard_items |
| name | string | – | New card caption |
| portal_id | string | – | If not given — the project's first portal |
| position | integer | – | Position in the grid (optional) |
No output schema declared.
No examples provided.
update_field ~2,211
Change/rename a form field (rename field, edit property, update column). Name, description, position, options for select/radio, default value, required, sizes, uniqueness. Does not change the field's type.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_new_values | boolean | – | For select fields only. true — users can add new options right from the record form («+ Add new value...» in the list). Default false. |
| app_id | string | yes | Project ID (from list_projects) |
| average_table_column | string | – | Not for an average over the rows linked to this record: their sum (linked_records + linked_column) divided by a linked_records_count. formula_type average is refused by this tool. |
| average_table_ref_column | string | – | formula_type average: the link field in that other table that points at this form, by id or name; may be left out when only one table links here |
| choices | array | – | New options for select / radio / checkbox (replaces all current ones) |
| cols | integer | – | Number of columns for textarea |
| column | string | – | Only for a linked_column field: the id of the field of the linked table it shows (get_form_fields of that table lists the ids). Changes WHAT the column shows; written here, beside settings — not insi… |
| currency_unit | string | – | Currency symbol |
| default | string | – | Default value. ⚠️ For select/radio/checkbox this key carries THE LIST of options itself — to set the option selected at the START, use `initial`. |
| delimiter | string | – | Thousands separator |
| dependent | boolean | – | rel only: true — the list offers only the rows linked to what another field of the same form holds (Country → City, Stage → Check point), with depends_from_field_id; false — the list is whole again |
| depends_from_field_id | string | – | rel only: the field of the same form (name or id) whose pick narrows this list — itself a link to a table that the linked table links to as well |
| desc | string | – | Description / hint under the field |
| disable_future | boolean | – | Forbid future dates |
| disable_past | boolean | – | Forbid past dates |
| display_as_image | boolean | – | true — show the URL as a picture in the table (url fields only) |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| field | array | – | Array of field IDs or constants ['Constant', 'text'] for formula_type=formula |
| field_id | string | – | Field ID — an alternative to field_name |
| field_name | string | – | Field name (resolved to the ID automatically) |
| file_preview | string | – | file fields only: inline — audio (mp3, wav, m4a, ogg), video (mp4, webm, mov) and PDF play or show right in the table and the record instead of a link; none — the link (the default). This is what «se… |
| formula_link_column | string | – | formula_type=link: ID of the field with the table/form name |
| formula_link_target | string | – | formula_type=link: _blank, _self, _parent, _top |
| formula_link_to | string | – | formula_type=link: on_table or table_form |
| formula_type | string | – | Formula type: formula (arithmetic/concatenation), function (built-in functions + Ruby), link (clickable link), total (sum), average (average). REQUIRED for field_type=formula. |
| func | integer | – | Function for formula_type=function: 0=MIN, 1=MAX, 2=ROUND_UP, 3=ROUND_DOWN, 4=Ruby script |
| func_fields | array | – | IDs of all fields used in func/script_body. REQUIRED for formula_type=function — without it the formula is not recalculated. |
| hide_from_public_form | boolean | – | true — remove the field from the PUBLIC form (the form widget: what is put on a website or sent to clients as a link), keeping it in the internal record form. This is how a short request form is made… |
| image_url | string | – | image fields only: what a click on the picture does — popup (a gallery over the table, the default), full_size (the picture in a new tab), record (opens the record), url (a link kept in another field… |
| image_url_column | string | – | with image_url=url: the id of the url field whose link the picture opens |
| initial | string | – | For select/radio: which option is selected in a new form (e.g. the status «Pending»). An empty string removes the starting choice. For ordinary fields the starting value is set by `default`. |
| is_currency | boolean | – | Show as currency |
| name | string | – | New field name |
| operand_is | string | – | Operand type for formula_type=formula: numbers, decimal, text, days, hours, year. REQUIRED when formula_type=formula. |
| operation | array | – | Operators between the fields: +, -, *, / (one fewer than the number of fields) |
| position | integer | – | Position in the form (ordinal number from 1) |
| precision | integer | – | Digits after the decimal point (for float) |
| rel_show_field_id | string | – | ONLY for rel fields (a link to another form). Changes WHICH field of the target record is shown in this rel field — e.g. "show the name instead of the date" / "show the name instead of id/date" for a… |
| required | boolean | – | true — the field is required, false — no longer required |
| rich | boolean | – | true — rich text editor (for textarea) |
| rows | integer | – | Number of rows for textarea |
| script_body | string | – | Ruby code for func=4. Rules: the result goes into the variable 'a', the last line is 'a'; field names in single quotes 'field_name'.to_f; def/while/puts/return/require are forbidden; aggregating subf… |
| separator | string | – | Decimal separator: '.' or ',' |
| settings | object | – | Any other setting of the field, as setting: value pairs in the product's own names — totals and averages under a column, barcode / QR code, an input mask, several files at once, a list's options side… |
| show_file_url_as_image | boolean | – | file and image fields only: true — an icon (file) or the thumbnail (image) in the table instead of the file name |
| size | integer | – | Field width in pixels |
| start_from | integer | – | Starting value of an autoincrement field |
| step | integer | – | Step of an autoincrement field |
| text_align | integer | – | Alignment in the cell: 1=left, 2=right, 3=center, 4=justify |
| time_settings | object | – | time field: how the time is picked. clock_system "12h" | "24h"; control_type "dropdown" | "slider"; units: { hour | minute | second | millisec | microsec: { show: true|false, min, max, step, grid } }… |
| total_table_column | string | – | Not for a sum over the rows linked to this record — that is a linked_records field and a linked_column over it (937). formula_type total is refused by this tool. |
| total_table_ref_column | string | – | Not for a sum over the rows linked to this record (see total_table_column). |
| truncates_after | integer | – | Cut the text after N characters in the table |
| uniq_columns | array | – | For uniq_validation=multi: an array of names or IDs of the other fields together with which uniqueness is checked. For example ["Last name", "Date of birth"] — the combination Field+Last name+Date mu… |
| uniq_error_message | string | – | A custom error message when uniqueness is broken |
| uniq_validation | string | – | Type of the uniqueness check: none — no check; simple — this field is unique on its own; multi — unique in combination with other fields (given in uniq_columns). Example: the Email field + uniq_valid… |
| validations | object | – | The field's checks (the recommended way, instead of validate_options). They check the text typed into the add or edit form, in the browser: none reads a date's weekday, a holiday, opening hours or ot… |
| vertical_align | integer | – | Vertical alignment: 1=top, 2=middle, 3=bottom |
| visible | boolean | – | Whether the field's column is shown on the table's PUBLIC page (the page, a found record, one record's own page). It does not hide the field from the form or from the owner's own table. For a public… |
No output schema declared.
No examples provided.
update_form ~79
Change a form's name, description or settings.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| desc | string | – | Form description |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| name | string | – | New form name |
| per_page | integer | – | Records per page |
No output schema declared.
No examples provided.
update_form_settings ~575
Form settings. A LIMIT ON HOW MANY RECORDS A FORM TAKES is turn_off_form_after — «close registration at 300 people» is this, and nothing else: never hide the add button or the page for it (that closes the form NOW). The answer says how many records the form holds and whether it is open. Update a form's settings: post_action (redirect URL after submit), per_page, sort_by, allow_delete, send_emails, inline_editing, allow_database, lqe_use_only_login and others.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_database | boolean | – | – |
| allow_delete | boolean | – | – |
| app_id | string | yes | Project ID (from list_projects) |
| asc | boolean | – | – |
| confirmation_checkbox | boolean | – | A consent checkbox at the bottom of the form that must be ticked before the form can be sent (the field picker's «Confirmation checkbox»): true adds it, false removes it. One per form; it is a settin… |
| confirmation_checkbox_text | string | – | The sentence beside the consent checkbox, e.g. «I agree to my data being stored». Required when the checkbox is added; given alone, it adds the checkbox |
| dtype_added_text | string | – | Text after a successful form submit |
| entity_id | string | yes | Form ID (from list_forms or describe_project) |
| inline_editing | boolean | – | – |
| lqe_use_only_login | boolean | – | – |
| per_page | integer | – | Number of records per page (max 100, default 20) |
| post_action | string | – | URL to redirect to after the form is submitted |
| redirect_to_new_page | boolean | – | Open target_page in a new tab instead of in the current one |
| send_emails | boolean | – | Send an email notification on a new record |
| sort_by | string | – | ID of the sort field |
| submit_button_msg_text | string | – | – |
| target_page | string | – | Where to send the person AFTER the PUBLIC form (the widget) is submitted. A full URL. Does not affect records created internally by staff. |
| turn_off_form | boolean | – | false removes the limit on the number of records (the form takes records again). true is only needed to switch back on a limit set before. |
| turn_off_form_after | integer | – | Close the form at this many records: «close registration at 300 people», «only 50 places», «stop taking orders after 100». The form stays OPEN until the table holds that many — it is not closed now.… |
| turn_off_form_msg_text | string | – | What people see instead of the form once it is closed by the limit below |
No output schema declared.
No examples provided.
update_formatting ~241
Change a formatting rule that exists: its name, the fields it styles, the style, the rows it applies to. settings are MERGED into the style it has (pass only what changes: «make it bold too» keeps its colour); conditions is the whole list of row conditions it keeps.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | true = every row; false = only the rows that match conditions |
| app_id | string | yes | Project ID (from list_projects) |
| conditions | array | – | The whole list: property_id (a field), condition (is, is_not, contains, is_empty, less_than, greater_than …), search, join (and / or) |
| criteria_name | string | – | The conditions in words |
| formatting_id | string | yes | From list_formattings |
| new_name | string | – | – |
| property_ids | array | – | Names or ids of the fields the style applies to (empty = every column) |
| settings | object | – | background_color (#hex), text_color (#hex), bold, italic, underline, strike (boolean), font_family, font_size (px), all_columns (boolean) |
No output schema declared.
No examples provided.
update_map ~235
Change a map: its name, where it is centred (center_type 1 = an address, 2 = coordinates, 3 = the first record) and its zoom. Pass only what changes. `add_data_sources` adds sources of markers and `remove_data_source_ids` removes sources by the ids list_maps shows (798); every other source stays as it is. Ids come from list_maps.
| Name | Type | Req | Description |
|---|---|---|---|
| add_data_sources | array | – | Sources of markers to ADD to the ones the map has. Each needs address_field_id, or latitude_field_id with longitude_field_id. |
| app_id | string | yes | Project ID (from list_projects) |
| center_address | string | – | – |
| center_latitude | number | – | – |
| center_longitude | number | – | – |
| center_type | integer | – | 1 = an address, 2 = coordinates, 3 = the first record |
| map_id | string | yes | – |
| new_name | string | – | – |
| remove_data_source_ids | array | – | Ids of the sources to remove, from list_maps |
| zoom | integer | – | – |
No output schema declared.
No examples provided.
update_portal_menu_item ~295
Update a portal menu item: rename it, change its module, icon, place or URL. Give section_id (a top-level item) or item_id (an item inside a section) from list_portal_menu_items. To MOVE an item, give `position`: the place it must stand at after the move among its own siblings, counted as list_portal_menu_items shows them (0 = first; a number past the end = last). The other items shift by themselves — one call moves one item; never renumber the others. «Put A before B» = position of B when A stands after B, position of B minus 1 when A stands before B.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| icon | string | – | – |
| item_id | string | – | ID of the submenu item (kind=submenu_item) |
| module_ai_id | string | – | New module: form_ID, report_ID and so on |
| module_id | string | – | – |
| module_type | integer | – | – |
| name | string | – | Display name |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
| position | integer | – | The place after the move among its siblings, 0 = first |
| section_id | string | – | ID of the top-level item (kind=section) |
| url | string | – | – |
No output schema declared.
No examples provided.
update_portal_page ~490
Update a portal page's HTML or name. Can also make it the default page. Before changing the HTML always get_portal_page and pass checksum + site_id from SURFACE CONTEXT. IMPORTANT: if the page holds forms or tables with data, better use generate_ai_site, not this tool directly. If you do insert an iframe by hand, the only right format is: src='https://quintadb.com/widgets/APP_ID/ENTITY_ID?iframe=true'. APP_ID and ENTITY_ID come from describe_project. Do NOT invent other URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| embed_form | object | – | The MAIN way to PUT A FORM ON THE SITE («add a request form to the page», «so that a visitor leaves their contacts»). The server itself inserts a ready block with the form into the html and does NOT… |
| html | string | – | New HTML content of the page |
| must_contain | array | – | A targeted edit (e.g. a site menu item): lines that MUST be in the saved HTML (the link's name, href). An independent verify check — if they are missing, the edit counts as failed. |
| name | string | – | New page name |
| nav_append | object | – | The MAIN way to add an item to the SITE MENU: the server itself inserts <a> into the page's <nav> and does NOT touch the rest of the html (quinta-* blocks are guaranteed whole). Do NOT pass html and… |
| page_checksum | string | – | SHA256 of the current HTML from get_portal_page.checksum. REQUIRED when updating html — a call without checksum is refused. |
| page_id | string | yes | Portal page ID (from list_portal_pages) |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
| set_as_default | boolean | – | Make this page the home page |
| site_id | string | – | site_id from SURFACE CONTEXT — dual-write into the right Site. |
No output schema declared.
No examples provided.
update_portal_settings ~671
Change a portal's settings: name, subdomain, locale, theme, colour, sign-in type (the login window), whether people can register themselves. The answer says where the menu is now (`menu`) and whether the change moved it (`menu_moved`), who gets into the portal now (`access`), whether your call changed that (`access_changed`) and whether people can create their own accounts (`self_registration`).
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| auth_type | integer | – | The portal's sign-in (the login window): 0=public: anyone with the link gets in, no sign-in; 1=one shared login and password for everyone; 2=sign-in required: each person signs in with their own logi… |
| color | integer | – | The colour: 0=White, 1=Black, 2=Grey, 3=Blue, 4=Green, 5=Orange, 6=Red. In themes 0, 1, 3, 4, 12, 13 0 is a light menu with dark letters, and 1–6 a menu of that colour with white letters. It keeps th… |
| locale | string | – | en, uk, ru, ... |
| name | string | – | Display name |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
| self_registration | boolean | – | true = a visitor can create their own account on the portal's login page; false = accounts only by invitation. Pass true ONLY when the person asked for exactly this — a request for «login» or «a logi… |
| subdomain | string | – | The subdomain without .quintadb.com |
| theme | integer | – | The theme, which also decides where the menu is: 0=Standard (menu: a bar across the top), 1=Professional (menu: a narrow strip of icons on the left that opens on hover), 3=Professional Opened (menu:… |
No output schema declared.
No examples provided.
update_portal_user ~194
Change a person's account in a portal: their email address, login, first name, last name or phone. Pass only what the person asked to change; nothing else is touched. The answer says CHANGED (was → now) / UNCHANGED per item. A password is NEVER set here and never asked for in the chat: send_portal_user_password_letter mails the person a link to set their own.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| string | – | The new email address | |
| first_name | string | – | – |
| last_name | string | – | – |
| login | string | – | The new login. Changing the email does not change the login. |
| phone | string | – | – |
| portal_id | string | yes | Portal ID (from list_portals or describe_project) |
| user_id | string | yes | The person's id from list_portal_users |
No output schema declared.
No examples provided.
update_project ~40
Rename a project or change its basic attributes.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | Project ID (from list_projects) |
| name | string | – | Display name |
No output schema declared.
No examples provided.
How do I install the QuintaDB MCP server?
QuintaDB is a hosted endpoint at https://quintadb.com.ua/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · quintadb.com.ua
claude mcp add --transport http ua-com-quintadb-mcp 'https://quintadb.com.ua/mcp'
What is the QuintaDB MCP server?
QuintaDB is an MCP server listed in the public MCP registry as ua.com.quintadb/mcp. No-code databases, forms, portals and AI sites. Manage records and automation via natural language. This page covers its hosted endpoint (https://quintadb.com.ua/mcp).
Is the QuintaDB MCP server safe to use?
QuintaDB scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the QuintaDB MCP server expose?
QuintaDB exposes 159 tools: list_projects, list_forms, get_form_fields, get_records, get_record, and 154 more. Their descriptions and schemas cost roughly 31,150 tokens of context every time the server is loaded.
Does the QuintaDB MCP server require authentication?
No. We connected to QuintaDB without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the QuintaDB MCP server still maintained?
QuintaDB is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.