com.aurgus/aurgus
v1.0.0Governed rebate & revenue close (ASC 606/705/842): explain, ingest, compute, trace to source.
Endpoint health
online- Last checked
- 11/20/2026, 4:16:55 AM
- Latency
- 26 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.aurgus%2Faurgus
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.aurgus/aurgus": {
"url": "https://mcp.aurgus.com/api/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
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 SQL), so it's deterministic, read-only, and ties to the ledger (accrued uses the SAME earned formula as the money path). measure: 'accrued' (earned rebate), 'settled' (paid), 'basis' (transaction amount), or 'count' (events). group_by: 'agreement', 'class' (a declared dimension — pass dimension_key, e.g. interchange_class), 'month', or 'quarter'. Optionally restrict to one agreement_id. Returns the grouped rows + total. Use this when the user asks to see/analyze/break down their rebates (e.g. 'rebate accrued by interchange class', 'settled by month'). Requires a connected Aurgus account.
Schema valid · SHA-256 2ffb8b1263b8…
View input schema
{ "type": "object", "properties": { "measure": { "type": "string", "enum": [ "accrued", "settled", "basis", "count" ], "description": "What to measure: accrued (earned) | settled (paid) | basis (transaction amount) | count (events)." }, "group_by": { "type": "string", "enum": [ "agreement", "class", "month", "quarter" ], "description": "How to break it down: agreement | class (needs dimension_key) | month | quarter." }, "dimension_key": { "type": "string", "description": "Required when group_by='class': the declared dimension to group by, e.g. 'interchange_class'." }, "agreement_id": { "type": "string", "description": "Optional — restrict the report to one agreement." } }, "required": [ "measure", "group_by" ], "additionalProperties": false }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 do you need from me'), call THIS with their message rather than picking a specific tool; Aurgus reads the engagement's real state, leads like a firm, and tells you the single next step. Pass entity/period/program when the user has named them (so Aurgus can open the engagement), and engagement_id once one is open. The specialized tools (ingest, compute_close, sign_close, …) are the controller's hands — reach for one only when Aurgus's reply tells you to (e.g. to ingest a CSV, compute with numbers, or sign). Free to greet; a real run on the user's data needs a connected account.
Connections
streamable-http
https://mcp.aurgus.com/api/mcp