Should my agent depend on the MCP server com.blixtworks.www/tools?

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

Blixtworks

com.blixtworks.www/tools

63 pay-per-call tools for agents: vision, text, data, web, blockchain. USDC on Base via x402.

— the operator's own registry description reported

Publisher com.blixtworks.www · first seen 2026-08-12 · endpoint https://www.blixtworks.com/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.483 (moderate). 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

latency352 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools68

vs populationhigh

capabilities1

harnessB

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_0d8110c9b0602848222927a4 · 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

address_validate base64 caption case_convert categorize check_credit color_convert cron_parse csv_to_json currency_convert date_diff diff distance dns email_validate embed ens_resolve exif gas_price hash hmac how_to_pay http_headers iban_validate image_crop image_info image_palette image_placeholder image_resize image_transform ip_lookup json_format json_query json_to_csv jwt_decode language_detect list_tools lorem luhn_validate markdown_to_html md metadata number_base ocr pdf percentage phone_parse qr redeem_payment regex robots_check rss_parse sitemap_parse slugify ssl_check text_stats timestamp token_info try_sample tx_lookup unit_convert url_expand uuid wallet_balance whois word_frequency xml_to_json yaml_convert

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 B — usable, with rough edges.

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

68 of 68 tools graded · 68 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.0.0

server version blixtworks

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:57:58Z	ok_tools	200	352	2025-06-18
2026-08-12T05:33:14Z	ok_tools	200	162	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/com.blixtworks.www/tools.svg)](https://robinsaige.com/s/com.blixtworks.www/tools)

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