Is ua.com.quintadb/mcp up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

Endpointhttps://quintadb.com.ua/mcp
Page built

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://quintadb.com.ua/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://quintadb.com.ua with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 146 tools: add_dashboard_item, add_portal_menu_item, add_record_comment, add_user_to_portal_group, add_user_to_team_group, attach_media_to_record, bulk_update_records, check_ai_site_status, configure_chat, create_action_rule, create_calendar, create_chart, create_email_template, create_field, create_folder, create_form, create_formatting, create_map, create_portal, create_portal_group, create_portal_page, create_project, create_record, create_record_template, create_reminder, create_report, create_saved_view, create_schedule, create_sms_template, create_team_group, create_telegram_template, create_webhook, create_whatsapp_template, delete_action_rule, delete_calendar, delete_chart, delete_dashboard_item, delete_few_records, delete_field, delete_form, delete_formatting, delete_map, delete_portal, delete_portal_group, delete_portal_menu_item, delete_portal_page, delete_portal_user, delete_project, delete_record, delete_records_by_filter, delete_reminder, delete_report, delete_saved_view, delete_schedule, delete_team_group, delete_template, delete_webhook, describe_project, duplicate_form, duplicate_record, edit_site_block, export_records, fetch_url, generate_ai_project, generate_ai_site, get_column_total, get_field_types, get_form_fields, get_form_settings, get_metric, get_portal_page, get_project, get_quickstart_guide, get_record, get_records, get_rel_id, get_relationship, get_report_data, get_reports, get_usage_stats, get_user_info, import_records, invite_portal_user, list_action_rules, list_calendars, list_charts, list_dashboard_items, list_folders, list_formattings, list_forms, list_maps, list_portal_groups, list_portal_menu_items, list_portal_pages, list_portal_users, list_portals, list_projects, list_record_comments, list_reminders, list_saved_views and 46 more.

Its tools changed between 2026-09 and 2026-10:

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry nameua.com.quintadb/mcp
Endpointhttps://quintadb.com.ua/mcp
Publisher repositorynot known: the registry did not return this listing within 4 seconds

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy