# Agoranome buyer checks and market data (remote · api.agoranome.com)

Free tools for agents that pay with x402: the fair pick, a check before paying, buyers' reports.

- Trust score: 75/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.agoranome.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/agoranome-agoranome/api.md), [page](https://verifymcp.io/servers/agoranome-agoranome/api)

## Channel facts

- Endpoint: `https://api.agoranome.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 4018 tokens (~223/item across 18 items; 17 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 28/100
  - Stability check failed: schema churn in the 27 days we've observed: 8 tool removals, 0 breaking changes, 0 auth/transport breaks, 12 additions.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Agoranome buyer checks and market data MCP server?

Agoranome buyer checks and market data is a hosted endpoint at https://api.agoranome.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http agoranome-agoranome 'https://api.agoranome.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "agoranome-agoranome": {
      "url": "https://api.agoranome.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "agoranome-agoranome": {
      "type": "http",
      "url": "https://api.agoranome.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.agoranome-agoranome]
url = "https://api.agoranome.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agoranome-agoranome": {
      "type": "remote",
      "url": "https://api.agoranome.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add agoranome-agoranome --url 'https://api.agoranome.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  agoranome-agoranome:
    url: "https://api.agoranome.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "agoranome-agoranome": {
      "Transport": "http",
      "Url": "https://api.agoranome.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add agoranome-agoranome -t streamable-http -u 'https://api.agoranome.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "agoranome-agoranome": {
      "type": "http",
      "url": "https://api.agoranome.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 25 to 28.

### 2026-11-19 (score 74, −1)

- [security regression] A breaking change shipped without a version bump: still 1.0.4
- [security regression] Tool “payer_mix” was removed
- [security regression] Tool “fund_commons” was removed
- [security regression] Tool “insights_page” was removed
- [security regression] Tool “mandate_check” was removed
- [security regression] Tool “payer_analytics” was removed
- [security regression] Tool “pick_odds” was removed
- [security regression] Tool “repeat_demand” was removed
- [security regression] Tool “research_brief” was removed
- [security regression] Tool “row_set” was removed
- [security regression] Tool “server_standing” was removed
- [security regression] Tool “solana_reach” was removed
- [security regression] Tool “status_credential” was removed
- [security regression] Tool “survival_odds” was removed
- [security regression] Tool “weekly_insights” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “ping” rewrote its description, which is the text the model reads
- [security] Tool “price_position” rewrote its description, which is the text the model reads
- [security] Tool “proof_value” rewrote its description, which is the text the model reads
- [security] Tool “which_delivers” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 310 → 223
- [cosmetic] “fair_pick” reworded the description of “rule”
- [cosmetic] “proof_value” dropped the optional parameter “kyapay-token”

### 2026-11-18 (score 75, 0)

- [security] Tool “server_standing” rewrote its description, which is the text the model reads
- [security] Tool “which_delivers” rewrote its description, which is the text the model reads
- [cosmetic] Tool “server_standing” changed its title: MCP server standing (answers from 17 Nov 2026) → MCP server standing
- [cosmetic] Tool “which_delivers” changed its title: Which paid offers deliver (not answering yet) → Which paid offers deliver

### 2026-11-17 (score 75, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “buyer_check” rewrote its description, which is the text the model reads
- [security] Tool “dispute_pack” rewrote its description, which is the text the model reads
- [security] Tool “fair_pick” rewrote its description, which is the text the model reads
- [security] Tool “price_position” rewrote its description, which is the text the model reads
- [security] Tool “rank_sample” rewrote its description, which is the text the model reads
- [security] Tool “repeat_demand” rewrote its description, which is the text the model reads
- [security] Tool “solana_reach” rewrote its description, which is the text the model reads
- [security] Tool “which_delivers” rewrote its description, which is the text the model reads
- [cosmetic] “buyer_check” added an optional parameter “network”
- [cosmetic] “dispute_pack” added an optional parameter “network”
- [cosmetic] “fair_pick” added an optional parameter “rule”
- [cosmetic] “response_scan” added an optional parameter “payment_tx”
- [cosmetic] “which_delivers” added an optional parameter “network”
- [cosmetic] “buyer_check” reworded the description of “tx”
- [cosmetic] “dispute_pack” reworded the description of “tx”
- [cosmetic] “insights_page” reworded the description of “page”
- [cosmetic] “response_scan” reworded the description of “share”
- [cosmetic] Tool “which_delivers” changed its title: Which paid offers deliver → Which paid offers deliver (not answering yet)

### 2026-11-16 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “fund_commons” rewrote its description, which is the text the model reads
- [security] Tool “insights_page” rewrote its description, which is the text the model reads
- [security] Tool “payer_analytics” rewrote its description, which is the text the model reads
- [security] Tool “payer_mix” rewrote its description, which is the text the model reads
- [security] Tool “pick_odds” rewrote its description, which is the text the model reads
- [security] Tool “ping” rewrote its description, which is the text the model reads
- [security] Tool “price_position” rewrote its description, which is the text the model reads
- [security] Tool “proof_value” rewrote its description, which is the text the model reads
- [security] Tool “repeat_demand” rewrote its description, which is the text the model reads
- [security] Tool “research_brief” rewrote its description, which is the text the model reads
- [security] Tool “row_set” rewrote its description, which is the text the model reads
- [security] Tool “server_standing” rewrote its description, which is the text the model reads
- [security] Tool “survival_odds” rewrote its description, which is the text the model reads
- [security] Tool “weekly_insights” rewrote its description, which is the text the model reads
- [security] Tool “which_delivers” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 253 → 306
- [functional] New tool “mandate_check”
- [functional] New tool “solana_reach”
- [functional] New tool “status_credential”
- [cosmetic] “row_set” added an optional parameter “network”
- [cosmetic] “pick_odds” reworded the description of “category”
- [cosmetic] “pick_odds” reworded the description of “price”
- [cosmetic] “price_position” reworded the description of “category”
- [cosmetic] “price_position” reworded the description of “price”
- [cosmetic] “price_position” reworded the description of “resource”
- [cosmetic] “proof_value” reworded the description of “price”
- [cosmetic] “repeat_demand” reworded the description of “category”
- [cosmetic] “survival_odds” reworded the description of “category”
- [cosmetic] “survival_odds” reworded the description of “price”
- [cosmetic] “survival_odds” reworded the description of “resource”
- [cosmetic] “which_delivers” reworded the description of “category”

### 2026-11-14 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 21.

### 2026-11-12 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 11 to 14.

### 2026-11-11 (score 72, −6)

- [security regression] Stability: 0.53 → fail
- [security regression] Tool “buyer_drill” was removed
- [security regression] Tool “buyer_panel” was removed
- [security regression] Tool “certify_continuous” was removed
- [security regression] Tool “certify_offer” was removed
- [security regression] Tool “conformance_check” was removed
- [security regression] Tool “demand_gaps” was removed
- [security regression] Tool “model_watch” was removed
- [security regression] Tool “rank_check” was removed
- [security regression] Tool “rank_watch” was removed
- [security regression] Tool “signed_sample” was removed
- [security regression] Tool “vendor_watch” was removed
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “buyer_check” rewrote its description, which is the text the model reads
- [security] Tool “dispute_pack” rewrote its description, which is the text the model reads
- [security] Tool “lint_listing” rewrote its description, which is the text the model reads
- [security] Tool “plan_quote” rewrote its description, which is the text the model reads
- [security] Tool “response_scan” rewrote its description, which is the text the model reads
- [security] Tool “spend_audit” rewrote its description, which is the text the model reads
- [security] Tool “pick_odds” rewrote its description, which is the text the model reads
- [security] Tool “which_delivers” rewrote its description, which is the text the model reads
- [functional improvement] Schema quality: 288 → 253
- [functional] Server version: 1.0.3 → 1.0.4
- [functional] New tool “fair_pick”
- [cosmetic] “buyer_check” dropped the optional parameter “kyapay-token”
- [cosmetic] “dispute_pack” dropped the optional parameter “kyapay-token”
- [cosmetic] “lint_listing” dropped the optional parameter “kyapay-token”
- [cosmetic] “plan_quote” dropped the optional parameter “kyapay-token”
- [cosmetic] “response_scan” dropped the optional parameter “kyapay-token”
- [cosmetic] “spend_audit” dropped the optional parameter “kyapay-token”
- [cosmetic] Tool “pick_odds” changed its title: Pick odds (not answering yet) → Pick odds
- [cosmetic] Tool “which_delivers” changed its title: Which paid offers deliver (not answering yet) → Which paid offers deliver

## MCP tools (17)

### `ping` (~262 tokens)

Payment test

x402 test payment: can this wallet pay an x402 API? A paid call of a fraction of a cent in USDC on Base or Solana that returns a signed receipt, proof that the wallet, its spending limit and its x402 client (an AgentCore payments session, a CDP or Privy wallet, or any other client) complete a real paid call end to end, plus what Agoranome already knows about the wallet. For an agent's first payment, before it buys anything bigger. Price: $0.001 in USDC per call, paid with x402 inside the tool call. Same price over HTTP, which any x402 client pays without MCP (prefer it if your client pays HTTP 402s): GET https://api.agoranome.com/v1/machine/ping. Or send a Skyfire pay or kya-pay token in the kyapay-token header (or in this tool's kyapay-token argument), and this tool charges $0.001 to it. Failed calls aren't charged.

Input parameters:

- `kyapay-token` (string): A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.

### `price_position` (~364 tokens)

Price position

Is this x402 seller's price high or low for its category? One signed number for the moment before paying: where a price per call sits among the established sellers in the same category, with its 95% range, the same place counted by calls, the category's median, p10 and p90, the seller count and the four newest weeks. Takes a category and the price asked, or the listing's URL. Asked again with its ETag, an unchanged answer is a free 304. Price: $0.001 in USDC per call, paid with x402 inside the tool call. Same price over HTTP, which any x402 client pays without MCP (prefer it if your client pays HTTP 402s): GET https://api.agoranome.com/v1/facts/price-position?category=web_search&price=0.01. Or send a Skyfire pay or kya-pay token in the kyapay-token header (or in this tool's kyapay-token argument), and this tool charges $0.001 to it. Failed calls aren't charged.

Input parameters:

- `category`: Category, such as web_search
- `if_none_match`: Send the answer's ETag back in If-None-Match (over MCP, the if_none_match argument): while the answer is unchanged it comes back as a free 304 Not Modified.
- `kyapay-token` (string): A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.
- `price`: Price per call in USD, such as 0.01
- `resource`: Or your listing's URL, in place of category and price

### `which_delivers` (~402 tokens)

Which paid offers deliver

Before paying one of several x402 tools for the same task: which ones deliver? The five offers in a category most likely to deliver at their listed terms, by odds from Agoranome's own paid calls, with price, listing and the order rule stated. Sellers the evidence can't tell apart rotate daily, and the answer says whether the odds are validated yet. Takes a category, an optional price cap and network. Read from the daily deliver feed: no new spend, no model call, refused unpaid when stale. Price: $0.002 in USDC per call, paid with x402 inside the tool call. Same price over HTTP, which any x402 client pays without MCP (prefer it if your client pays HTTP 402s): GET https://api.agoranome.com/v1/facts/delivers?category=web_search. Or send a Skyfire pay or kya-pay token in the kyapay-token header (or in this tool's kyapay-token argument), and this tool charges $0.002 to it. Failed calls aren't charged.

Input parameters:

- `category` (string, required): Category, such as web_search
- `explore`: Optional: give the fifth place to the most recently listed seller with an attested sample and no probe yet, labelled exploration
- `if_none_match`: Send the answer's ETag back in If-None-Match (over MCP, the if_none_match argument): while the answer is unchanged it comes back as a free 304 Not Modified.
- `kyapay-token` (string): A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.
- `max_price`: Optional: only offers at or under this price per call in USD
- `network`: Optional: only offers whose listing takes USDC on this network's mainnet, at their price there

### `fair_pick` (~251 tokens)

Fair pick

Which paid API should my agent call for this job? Paid x402 and MPP endpoints that fit a job in plain words, under your price per call, ranked by a published rule no seller can pay for: only offers that answered payable this week, those that asked what they list first, then a Fair Offer block, then the closer fit, then the lower price, two places a seller at most. From the inspector's signed weekly tables; anyone can recompute it. Free at agoranome.com/pick. Free: no payment is asked.

Input parameters:

- `budget_usd`: Optional: the most to pay for one request, in USD
- `job` (string, required): What the endpoint should do, in plain words
- `kyapay-token` (string): A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.
- `limit` (integer): How many to return
- `market`: Optional: one market only
- `rule`: Optional: pick-2 (the default, the inspector's public rule) or pick-1, its first

### `lint_listing` (~154 tokens)

Listing lint

Why isn't my x402 API in the Bazaar? Listing lint checks an x402 endpoint for Bazaar indexing: one unpaid call validates its 402 PAYMENT-REQUIRED header, discovery metadata, input and output schemas, description limits and service name against the indexing rules, with a fix for each problem and the fixed 402 ready to paste, graded as the weekly report card would grade it. Also lints A2A agent cards. Use when an agent needs to lint an x402 listing or A2A agent card before its first sale. Free: no payment is asked.

Input parameters:

- `url` (string, required): Public https URL of the paid endpoint, or of an A2A agent card (/.well-known/agent-card.json)

### `buyer_check` (~289 tokens)

Buyer check

Use when a buyer agent is about to pay an x402 seller it hasn't paid before, or above its usual amount: a signed verdict from what Agoranome holds: the Fair Offer block and certification, the pay-to and since when, OFAC sanctions on it, Google Web Risk on the URL, price against listing and quote, verified deliveries, policy tiers met. Give url= up to 20 times to rank sellers safest first. With tx=, settlement proof: the USDC transfer on Base, Monad or Solana and if it matched the quote. Free: no payment is asked.

Input parameters:

- `accept_proof`: Your requirements, as an Accept-Proof value
- `expected_price`: The quoted price in USD
- `max_price` (number): Your per-call cap in USD
- `network`: Settlement mode: eip155:8453 (Base, the default), eip155:143 (Monad) or solana
- `pay_to`: The quoted pay-to address
- `share` (boolean): Settlement mode: publish the buyer-side receipt in the evidence commons
- `tx`: Settlement mode: the payment's transaction hash on Base or Monad, or its signature on Solana
- `url` (required): The x402 offer's URL, or a list of up to 20 offer URLs to check in one call for the same price, listed safest first

### `spend_audit` (~189 tokens)

Wallet statement

Use when a buyer agent or its operator must account for an x402 wallet's spending: a statement for a buyer wallet on Base. Every USDC payment checked against the payee's listed Bazaar price (above listed, oversize 10x or more, unlisted), spend and calls per seller, duplicate payments within a minute, payments after a seller's listing vanished or its pay-to changed, sellers whose certification failed since, whether the wallet looks sweep-like, and a CSV of every payment. Free: no payment is asked.

Input parameters:

- `days` (integer): Days to look back
- `ticket`: Optional: true to get a ticket instead of waiting. The run then has minutes instead of 85 s and waits for a busy slot; the paid answer is the ticket, and its result is free with the job_status tool.
- `wallet` (string, required): Buyer wallet address on Base

### `response_scan` (~198 tokens)

Response safety scan

Use when a buyer agent is about to act on a paid x402 response: post the body, or passages of it, with the seller's URL and get back instruction-like passages aimed at an agent, hidden characters, exfiltration links, a mismatch against the seller's declared output example, and whether its "data, never instructions" claim held. Nothing posted is stored; with share=true a contradicted claim becomes evidence on the seller's record, as hashes. Free: no payment is asked.

Input parameters:

- `body`: The paid response body
- `payment_tx`: With share: your payment for this response on Base, settled in the last 24 hours
- `seller` (string, required): The x402 offer's URL the response came from
- `share` (boolean): Let a contradicted claim count as evidence on the seller's record (hashes only); needs payment_tx
- `spans`: Or: passages of the body

### `plan_quote` (~140 tokens)

Pre-flight plan quote

Use when a buyer's planner agent is about to start a batch of paid x402 calls: post a plan of seller URLs and call counts and get the total cost, each seller's listing and certification state, its expected failure share from reconciled receipts, the fit against your caps (per call, per seller, total, policy tier), and every certified seller in the same category sorted by price with the sort key stated. Free: no payment is asked.

Input parameters:

- `caps`: max_price_usd, max_per_seller_usd, max_total_usd, tier
- `plan` (array, required): Lines of {seller: URL, calls: n}

### `dispute_pack` (~278 tokens)

Dispute evidence pack

Use when a buyer agent was charged by an x402 seller and not served: given the payment's transaction hash, the seller URL, the accepted 402 and the response, get the settlement on Base, Monad or Solana, the Fair Offer terms at quote time (failed calls free, receipts, refunds), what Agoranome observed of that seller in that hour, the seller's published contact and a draft claim addressed to it, all signed. Free: no payment is asked.

Input parameters:

- `claim`: What went wrong, in your words
- `expected_price_usd`
- `network`: Where the payment settled: eip155:8453 (Base, the default), eip155:143 (Monad) or solana
- `offer`: The accepted 402 as received
- `pay_to`
- `response`: status, body or body_sha256, headers, received_at
- `seller` (string, required): The x402 offer's URL
- `ticket`: Optional: true to get a ticket instead of waiting. The run then has minutes instead of 85 s and waits for a busy slot; the paid answer is the ticket, and its result is free with the job_status tool.
- `tx` (string, required): The payment's transaction hash on Base or Monad, or its signature on Solana

### `proof_value` (~191 tokens)

Proof value at your price

What is a proof worth at my x402 price? One signed number: the premium buyer-agent models gave a cue (a passed certification, an attested sample, pay on delivery, signed receipts, a pledge, the data-not-instructions declaration, or a fake payer count, urgency or an authority claim), in dollars at your price, with its 95% range and whether it's beyond chance, from the newest readable price-of-proof run, and only near the listing prices that run tested. Free: no payment is asked.

Input parameters:

- `cue` (string, required): The proof or manipulation to price
- `if_none_match`: Send the answer's ETag back in If-None-Match (over MCP, the if_none_match argument): while the answer is unchanged it comes back as a free 304 Not Modified.
- `price` (number, required): Price per call in USD, such as 0.01

### `rank_sample` (~57 tokens)

Rank sample (free)

Free: the top three Bazaar results a buyer agent would see for a task, and your rank if you pass resource.

Input parameters:

- `resource` (string): Your listed resource URL
- `task` (string, required): What a buyer agent is searching for

### `check_fair_offer` (~101 tokens)

Fair Offer check (free)

Free: check any x402 offer's Fair Offer block from outside, without paying. Each of the eight Fair Offer rules comes back verified, declared, contradicted or not claimed. Pass accept_proof (e.g. "sample=attested; price<=listing") to learn whether the offer meets a buyer's requirements.

Input parameters:

- `accept_proof`: Optional Accept-Proof value
- `url` (string, required): Public https URL of the paid endpoint

### `check_offer` (~128 tokens)

Buyer policy check (free)

Free: would a buyer's policy pay this x402 offer? Applies Agoranome's open buyer policy (a price cap, the listing price, no instructions in the listing, and a proof tier: any, sampled or delivered) and returns allowed or refused with the reasons. Nothing is paid or signed.

Input parameters:

- `expected_price_usd`: A quoted price, if any
- `max_price_usd` (number): The buyer's price cap
- `tier` (string): Proof tier: any, sampled or delivered
- `url` (string, required): Public https URL of the paid endpoint

### `agent_payments_weekly` (~107 tokens)

Agent payments weekly (free)

Free: Agoranome Weekly's edition for a week (the newest if week is left out): real demand on Base (payments into the busiest Bazaar sellers with catalog sweeps and self-payments taken out), the Bazaar's sellers, new sellers, price index and Fair Offer share, and x402 SDK downloads, with the method version and how to cite it. CC BY 4.0.

Input parameters:

- `week`: ISO week, e.g. 2026-W44

### `job_status` (~80 tokens)

Job status (free)

Free: a ticket's standing, and its result once the run is done. A slow tool called with ticket=true answers with a job; pass its id here as often as you like. A failed run says why and when it will be tried again; it's owed a result.

Input parameters:

- `job_id` (string, required): The job's id, from the ticket

### `registered_agent_card` (~98 tokens)

Registered agent card (free)

Free: check an ERC-8004 agent on Base from outside, by its id in the Identity Registry: whether its registration file is valid and points back to it, whether its https endpoints answer and their domains list it, whether its x402 offer or A2A agent card passes the lint, and how concentrated its Reputation Registry feedback is. Nothing is paid or written.

Input parameters:

- `agent_id` (integer, required): The agent's id on Base

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/agoranome-agoranome/api#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 75
- 2026-11-17: 75
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 73
- 2026-11-11: 72
- 2026-11-10: 78
- 2026-11-09: 78
- 2026-11-08: 78
- 2026-11-07: 77
- 2026-11-06: 77
- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 67
- 2026-10-28: 66
- 2026-10-27: 66
- 2026-10-26: 66
- 2026-10-25: 66

## Common questions

### What is the Agoranome buyer checks and market data MCP server?

Agoranome buyer checks and market data is an MCP server listed in the public MCP registry as io.github.Agoranome/agoranome. Free tools for agents that pay with x402: the fair pick, a check before paying, buyers' reports. This page covers its hosted endpoint (https://api.agoranome.com/mcp).

### Is the Agoranome buyer checks and market data MCP server safe to use?

Agoranome buyer checks and market data scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Agoranome buyer checks and market data MCP server expose?

Agoranome buyer checks and market data exposes 17 tools: ping, price_position, which_delivers, fair_pick, lint_listing, and 12 more. Their descriptions and schemas cost roughly 3,289 tokens of context every time the server is loaded.

### Does the Agoranome buyer checks and market data MCP server require authentication?

No. We connected to Agoranome buyer checks and market data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Agoranome buyer checks and market data MCP server still maintained?

Agoranome buyer checks and market data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Agoranome buyer checks and market data MCP server?

VerifyMCP ran 13 checks on Agoranome buyer checks and market data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.agoranome.com/mcp
- Repository: https://github.com/Agoranome/fair-offer
- Website: https://agoranome.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/agoranome-agoranome/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/agoranome-agoranome/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/agoranome-agoranome/api.json
- HTML version of this page: https://verifymcp.io/servers/agoranome-agoranome/api
