Deterministic Schedule III statements for Indian companies: trial balance in, Excel workbook out.
Otherv1.0.0streamable-httpapp.datavrn.com
| Registry identity | com.datavrn/schedule-iii |
| Stable evidence key | https://mcpqueen.com/s/com.datavrn/schedule-iii |
| Declared repository | No repository declared Mutable Registry metadata; not proof of current ownership or availability. Mapping synchronized . |
| Operational endpoint | https://app.datavrn.com/api/mcpProbed separately from repository state. |
Repositories can be renamed, transferred, archived, privatized, or deleted. MCP Queen keeps this evidence page and badge keyed to the Registry name. Moved this repository? Follow the maintainer guide.
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 925ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo mcp-typescript server on vercel@0.1.0 |
| tooling | 35 / 35 | tools/list OK: 47 tools e.g. "list_clients"; 47/47 described, 47/47 fully-typed schemas, median description 387 chars |
| latency | 7 / 10 | initialize round-trip 925ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.0.0; namespace com.datavrn matches endpoint/repo |
Score 94/100 · latency 925ms · 47 tools · protocol access: open ⓘ
Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.
| Dimension | Metric | Status | Evidence | Source |
|---|---|---|---|---|
| security | sensitive_capabilities_declared | concern | 2 discovered tool(s) advertise potentially state-changing or privileged capabilities. Tool names: list_clients, get_setup_status. Classification is description-based and does not prove exploitability. Observed value: list_clients, get_setup_status Sample: n=2 | live_probe |
| security | authentication_boundary | observed | Live protocol probe observed auth_state=open. This describes discovery/access behavior; it is not by itself a vulnerability finding. Observed value: open | live_probe |
Machine-readable receipt: /api/trust/com.datavrn/schedule-iii.json
Claude Code:
claude mcp add --transport http schedule-iii https://app.datavrn.com/api/mcp
Generic MCP client config:
{ "mcpServers": { "schedule-iii": { "type": "http", "url": "https://app.datavrn.com/api/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/com.datavrn/schedule-iii · referral link https://mcpqueen.com/go/com.datavrn/schedule-iii (counts as “routed via the queen”).
Live operational-grade badge, re-probed continuously — not a security or data-quality certification. Copy the ready-made Markdown into your README:
[](https://mcpqueen.com/s/com.datavrn/schedule-iii)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-08-06 19:30 | A | 94 | 925ms |