Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory
Menu

A.U.G.U.R Foresight · Wallets & Risk

MCP server · augur-trade.com · found in a public list · checked since 2026-10-30

Live, handshake completed · latest check

As JSON

Screens crypto tokens and addresses for risk and validates address formats.

Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means

Placed in Check a token before trading: Check a token address for rug-pull, honeypot, tax and holder-concentration risks.

https://augur-trade.com/foresight/mcp/risk MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person. See 16 endpoints from augur-trade.com.

Our checks

An unpaid request daily, from eastern North America

Last 1 checks, oldest to newest; room for 29 more

1 passed, 0 failed, 29 not run.

Passed, 30 daysshort history1 of 1 run
Checks missed0in 30 days
Response, latest62 mswhole handshake
Scheduledailyset by usage; rule below
Checked since2026-10-30under 1 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hourssince 2026-10-3010——————
7 dayssince 2026-10-3010——————
30 dayssince 2026-10-3010——————

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Tools listed by the server

address_checkbitcoin_networkcounterparty_checkens_resolveerc20_infoevm_addressevm_token_securityevm_txlaunch_scanpricesolana_networktoken_risktx_explainvuln_checkwallet_holdings

Tools
15
This list since
2026-10-30
First listed to us
2026-10-30
List changes, 90 days
0

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check
Nothing asked
Stated
not stated
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol
MCP 2025-06-18
Capabilities
promptsresourcestools
Transports
streamable-http

As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions

Calls it declares

  • token_risk mint* → mint found name symbol price_usd
  • launch_scan mint* → mint symbol score verdict positives
  • counterparty_check wallet* → wallet risk_score level reasons launches
  • price mints* → prices source
  • wallet_holdings wallet* → wallet sol sol_usd tokens_usd total_usd
  • tx_explain signature* → found signature slot time status
  • evm_token_security token* chain → found chain token name symbol
  • evm_address address* chain → address ens_name total_native_usd chains_checked chains
  • erc20_info token* wallet chain → found chain token name symbol
  • evm_tx hash* chain → found chain hash status block
  • ens_resolve query* → found name address records app
  • solana_network → tps_total tps_non_vote avg_slot_ms slot block_height

From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Financial and economic data / Crypto and on-chain data / Token, contract and wallet risk checks / Check a token before trading (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-30. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:EWR		 Live, handshake completed HTTP 200 62 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
  • Limited evidence: monitored for under 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_35fe8959a64acd67