dyoe-agent-tools-mcp
Related Servers
Alternatives to dyoe-agent-tools-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityDmaintenanceEnables AI agents to call 50+ pay-per-request tools covering onchain and crypto data, web research, security, compliance screening, business intelligence, and infrastructure checks. Payments settle per call in USDC on Base through the x402 protocol with no accounts, API keys, or subscriptions, and the first call is free for new wallets.MIT- AlicenseAqualityAmaintenancePay-per-call data and tools for AI agents over x402, by UnyKorn. 360 endpoints: DeFi and market data, multi-chain wallet reads, wallet and token risk signals, SEC filings, web and domain intel, and AI text tools. Settled per call in USDC on Base ($0.001-$0.25). No API keys or subscriptions; unpaid calls return the exact quote first.221MIT
- 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
- 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

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- FlicenseNot gradedqualityDmaintenancePay-per-use AI security and research tools for autonomous agents on Base, enabling honeypot detection, risk assessment, wallet analysis, and yield optimization via the x402 protocol.1-
TDQS
Scored across 16 tools
Tools have distinct purposes overall, with crypto, web extraction, trust, and general utilities clearly separated. Some overlap exists among trust tools (trust_check vs merchant_trust vs site_audit), but descriptions sufficiently differentiate them.
Naming uses snake_case but conventions vary: many tools have prefix patterns (crypto_, extract_) while others mix noun_verb (guardian_approve) or have inconsistent suffixes (intel_dossier vs token_intel). No strong uniform pattern.
16 tools is slightly above the typical well-scoped range but still acceptable. The broad scope covering crypto, web, trust, weather, wiki, etc. justifies the count, though it feels slightly heavy for a coherent server.
The tool set covers many common agent needs but lacks a focused domain. Gaps are unclear because it's a random collection; it doesn't provide complete CRUD for any specific area. Incompleteness is notable for a general toolkit missing obvious utilities like file handling or email.