FiatDock

Address intelligence on Base ($0.0045)

address_intel

Read-onlyIdempotent

PAID ($0.0045 USDC via x402). Enrich ANY Base address in one call before you trust it: EOA vs contract (and whether it's an ERC-20, with its name/symbol/decimals), account nonce, ETH + USDC balance, and a KEYLESS GoPlus security verdict (phishing / sanctioned / mixer / money-laundering / blacklist and more) — the loop input for triaging a counterparty, payout target or approval spender. Without payment this returns the 402 challenge; the fiatdock-mcp npm package pays automatically. A bad address returns 400; if Base RPC or GoPlus is unavailable it returns 502 — neither is charged.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`address`	Yes	A 40-hex EVM address (0x…) on Base to enrich
`payment`	No	Base64 of a single x402 v2 PaymentPayload (EIP-3009 transferWithAuthorization on Base USDC). OMIT it on the first call: the 402 you get back carries `howToPay.payloadTemplate` — the exact envelope to fill in — plus the price and the EIP-712 domain. Send it on the second call to complete the purchase; it is forwarded as the PAYMENT-SIGNATURE header, never as body data. Nothing is charged for the 402 itself, and a call that fails after payment settles nothing.

Output Schema

TableJSON Schema

Name	Required	Description
`asOf`	Yes	ISO 8601 read time
`type`	Yes	eoa \| contract \| erc20_contract
`nonce`	Yes	Outgoing transaction count (account nonce)
`token`	Yes	ERC-20 identity when isErc20, else null
`address`	Yes	The queried address
`isErc20`	Yes	true if it is an ERC-20 token contract
`network`	Yes	Chain read (always base)
`summary`	Yes	One-line human-readable verdict
`security`	Yes	Keyless GoPlus address-security verdict
`ethBalance`	Yes	Native ETH balance as a decimal string
`isContract`	Yes	true if the address has bytecode on Base
`usdcBalance`	Yes	USDC balance as a decimal string

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 23, 2026

addedInput schema / properties / payment

Added value: +{
+  "description": "Base64 of a single x402 v2 PaymentPayload (EIP-3009 transferWithAuthorization on Base USDC). OMIT it on the first call: the 402 you get back carries `howToPay.payloadTemplate` — the exact envelope to fill in — plus the price and the EIP-712 domain. Send it on the second call to complete the purchase; it is forwarded as the PAYMENT-SIGNATURE header, never as body data. Nothing is charged for the 402 itself, and a call that fails after payment settles nothing.",
+  "type": "string"
+}

AddedJul 29, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnly/openWorld/idempotent, but the description discloses far more: a $0.0045 x402 payment requirement, the 402 challenge on an unpaid first call, the npm package that auto-pays, a 400 for bad addresses and 502 for RPC/GoPlus outages, and the guarantee that neither failure is charged. That is exactly the behavioral context an agent needs before invoking a paid tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the cost and the core capability, then the payment mechanics and error codes. It is dense and mostly earns its space, though 'PAID ($0.0045 USDC via x402)' mildly duplicates the title's price and the single dash-heavy sentence packs a lot together.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be spelled out, annotations carry the safety profile, and the description still covers the paid-call flow, the auto-pay path, and both failure codes. Nothing an agent needs to invoke this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both the address format and the payment payload envelope, establishing a baseline of 3. The description adds real value on the payment parameter's lifecycle — omit it first, read howToPay.payloadTemplate from the 402, resend on the second call — clarifying the two-step flow beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (enrich) and resource (any Base address) and enumerates exactly what comes back: EOA vs contract detection, ERC-20 metadata, nonce, ETH/USDC balances, and a GoPlus security verdict. That specificity distinguishes it from sibling lookups like token_safety, eth_balance, or domain_intel without opening their schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context — 'before you trust it,' triaging a counterparty, payout target, or approval spender — which tells the agent when this tool is the right call. It stops short of naming an alternative sibling to use instead when the agent only needs a single balance or token-safety verdict, so exclusions are absent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FiatDock tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.