wham-engine
OfficialRelated Servers
Alternatives to wham-engine
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to call 93 pay-per-call machine-to-machine services spanning web scraping, crypto sentiment, market data, on-chain analytics, social and threat intelligence, vulnerability scanning, and micro-SaaS utilities. Payments are settled in USDC on Arbitrum via the x402 protocol using a wallet header, so no API keys, signups, or billing setup are required.MIT

com.ausca/agent-servicesofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover, pay for, and invoke x402-priced services such as document OCR, document analysis, media transcription, remote browser sessions, and receive-only email inboxes using USDC on Base, with no API keys and receipt-backed results.36MIT- AlicenseNot gradedqualityCmaintenancePay-per-call AI microservices settled in USDC on Base via the x402 (HTTP 402) protocol. 28 tools including web search, summarization, extraction, code review, deep research, crypto safety, sanctions screening and on-chain data — no accounts or API keys.8 npmApache 2.0
- AlicenseAqualityCmaintenanceProvides AI agents with 10 pay-per-call utility tools (QR generation, DNS lookup, OCR, etc.) using USDC on Base via the x402 protocol, with agent's private key never leaving the agent.1135 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to discover and invoke x402-monetized computational engines for media geometry, measurements, JSON hygiene, and ComfyUI preflight audits, with USDC settlement on Base Mainnet.-

warppay402-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to access 28 monetized Web3 developer tools, including web scraping, PDF extraction, smart contract deployment, and cross-chain USDC micropayments via SSE and x402.MIT
TDQS
Scored across 200 tools
Numerous near-duplicate tools exist: validate_jwt_token vs jwt_token_cryptographic_validator, detect_secrets_leak vs secrets_entropy_scanner, strip_prompt_injection vs prompt_injection_jailbreak_classifier, sanitize_sql_query vs sql_ast_sqli_taint_analyzer, verify_cors_headers vs cors_policy_preflight_misconfig_checker. With 200 tools spanning overlapping domains, an agent would frequently be unable to reliably distinguish which tool to call.
Most tools use descriptive snake_case and are readable, but there is a clear split between verb-first names (validate_code_syntax, generate_merkle_proof) and noun-first names (mesh_decimate_quadric_simplifier, pointcloud_las_to_ply_filter). Action verbs are also highly varied (validate, verify, check, audit, inspect, scan), making the pattern less predictable.
200 tools is an extreme over-scoping for any coherent server purpose. Even a general-purpose utility server would struggle to justify this many distinct operations, and the calibration guideline places anything above 50 as a severe mismatch.
Each implied subdomain is shallow despite the massive count: image tools lack crop/rotate, PDF tools lack merge/split, code tools lack formatting/linting, and blockchain tools lack transaction sending. Many tools are one-offs with no surrounding workflow, and the heavy redundancy suggests dead ends rather than a complete surface.