Skip to main content
Glama
Sign In
VEYA MCP

VEYA MCP

Official
by veyanet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to VEYA MCP

No user-submitted related servers found.

    Related Servers

    • tool-mcp-server

      maple-awa
      A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server exposing 58 online tools (crypto, data, image, text, etc.) and workflow execution, enabling MCP clients like Claude Desktop to invoke them via natural language.
      58
      5 npm
      MIT

    • Stratly Town Square

      glitch105106
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables stdio-only MCP clients to reach an agent-native venue where autonomous agents chat in rooms, post and team up on problems, create and claim bounties (first claim wins), search all content, and pull deterministic digests, with an optional API key unlocking mutating tools and free read-only access otherwise.
      MIT
    • x402-mcp

      x402-mcpofficial

      x402node
      A
      license
      C
      quality
      D
      maintenance
      MCP server bringing 100+ x402-paid APIs to AI agents (Claude, Cursor, MCP-aware clients). Auto-discovers tools from CDP Bazaar; handles USDC micropayments on Base.
      100
      60 npm
      1
      MIT

    • AmanChain MCP Gateway

      gitajhd
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides 59 pay-per-call AI tools covering crypto prices and audits, market and whale data, LLM chat, image generation, web search/fetch/summarize, and utility services, with automatic x402 USDC-on-Base payments and on-chain receipts. It works with Claude Code/Desktop, Cursor, and other MCP clients without API keys or subscriptions.
      51 npm
      MIT

    • XAF Shadow Node

      chengganping-ship-it
      A
      license
      Not graded
      quality
      C
      maintenance
      A stateless, anonymous MCP edge node exposing three paid JSON-RPC tools on Cloudflare Workers: digital-asset rights pre-check, C2C lead sniffing, and portfolio valuation. Requests are metered per call through an x402 testnet paywall (Base Sepolia / Polygon Amoy) with no IP, user-agent, or persistent storage.
      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

    C2.7/5.0

    Scored across 51 tools

    Disambiguation3/5

    Many tools are clearly distinct, but several clusters overlap heavily: four verification tools (verify_transaction, verify_commitment_onchain, commitment_exists, verify_proof_api), multiple proof/commitment writers (prove, anchor_proof, store_commitment, attest_execution), and duplicate consensus tools. Descriptions clarify contexts like public API, on-chain, and wallet-signed, but misselection risk remains.

    Naming Consistency5/5

    All 51 tools use the veya_ prefix and snake_case, with predictable verb_noun patterns such as list/get/create/register/verify. Even the deprecated client_run_consensus follows the same convention, so naming is highly consistent.

    Tool Count1/5

    51 tools far exceeds the 3-15 sweet spot and the 25+ 'too many' threshold. Deprecated, redundant, and niche operations inflate the surface, making this an extreme tool count for an MCP server even given the broad protocol scope.

    Completeness4/5

    The surface covers public registry, on-chain reads/writes, PQ crypto, environments, agents, memory, proofs, and policy routing. Some lifecycle gaps exist (no update/delete for agents or environments, no memory update, limited API key management), but most workflows have a path.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources