Is io.customerdashboard/customerdashboard up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | customerdashboard 0.1.0 |
| Answered in | 585 ms |
| Endpoint checked | https://app.customerdashboard.io/mcp |
| Checked |
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 200 with an HTML page, not JSON)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://app.customerdashboard.io/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 200 with an HTML page, not JSON)./.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 200 with an HTML page, not JSON)./.well-known/http-message-signatures-directory |
Read at https://app.customerdashboard.io 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 42 tools: add_customer, add_customer_user, add_data_source, create_dashboard, create_view, create_widget, delete_customer, delete_customer_user, delete_dashboard, delete_data_source, delete_view, delete_widget, explain_customer_filtering, get_account, get_dashboard, get_dashboard_share_url, get_data_source, get_data_source_schema, get_platform_overview, get_started, list_customers, list_dashboards, list_data_sources, list_plans_and_limits, list_supported_data_connectors, list_views, list_widget_types, list_widgets, publish_dashboard, reorder_views, run_query_preview, set_dashboard_formatting, set_dashboard_theme, set_widget_layout, test_data_source_connection, unpublish_dashboard, update_customer, update_dashboard, update_data_source, update_view, update_widget, validate_customer_filtering.
No change to its tools 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 name | io.customerdashboard/customerdashboard |
|---|---|
| Title | CustomerDashboard |
| Description | Build dashboards on your own data, including multi-customer views with per-customer login. |
| Endpoint | https://app.customerdashboard.io/mcp |
| Publisher repository | none listed |
| Version | 0.1.0 |
| Listing updated |
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