Fresh402 Web Intelligence API
REMOTE · FRESH402.KIRILLLABS.WORKERS.DEV
Web intelligence: free baseline; Check $0.005, Extract $0.01, Smart Diff $0.015 USDC on Base.
Available components
Last scanned (5 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Web Scraping
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability51
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 445 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage68
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 4% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
- Server version: 2.3.0 → 2.4.0 functional
- 15 Oct 26 0
- Server version: 2.2.0 → 2.3.0 functional
- 14 Oct 26 +1
- Schema quality: 372 → 445 ▼ functional
- New tool “fresh402_openapi_contract_diff” functional
- 13 Oct 26 0
- Server version: 2.0.0 → 2.2.0 functional
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 0
- Tool coverage: 0% → 5% ▲ functional
- “fresh402_smart_diff” reworded the description of “watch_id” cosmetic
- 10 Oct 26 +1
- Tool “fresh402_check” rewrote its description, which is the text the model reads security
- Tool “fresh402_register” rewrote its description, which is the text the model reads security
- Schema quality: 187 → 343 ▼ functional
- Server version: 1.1.1 → 2.0.0 functional
- New tool “fresh402_extract” functional
- New tool “fresh402_smart_diff” functional
- 9 Oct 26 53
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://fresh402.kirilllabs.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=kirilllabs.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 62f79823a7dba704e6414e73ea570b29e48 |
| SANs: *.kirilllabs.workers.dev, kirilllabs.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fresh402.kirilllabs.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fresh402.kirilllabs.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://fresh402.kirilllabs.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fresh402_check ~102
Check a persistent watch or URL for changes, with noise filtering, conditional HTTP and a compact deterministic diff. $0.005 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| ignore_json_paths | array | – | – |
| ignore_selectors | array | – | – |
| include_diff | boolean | – | – |
| max_age_seconds | integer | – | – |
| previous_hash | string | – | – |
| selector | string | – | – |
| url | string | – | – |
| watch_id | string | – | – |
No output schema declared.
No examples provided.
fresh402_extract ~106
Extract main text, metadata, headings, links and JSON-LD from a public URL without executing JavaScript. HTML, JSON and text; CSS scoping. $0.01 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| ignore_json_paths | array | – | – |
| ignore_selectors | array | – | – |
| include_links | boolean | – | – |
| include_structured_data | boolean | – | – |
| max_chars | integer | – | – |
| selector | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
fresh402_openapi_contract_diff ~73
Compare a registered public JSON OpenAPI 3.0/3.1 contract against its baseline or previous snapshot. Deterministic structural compatibility evidence; no remote references or LLM.
| Name | Type | Req | Description |
|---|---|---|---|
| compare_to | string | – | – |
| previous_hash | string | – | – |
| watch_id | string | yes | – |
No output schema declared.
No examples provided.
fresh402_register ~62
Create or retrieve a free persistent baseline. Existing registrations never refetch the target. No JavaScript execution.
| Name | Type | Req | Description |
|---|---|---|---|
| ignore_json_paths | array | – | – |
| ignore_selectors | array | – | – |
| selector | string | – | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
fresh402_smart_diff ~102
Compare a watch with its previous Smart Diff snapshot or fixed baseline. JSON Pointer changes, HTML block changes and explained significance rules; deterministic, no LLM. $0.015 USDC.
| Name | Type | Req | Description |
|---|---|---|---|
| compare_to | string | – | – |
| previous_hash | string | – | – |
| watch_id | string | yes | Required ID returned by free fresh402_register or POST /v1/register. Example IDs are illustrative; replace them with a returned watch ID before paying. |
No output schema declared.
No examples provided.
How do I install the Fresh402 Web Intelligence API MCP server?
Fresh402 Web Intelligence API is a hosted endpoint at https://fresh402.kirilllabs.workers.dev/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.
remote · fresh402.kirilllabs.workers.dev
claude mcp add --transport http kirillradchenko96-fresh402 'https://fresh402.kirilllabs.workers.dev/mcp'
What is the Fresh402 Web Intelligence API MCP server?
Fresh402 Web Intelligence API is an MCP server listed in the public MCP registry as io.github.kirillradchenko96/fresh402. Web intelligence: free baseline; Check $0.005, Extract $0.01, Smart Diff $0.015 USDC on Base. This page covers its hosted endpoint (https://fresh402.kirilllabs.workers.dev/mcp).
Is the Fresh402 Web Intelligence API MCP server safe to use?
Fresh402 Web Intelligence API scores 57 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 Fresh402 Web Intelligence API MCP server expose?
Fresh402 Web Intelligence API exposes 5 tools: fresh402_register, fresh402_check, fresh402_extract, fresh402_smart_diff, fresh402_openapi_contract_diff. Their descriptions and schemas cost roughly 445 tokens of context every time the server is loaded.
Does the Fresh402 Web Intelligence API MCP server require authentication?
No. We connected to Fresh402 Web Intelligence API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fresh402 Web Intelligence API MCP server still maintained?
Fresh402 Web Intelligence API is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.