# Aurgus MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.aurgus%2Faurgus
Registry id: `mcp-registry/com.aurgus/aurgus`
Status: live (checked 2026-11-22T15:14:57.687Z)

## Verdict

Aurgus MCP server answered 97.94% of Glimind's liveness checks over 30 days, better than 14% of MCP servers, with 296 ms median handshake and 17 outages in 90 days. Its agent-readiness grade is A (92/100) across 37 tools, costing an agent about 11,151 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 97.94% | 14% of MCP servers |
| Median handshake latency | 296 ms | 41% of MCP servers |
| p95 handshake latency | 403 ms | — |
| Checks in 30 days | 4,428 | — |
| Outages, 90 days | 17 | — |
| Median recovery | 2 min | — |
| Agent-readiness score | 92/100 (A) | 65% of MCP servers |
| Tools | 37 | — |
| Tool-list size for an agent | ~11,151 tokens | 13% of MCP servers |
| Days observed | 20 | — |

## Install

```json
{
  "mcpServers": {
    "aurgus-mcp-server": {
      "type": "http",
      "url": "https://mcp.aurgus.com/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http aurgus-mcp-server https://mcp.aurgus.com/api/mcp
```

## Tools (37)

- `analyze`: Build a GOVERNED analytics report over the rebate data. Pick a MEASURE and GROUP it BY a dimension — the report is composed from a fixed semantic layer (no raw 
- `aurgus`: THE one way to talk to Aurgus — the client's revenue-management controller. For ANYTHING the user says to Aurgus (a greeting, 'close Q3', 'where are we', 'what 
- `begin`: Call this the moment the user greets Aurgus or wants to start — 'Aurgus, hi', 'hello', 'hey Aurgus', 'let's start', 'I want to run a close', 'where do I begin'.
- `close_agreement`: Close an agreement for good — the terminal true-up at the END of its life (its term ended, or it's being wound down). Closing posts a final true-up Adjustment t
- `compose_agreement`: Build a rebate/incentive agreement by talking it through — no document needed. Describe the program in plain words and Aurgus DRAFTS the terms (who qualifies, h
- `compute_close`: The RUN step (step 6) of an open engagement — work the governed, deterministic earned → settled → open accrual across the engagement's active agreements and cer
- `compute_commission`: Compute a sales-commission engagement under ASC 340-40 (incremental cost to obtain a contract). Give the commission amount, the benefit period it amortizes over
- `compute_lease`: Measure a lease under ASC 842 (v1: the lessee side — real estate and equipment). Give the term, the CERTIFIED discount rate (the rate implicit in the lease, or 
- `compute_revenue_contract`: Run the full ASC 606 five-step recognition for a general revenue contract: identify the performance obligations (Step 2), allocate the transaction price by stan
- `compute_trade_spend`: Split a trade-spend payment to a customer (co-op advertising, MDF, slotting, listing allowance) under ASC 606-10-32-26 / 705-20-25-2. If the payment buys a DIST
- `confirm_grouping`: Record the human's answer to a customer-grouping question Aurgus asked — a grouping compute_close PROPOSED ('GPG LLC resembles Global Procurement Group LLC', or
- `defunct_agreement`: Retire a WRONG agreement that has already accrued — reverse its postings, then archive it. Voiding alone only stops FUTURE accruals; this UNWINDS what already a
- `edit_agreement`: Change an agreement's TERMS — its name, the counterparty (customer_name), the direction (payable_sell_side = you pay a rebate / receivable_buy_side = you earn o
- `edit_agreement_rates`: Change the RATES on a rate-routed (dimension-routed) agreement — a regime's flat rate, a tiered regime's own ladder, or the shared tier ladder. Rates are given 
- `engagement_status`: Report where an engagement stands — derived from the engagement file's real events, not a stored status. With an engagement id, it shows which steps are on the 
- `explain`: State the governed US-GAAP treatment FOR A PAYMENT TYPE — a rebate, incentive, chargeback, or trade-spend payment — under ASC 606 (customer rebate / considerati
- `export`: Put together the auditor-ready package for your tenant: the open accrual you can stand behind (earned → settled → open), where margin is leaking versus what's s
- `export_workpapers`: Deliver the engagement workpapers — the certified figures and the open-items register on one page, from the hash-chained engagement file. Refuses until a princi
- `help`: Call this when the user asks for help or how to use Aurgus — 'Aurgus help', 'help', 'what can you do', 'how do I use this', 'show me the manual', 'what are the 
- `ingest`: Hand Aurgus one of your three rebate files (CSV) to read into your tenant: 'pos' (your POS / sell-through extract — what was earned), 'claims' (the claims you s
- `ingest_agreement`: Hand Aurgus your rebate agreement — PASTE its text, or DROP a PDF/scanned document (pass it as file_base64). Aurgus reads the terms with its deterministic parse
- `list_reports`: List the saved analytics reports on this tenant (name + what each measures). Use `run_report` with a name to re-run one. Requires a connected Aurgus account.
- `open_engagement`: Open a revenue-management engagement for a client. Capture the intake — the client entity, the period, the program(s), the sources of truth, and who will certif
- `open_items`: The engagement's open-items register — the things the close can't yet account for (a document not received, a term not found in the agreement, an unmatched figu
- `recalculate`: Recalculate — re-run the deterministic engine over the POS data, dispatching every row against the agreement(s) so rows that just became eligible (e.g. after a 
- `receive_document`: Receive a client document into an engagement BY REFERENCE — a client-granted signed https link (or an upload handle), never the file's contents. The engine fetc
- `release_notes`: What's new in Aurgus and how to stress-test it — call this for 'what changed', 'release notes', 'what's new', 'changelog', or if you're reviewing/pressure-testi
- `report`: The portfolio report — every active agreement on the tenant (or one, by id), with its earned / settled / open accrual, basis, status, and when it last calculate
- `request_documents`: Draft the PBC (prepared-by-client) document list for an engagement, FROM its agreement — the program decides which files the close needs (a sell-side rebate → t
- `request_real_run`: Get the link to run a real close on your OWN numbers — bring a rebate / SPA / deduction extract and get back audit-defensible accruals, full lineage, and an aud
- `run_report`: Re-run a SAVED analytics report by name on current data — returns the grouped rows + total, governed and read-only exactly like `analyze`. Requires a connected 
- `save_report`: Save an analytics report for reuse. Give it a NAME plus the same measure / group_by (/ dimension_key / agreement_id) you'd pass to `analyze` — the governed spec
- `set_cadence`: Set how often an agreement ACCRUES and SETTLES. Ask the user these when setting an agreement up (or to change them later): (1) how often to accrue — 'realtime' 
- `settle`: Settle an agreement — post the PAYOUT. Creates per-bucket Settlement event(s) totalling the open accrual (earned − already settled), moving the open balance to 
- `sign_close`: A principal signs the governed close for an engagement, by name, on the engagement file. It refuses while any open item remains — the open-items register gates 
- `trace`: Walk any accrued figure all the way back to where it came from — source row → eligibility → bucket → rate → rule → event chain — for a given transaction. This i
- `true_up`: True-up an agreement — AFTER a settlement, match the accrual account to what was ACTUALLY settled. Posts ONE Adjustment (signed = settled − earned) in the CURRE

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
