numproof
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NUMPROOF_API_KEY | Yes | Your NumProof API key for verification. Obtain one by signing up at https://numproof.com/signup. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| verify_claimA | Exactly verify a math/finance claim -> VERIFY/REFUTE/ABSTAIN with certificate and counterexample. |
| audit_rowsB | Audit spreadsheet-like rows for footing, margins, formula cells, and cell provenance. |
| diff_rowsB | Compare two report versions by numeric row labels with provenance. |
| covenant_rulesB | Check finance covenant rules (e.g. DSCR, Debt/EBITDA) over labeled rows; rule_pack selects a built-in pack such as credit_covenants_basic. Returns a signed covenant bundle. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool addresses a distinct aspect of numeric proof: auditing row-level consistency, verifying standalone claims, comparing versions, and checking covenant compliance. There is no noticeable overlap in purpose.
Three tools follow the verb_noun pattern (audit_rows, verify_claim, diff_rows), but covenant_rules is a noun_noun construction, breaking the pattern. Despite this, all names use consistent lowercase underscores, so the deviation is minor.
With four tools, the server is well-scoped for its specialized domain. Each tool covers a core operation without redundancy, and four is within the ideal range for a focused utility.
The tools cover the primary needs of numeric proof work: auditing rows, verifying claims, diffing versions, and evaluating covenant rules. No obvious missing operations for the stated purpose are apparent.