Servidor MCP de Aurgus

• Nome no registrocom.aurgus/aurgusverificado no registro MCP

O nome no registro fica sob aurgus.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-11-01
• Ferramentas38
• O servidor se chamaaurgus
• Versão do servidor0.1.0
• Versão do protocolo2025-06-18

Em 2026-11-01 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 207 ms.

• As ferramentas fazem todos os casos de uso verificados: Reconcile rebate accruals against contract sales, claims and payments; Trace each accrual figure back to its source rows; Replay a calculation to explain how a rebate number was reached.
• Verificado em 2 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 2 até agora
• O que um agente consegue fazer com ele3 de 3 casos de uso
• Respondeumedindo2 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta257 ms
• Espaço no contexto do agente≈ 11.721 tokensas definições de todas as ferramentas (38), que o agente carrega a cada turno
• Definições das ferramentasA · 100 de 100
• Resultados tipados0 de 38 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Todas as ferramentas passam nas seis verificações.

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• 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'. Aurgus introduces itself as the client's independent revenue-management…

• 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 commands / trigger words'. Returns the Aurgus manual: what it is, how an…

• 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-testing the product. Returns the current release summary (reuse-first institutional…

• explain

  State the governed US-GAAP treatment FOR A PAYMENT TYPE — a rebate, incentive, chargeback, or trade-spend payment — under ASC 606 (customer rebate / consideration payable to a customer / variable consideration), ASC 705-20 (vendor…

• 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 auditor-ready export, with nothing posted to your GL. Use this when the user is…

• 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…

• 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 certify — and start the engagement file (a hash-chained, append-only record of…

• 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 chain, what's next, and any open items (the close can't be signed while any…

• 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 → the POS / sell-through extract; a buy-side billback → the claims file), never a…

• 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 figure). List them, open a new one, or resolve one by id. The register ships…

• 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 fetches it server-side, stages it inside the client's tenant for certification…

• 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, and how many months have elapsed; it classifies the cost, then capitalizes a…

• 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 standalone selling price (Step 4), and recognize over time or at a point in time…

• 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 the incremental borrowing rate — it will NOT assume one), and the payment…

• 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 DISTINCT good or service the customer actually provides (e.g. advertising with…

• 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 the signature — and a close must have been computed. You cannot sign on the…

• 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 principal has signed the close. This is the auditor-ready deliverable: what was…

• 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 parser (and CV/OCR for a PDF/scan — a Python CPU service, ZERO LLM): customer…

• 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, how volume is measured and over what period, the threshold, the rate or…

• 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 submitted), or 'credits' (credit memos / vendor invoices you received). Give it…

• 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 certified data. Do NOT call this as the first thing when a user says 'compute the…

• 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 'these are the GPO's members'), OR a change to a roster Aurgus already knows…

• 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 calculated. This is the book-at-a-glance a controller watches: which agreements are…

• 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' as sales land, or batched 'daily' / 'weekly' / 'monthly' / 'per_event'; (2)…

• 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 that matches the accrual to the settled amount (open → $0), THEN FREEZES the…

• 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 accrued by appending a Reversal for every earning event (earned → $0, strictly…

• 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 CURRENT period so earned equals settled and the open balance nets to $0…

• 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 in PERCENT (1.5 = 1.5%); thresholds in dollars. Call WITHOUT confirm first to…

• 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 one), the validity window (valid_from / valid_to, YYYY-MM-DD; pass…

• 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…

• 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 is stored under that name (re-saving the same name updates it). Later…

• 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.

• 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 Aurgus account.

• 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 data fix or a rule change) accrue. Posts provisional accruals (the same engine…

• connect_integration

  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…

• 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 $0. This is the money-OUT step (distinct from compute_close, which accrues…

• 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 is how you show an auditor exactly why a number is what it is. Requires a…

• 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 sitting outside any program, and sample lineage tracing back to source — all…