schedule-iii
warningsapp.datavrn.com
Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out.
https://app.datavrn.com/api/mcpWebsiteOAuthMCP 2025-11-25v0.1.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 799 msHow to authenticate
Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.
| Scheme | OAuth |
|---|---|
| Issuer | https://jmkgxtzscatvuqefbiyq.supabase.co/auth/v1 |
| Dynamic client registration | ✓Advertised (RFC 7591) |
| Client ID Metadata Document | ✕Not advertised |
| PKCE | ✓S256, plain |
| Grant types | authorization_code, refresh_token |
| Scopes | openid, profile, email, phone, offline_access |
| Protected-resource metadata | ✓Published (RFC 9728) |
| Anonymous access | Handshake succeeds; 67 tools listable |
| Credentials demanded in prose | ✕get_schedule3_workspace, confirm_groupings, generate_schedule_iii, get_spreading_reconciliation, get_setup_status These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error. |
| Documentation | https://datavrn.com/connect-assistant |
What the probe found
5 of the 67 tools listed anonymously say in their own descriptions that they need an account or a key (get_schedule3_workspace, confirm_groupings, generate_schedule_iii, get_spreading_reconciliation, get_setup_status), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.
A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.
The server exposes a public surface before authorization: list_clients, create_client, upload_trial_balance, get_upload, set_header_row, confirm_column_mapping, ingest_upload, list_periods, get_schedule3_workspace, list_grouping_suggestions, confirm_groupings, save_adjustments, save_py_values, save_asset_movements, save_provision_movements, save_reserves_movements, save_share_capital, save_statement_settings, save_disclosures, declare_capture_na, confirm_capture_review, revoke_capture_declaration, copy_capture_declarations, save_partner_capital, get_partner_capital, save_accounting_policies, save_regulatory_affirmations, list_statement_policy_choices, get_finalise_readiness, finalise_statement, get_comparative_source_state, assert_previous_year_no_activity, generate_schedule_iii, get_job, list_snapshots, get_workbook_download, create_upload_link, get_upload_link_status, get_statement_figures, get_statement_notes, get_tb_rows, get_pending_work, list_allocation_runs, get_allocation_account_figures, get_allocation_target_figures, get_spreading_reconciliation, list_budgets, get_budget, get_variance_report, get_consolidated_statements, list_cost_centres, create_cost_centre, list_profit_centres, create_profit_centre, list_account_mappings, confirm_centre_mappings, list_reporting_lines, confirm_reporting_lines, get_setup_status, list_replacements, preview_replacement_restore, restore_replacement, list_chart_rebaselines, preview_chart_rebaseline, confirm_complete_chart, verify_connection, get_help.
Tools
Contract history
Get alerted when this contract changes
Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.
Prefer a feed reader? This page's contract changes are also an Atom feed.
Status badge
Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.
[](https://mcpi.app/servers/schedule-iii)Own this server?
Sign in to claim this listing by proving control of the endpoint.