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

Fresh402 Agent Intelligence

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

Live, handshake completed · latest check

As JSON

Detects web page changes and inspects Base smart contract code, storage and events.

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

Placed in Watch pages for changes: Detect changes to web pages, prices and public sources, with diffs and alerts.

https://api.fresh402.com/mcp MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person. See 2 endpoints from fresh402.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, latest573 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

fresh402_checkfresh402_contract_watchfresh402_extractfresh402_openapi_contract_difffresh402_registerfresh402_smart_difffresh402_token_factsfresh402_wallet_watch

Tools
8
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
tools
Transports
streamable-http

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

Calls it declares

  • fresh402_register url* selector ignore_selectors ignore_json_paths html_attributes
  • fresh402_check url watch_id selector ignore_selectors ignore_json_paths html_attributes previous_hash max_age_seconds include_diff
  • fresh402_extract url* selector ignore_selectors ignore_json_paths feed_mode json_pointer json_pointers max_chars include_links include_structured_data
  • fresh402_smart_diff watch_id* compare_to previous_hash json_array_keys
  • fresh402_openapi_contract_diff watch_id* compare_to previous_hash
  • fresh402_contract_watch chain_id* address* block previous_snapshot slots reads event_topics events_from_block
  • fresh402_wallet_watch chain_id* block address* tokens* cursor from_block max_blocks chunk_size
  • fresh402_token_facts chain_id* address* block categories

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: Web access and automation / Website analysis / Watch pages for changes (primary); Financial and economic data / Crypto and on-chain data / Read blockchain data. 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:MIA		 Live, handshake completed HTTP 200 573 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_24a3cec6ef384bf6