Is com.datavrn/schedule-iii 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://app.datavrn.com/api/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://app.datavrn.com/api/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://app.datavrn.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 67 tools: assert_previous_year_no_activity, confirm_capture_review, confirm_centre_mappings, confirm_column_mapping, confirm_complete_chart, confirm_groupings, confirm_reporting_lines, copy_capture_declarations, create_client, create_cost_centre, create_profit_centre, create_upload_link, declare_capture_na, finalise_statement, generate_schedule_iii, get_allocation_account_figures, get_allocation_target_figures, get_budget, get_comparative_source_state, get_consolidated_statements, get_finalise_readiness, get_help, get_job, get_partner_capital, get_pending_work, get_schedule3_workspace, get_setup_status, get_spreading_reconciliation, get_statement_figures, get_statement_notes, get_tb_rows, get_upload, get_upload_link_status, get_variance_report, get_workbook_download, ingest_upload, list_account_mappings, list_allocation_runs, list_budgets, list_chart_rebaselines, list_clients, list_cost_centres, list_grouping_suggestions, list_periods, list_profit_centres, list_replacements, list_reporting_lines, list_snapshots, list_statement_policy_choices, preview_chart_rebaseline, preview_replacement_restore, restore_replacement, revoke_capture_declaration, save_accounting_policies, save_adjustments, save_asset_movements, save_disclosures, save_partner_capital, save_provision_movements, save_py_values, save_regulatory_affirmations, save_reserves_movements, save_share_capital, save_statement_settings, set_header_row, upload_trial_balance, verify_connection.

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 namecom.datavrn/schedule-iii
Endpointhttps://app.datavrn.com/api/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