Is com.ask-ai-data-connector/ask-ai 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.
| Endpoint | https://ask-ai-data-connector.com/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 card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://ask-ai-data-connector.com/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 directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://ask-ai-data-connector.com 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 66 tools: ask_moby, complete_intervention, get_abandoned_checkouts, get_analytics, get_anomalies, get_briefing, get_campaign_impact, get_cart_affinity, get_collections, get_complete_dashboard, get_connector_data, get_customer_insights, get_customers, get_daily_metrics, get_data_sources, get_discounts, get_focus, get_forecast, get_ga4_dimensions, get_ga4_funnel, get_help, get_insights, get_interventions, get_inventory, get_marketing_performance, get_markets, get_metrics_comparison, get_metrics_multi_compare, get_order, get_orders, get_product_analytics, get_product_catalog, get_product_health, get_products_by_channel, get_query_to_url, get_refunds, get_revenue_drivers, get_reviews, get_spend_reconciliation, get_store_notes, get_store_profile, get_store_summary, get_sync_health, get_targets, get_timeline, get_top_products, get_velocity, get_wakeup, get_wakeups, get_weekly_trends, get_yoy_monthly, query_metric_snapshots, query_orders, record_metric_snapshot, report_concern, report_data_issue, save_focus, save_insights, save_store_note, save_target, save_wakeup, set_intervention, update_focus_item, update_insight, update_intervention, update_store_profile.
Its tools changed between 2026-09 and 2026-10:
- Added (1):
update_intervention get_connector_data: description, input schema changedget_velocity: input schema changedquery_orders: input schema changedset_intervention: input schema changed
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 name | com.ask-ai-data-connector/ask-ai |
|---|---|
| Endpoint | https://ask-ai-data-connector.com/mcp |
| Publisher repository | not 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