Skip to main content
Glama
bjyoe2016

dyoe-agent-tools-mcp

by bjyoe2016
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to dyoe-agent-tools-mcp

No user-submitted related servers found.

    Related Servers

    • x402tools MCP Server

      acrylicfiddle
      A
      license
      A
      quality
      C
      maintenance
      Provides 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.
      11
      23 npm
      MIT

    • agentpay

      ronaldanton
      A
      license
      Not graded
      quality
      C
      maintenance
      Pay-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.
      5 npm
      Apache 2.0
    • @connskill/mcp-growth-services by CONN-SKILL

      @connskill/mcp-growth-servicesofficial

      CONN-SKILL
      A
      license
      Not graded
      quality
      B
      maintenance
      Pay-per-call access to SEO and SERP data, keyword research, backlink and site audits, local business search, SMS verification, social marketing, EU-hosted LLM inference, and read-only on-chain calls. No signup and no API key: agents pay per request in USDC on Base via x402.
      54 npm
      MIT

    • CorteX402

      Ooak21
      A
      license
      A
      quality
      D
      maintenance
      Pay-per-call x402 data products on Base mainnet — sanctions screening, aviation weather, mortgage rates, US property dossier, title chain, wallet balance, and agent session auth. Every call settles in USDC with an on-chain receipt, no accounts or API keys.
      7
      40 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 16 tools

    Disambiguation4/5

    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 Consistency3/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources