Repository navigation
Releases
0.3.3 — afg editioncheck
Nothing changes for MCP clients.
afg editioncheck <period>, a reader's check of a State of Agent Money edition (2026-09, or2026-Q4when quarters exist):- the edition file's SHA-256 is found in the statement log as
publication/1|<slug>|<sha>|<at>(the log's signed head isafg logwatch's job); - the registrations minted in the period and the total at its end are re-derived from the ERC-8004 Identity Registry at the period's first and last block, through a public Base RPC we do not run (agent ids are sequential, so the highest id that answers
ownerOfat a block is the count), and compared with the edition's figures; - every definition id the edition cites resolves on
/api/def; - counted payments are not re-derived (they need the ledger's binding set);
afg chaincheck <agent>does that for one agent.
- the edition file's SHA-256 is found in the statement log as
- On 24 Oct the September 2026 edition passed: 16,013 minted between blocks 50,715,727 and 52,011,727 and 96,637 at the end, both equal to the file.
v0.3.2: afg logwatch
afg logwatch: an outside monitor for our statement log.
Run it once, then daily:
- It checks the Ed25519 signature on the current signed tree head.
- It verifies an RFC 9162 consistency proof from the head it kept last time.
- If the published history was ever rewritten, the proof fails and the command exits 1. A shrinking tree or a changed key is reported too.
npx -y github:AgenticFinanceGraph/agentic-finance-graph-mcp logwatch
On 23 Oct 2026 the live log (153 entries) verified, including proofs from sizes 1, 2, 64, 100, 137 and 152. Nothing changes for MCP clients. Tests: 38.
v0.3.1: afg chaincheck
afg chaincheck <agent-id>: check an agent's record against the chain itself.
The record comes from our API. Every check is answered by a public Base RPC that we do not run (https://mainnet.base.org by default; set AFG_BASE_RPC to use your own):
- Registration: the mint transaction minted the token to the stated account, at the stated time.
- Bindings: each open binding still holds (
ownerOf,getAgentWallet; a minting-account binding equals the account the registration was minted to). - Payments: every payment in the money path is a successful USDC, USDT, EURC or DAI transfer, matched by contract address, from a bound wallet to the stated recipient, for the stated amount, after the registration.
npx -y github:AgenticFinanceGraph/agentic-finance-graph-mcp chaincheck 57067
A claim the RPC did not return is shown as unread, never as passed. The exit code is 1 only when a claim read from the chain does not hold. On 23 Oct 2026 the top 10 ranked agents and five others passed every claim.
Nothing changes for MCP clients. Tests: 34.
0.3.0 — the security layer (shadow) and the x402 Gate hook
Mirrors the seven security-layer tools the server gained on 16 Oct 2026, all in shadow / log-only mode: agent_pattern, payee_facts, gate_check, agent_pass, blast_radius, canary_register, canary_status. Every answer is a measurement with its time and definition id; nothing is a verdict and nothing is blocked by us.
- CLI:
afg pattern <id>,afg facts <payee> [agent] [usd],afg gate <agent> <payee> <usd> [policy],afg pass <id>,afg blast <id|0xwallet>. bin/x402-gate-hook.mjs: anonBeforePaymentCreationhook for@x402/core2.x that asksgate_checkbefore signing and aborts on the decisions the operator chooses; fail mode is the operator's (warnby default,abort,allow).- Stranger-written fields (
declared_name,endpoint, feedbackuri/file_uri, tags, caller echoes) now arrive as{untrusted: true, source, text}; a client that readdeclared_nameas a string reads.text. - Ten new tests against a stand-in server (26 in all), no dependencies.
How it works, with live figures: https://agenticfinancegraph.com/security
0.2.5: payer_set, poisoning rule v2, statement log (server 1.5.0)
Nothing to install for MCP clients; the CLI is unchanged.
-
A new tool,
payer_set. It returns the wallets observed paying one agent (income into its bound wallets, plus counted payments from other registered agents), up to 250, with payments, USD and first and last paid. It also says how much of the agent's ERC-8004 feedback is payment-grounded, meaning the reviewer paid before rating.get_summary_inputis ready for the Reputation Registry'sgetSummary(agentId, clientAddresses), the reviewer filter the standard asks for. It is also served at/api/payers?agent=. Paying first does not make a reviewer independent: one agent's 85 reviews all came from one wallet that pays it. -
Address-poisoning rule v2. The watch now also counts a look-alike that matches a payee on the first 3 and last 4 hex characters, the threshold of Tsuchiya, Dong, Soska and Christin (USENIX Security 2025), and still counts fake-token plants that match only the last 4. Measured before the change:
- of 82,132 plants either rule counts, the old rule found 80,509 and the paper's 80,880;
- a second read from the chain found every one of 300 sampled plants sent by somebody other than the wallet.
poison.*.v2definitions; v1 is kept and marked superseded. -
A statement log that cannot be quietly rewritten. Every signed statement-window root is a leaf of an append-only log in the shape of Certificate Transparency (RFC 6962), with a signed tree head and consistency and inclusion proofs at
/api/statements/log. -
Endpoint-domain verification in the liveness sweep (ERC-8004's
/.well-known/agent-registration.json), and a data check for unexplained steps in our own series, with the list at/api/steps. Both are listed bylist_metricsand dated in/api/changepoints.
v0.2.4 — pay_check, list_metrics, changepoints
MCP server 1.4.0 (nothing to install for MCP clients; the CLI is unchanged).
- Two new tools:
pay_check(one free call before paying an agent: statement freshness and chain, live incidents, detections in the last 72 hours, last payment, payments since the statement, which refuse conditions are met) andlist_metrics(every metric with key, unit, definition id, first stored sample,comparable_since). - Our own changes, dated: a register at /api/changepoints;
metric_historyreturns the ones inside the range andcomparable_since;since_lastflagschangepoint_in_window;market_statefigures carrycomparable_since. market_state.composition: what counted spending consists of, ten parts from one pass that add up to the counted total; adata_qualityblock;pay_usd_last_daynames its day.- Definitions:
rank.l8plus.v2andrank.l9.v2state the four-stablecoin rule the counts have followed since 27 September; every definition returns dated revisions andbody_sha256. - A
start_hereprompt, server instructions for the first "what can you do?", and three resources (afg://guide,afg://changepoints,afg://definitions).
Full list: CHANGELOG.md.
v0.2.3 — prompts and typed results
Server-side, nothing to install for MCP clients (MCP server 1.3.0):
- Prompts:
daily_brief,check_before_paying,explain_agentandwhere_agents_pay. Clients such as Claude list them in the prompt menu. - Typed results:
market_state,ranked_agentsandagent_recordreturnstructuredContentwith anoutputSchema. - Protocol: negotiates MCP 2025-11-25 as well as 2025-06-18, 2025-03-26 and 2024-11-05; declares prompts and resources.
market_statenotes thatactors_l8_plusmoves in steps when an operator funds a fleet of its own registrations;actors_l9is the steadier measure.
The bridge and the CLI are unchanged. Setup: https://agenticfinancegraph.com/mcp-server-connect-your-ai-to-agent-money-data
v0.2.2 — check before you pay
Three new paid packs on the server (MCP server 1.2.0), quoted by evidence_pack_quote:
precheck(5 cents): the routine check before an agent pays or hires another. Level and last observed payment, live incidents, how old its latest statement is and whether the chain is intact, and, withpayto, what the address it gave you is: label and basis, contract or plain key, how many registered agents paid it, whether this agent paid it before, and whether our poisoning watch saw it planted as a look-alike. Facts only, never a verdict.venue(3 cents): what one address on Base is, who pays it, and its stablecoin flow over the last 48 hours, read live.builders(1 cent): the ERC-8021 Builder Codes on one agent's counted payments.
The CLI passes a payto as a third argument: afg quote precheck 53008 0x…. The skill afg-check-agent (0.2.0) names the precheck as the one-call version of its workflow.
Prices and every pack: https://agenticfinancegraph.com/pricing
v0.2.1: Dockerfile and where the server is listed
A Dockerfile for the stdio bridge, so directories that start servers from source can introspect it: docker run -i --rm afg-mcp serves the same eleven read-only tools by forwarding to https://agenticfinancegraph.com/mcp.
The README now lists where the server is published: the official MCP Registry as com.agenticfinancegraph/agentic-finance-graph (publisher verified by domain), Smithery and Glama (health-checked). The paid evidence packs are in the Coinbase x402 Bazaar and on x402scan.
No change to the tools or the CLI commands. Read-only, no key, nothing here can move funds.
v0.1.1: security scanning, lockfile, Dependabot, and new figures in market_state
Security
- Every push and pull request is now scanned by the HOL AI Plugin Scanner, pinned to an exact commit and run with read-only permissions. First run: 88/100, with two requests, both done in this release.
- A lockfile (
package-lock.json), so dependency resolution is reproducible. The package still has no dependencies. - Dependabot watches the GitHub Actions and npm manifests weekly.
New in market_state (server side: nothing to update in your client)
- Where counted agent money that left Base through bridges arrived, and how much of it reached the paying wallet's own address on the other chain.
- Counted dollars by the paying wallet's account type: contract account, plain key, EIP-7702 delegated.
- Our own count of ERC-8004 registrations on BNB Smart Chain (issuance, not agents).
Each figure carries its definition id; call definition for the method. Full history: CHANGELOG.md and the site changelog.
Connect: claude mcp add --transport http afg https://agenticfinancegraph.com/mcp