Formula WorkPaper and XLSX recalculation runtime for Node.js services and agent
Formula WorkPaper and XLSX recalculation runtime for Node.js services and agent tools: edit cells, recalc, verify readback, persist JSON.
active Production-safe Score 89/100 http no auth
At a glance
| Endpoint | https://bilig.proompteng.ai/mcp |
|---|---|
| Source | https://github.com/proompteng/bilig |
| Transport | http |
| Tools | 8 |
| Auth | none |
| First seen | 2026-05-23 11:36:31 |
| Last checked | 2026-11-17 21:41:21 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 840 / 1214 ms |
| Last successful check | 2026-11-17 21:41:21 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (8)
list_sheets— Discover sheet names and used dimensions before reading or editing a WorkPaper. Returns metadata only; use read_range or read_cell for valueread_range— Read calculated values plus serialized formulas/inputs for an A1 range. Use for audit readback after edits; use read_cell for one address.read_cell— Read one cell with calculated value, display text, formula text, formula diagnostics, and serialized content. Use after set_cell_contents toset_cell_contents— Write raw content to one cell and recalculate dependents in memory only. Start with --writable when the edit should persist to JSON.set_cell_contents_and_readback— Write raw content to one cell, recalculate dependents, read a dependent range in the same tool call, and return persistence proof. Use thisget_cell_display_value— Return the formatted display string for one cell. Use when an agent needs what a user would see, not the raw numeric value.export_workpaper_document— Export the current WorkPaper JSON document for persistence, review, or handoff to another agent. Does not write files by itself.validate_formula— Validate formula syntax with the WorkPaper parser before writing it to a cell. This checks syntax only; use set_cell_contents plus readback
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:41:21 | ✓ | ✓ | 697 ms | 90 | active |
| 2026-11-17 20:56:27 | ✓ | ✓ | 900 ms | 90 | active |
| 2026-11-17 20:26:49 | ✓ | ✓ | 905 ms | 90 | active |
| 2026-11-17 19:42:06 | ✓ | ✓ | 800 ms | 90 | active |
| 2026-11-17 19:02:43 | ✓ | ✓ | 792 ms | 90 | active |
| 2026-11-17 18:41:29 | ✓ | ✓ | 723 ms | 90 | active |
| 2026-11-17 17:57:00 | ✓ | ✓ | 928 ms | 90 | active |
| 2026-11-17 17:27:25 | ✓ | ✓ | 1035 ms | 86 | active |
| 2026-11-17 16:42:00 | ✓ | ✓ | 795 ms | 90 | active |
| 2026-11-17 15:55:40 | ✓ | ✓ | 801 ms | 90 | active |
| 2026-11-17 15:24:50 | ✓ | ✓ | 1027 ms | 86 | active |
| 2026-11-17 14:32:36 | ✓ | ✓ | 800 ms | 90 | active |
| 2026-11-17 13:42:25 | ✓ | ✓ | 778 ms | 90 | active |
| 2026-11-17 13:25:01 | ✓ | ✓ | 888 ms | 90 | active |
| 2026-11-17 12:41:07 | ✓ | ✓ | 754 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://bilig.proompteng.ai/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/bilig-proompteng-ai-mcp # JSON