Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Removed "connect_integration"; changed the definition of "compute_commission" (38 tools before, 37 now)
⟨26 unchanged words⟩ the contract.","type":"number"},"contract_terminated":{"description":"Set true if the underlying contract was TERMINATED early. The remaining capitalized asset can't simply finish amortizing — it triggers an ASC 340-40-35-3 impairment assessment, raised as an open item rather than closed clean.","type":"boolean"},"elect_practical_expedient":{"description":"Set true ONLY if ⟨75 unchanged words⟩ elapsed into the benefit period at this close.","type":"number"},"remaining_consideration_usd":{"description":"On a terminated contract, the consideration the entity still expects to receive (340-40-35-3(a)). Omit if none/unknown and the full carrying amount is flagged for impairment review.","type":"number"}},"required": ⟨6 unchanged words⟩
Connect the client's ERP / POS / order system (or Zapier) to Aurgus by creating an API key for their account. This is how transactions flow IN automatically (no CSV uploads) and how Aurgus's journal entries flow OUT to their GL — through the Aurgus Open-API (/api/v1) that the key authenticates. The key carries DATA-INTAKE authorization ONLY: it can push transactions and read the journal/position, but it can NEVER run a close, settle, or move money — those stay human-gated in the workspace. Because a key is a real credential, call WITHOUT confirm first to explain what will be created and ask; …
Certificate recorded, valid to 2027-01-02
Authorization not required
Unknown → Live
First tool surface recorded: 38 tools (server version 0.1.0)
https://mcp.aurgus.com/api/mcp (mcp_streamable_http) — from mcp_registry, with the record
Showing the latest 6 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed