Should my agent depend on the MCP server dev.weblens/weblens?

Verdict: allow — rich-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

WebLens

dev.weblens/weblens

Scrape, crawl, map and extract the web. Pay per call in USDC, no account or API key.

— the operator's own registry description reported

Publisher dev.weblens · first seen 2026-08-12 · endpoint https://api.weblens.dev/mcp

allow

verdict

rich-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-solo — safe to depend on

Cluster rich-solo · distinctiveness 0.349 (typical). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency241 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools36

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_cde1dc6b1f0773a9ddf91365 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

answer_question batch_fetch compare_urls crawl_site deep_research detect_tech domain_intel extract_data extract_pdf fetch_resilient fetch_webpage fetch_webpage_pro get_contents intel_company intel_competitive intel_market intel_site_audit map_site memory_set monitor_create package_intel preview_endpoint project_due_diligence research screenshot search_autocomplete search_discussions search_images search_news search_places search_scholar search_shopping search_trends search_web smart_extract youtube_transcript

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	36/36	✓
has a description	36/36	✓
description is substantive	36/36	✓
parameters are typed	35/36	35/36
parameters are described	36/36	✓

36 of 36 tools graded · 36 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

2.1.0

server version weblens

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:46Z	ok_tools	200	241	2025-06-18
2026-08-12T05:33:59Z	ok_tools	200	282	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/dev.weblens/weblens.svg)](https://robinsaige.com/s/dev.weblens/weblens)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview