Agent Data Tools
Related Servers
Alternatives to Agent Data Tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenance62 real-time data tools for AI agents via MCP. Finance, crypto, FMCSA, sanctions, courts, weather, vehicles, cybersecurity. One bearer token, one bill. Free tier available.MIT
- FlicenseNot gradedqualityCmaintenancePay-per-use tool marketplace for AI agents. Search, price-check, and call APIs via MCP.-
- AlicenseNot gradedqualityDmaintenanceMulti-tool MCP server for AI agents with 29 tools across web scraping, SEO analysis, screenshot and PDF generation, domain intelligence, content extraction, multi-chain EVM blockchain queries, and security toolkit. Free tier available with no auth required.50 npm1MIT
- AlicenseNot gradedqualityDmaintenanceMonetizable AI agent tools - document parsing, text analysis, code generation, security scanning, format conversion, and more. 8 tools with HTTP API and MCP protocol support.MIT
- AlicenseNot gradedqualityDmaintenance55+ pay-per-call tools for AI agents over MCP: live telemetry, blockchain/on-chain checks, environmental, transit, finance, and network utilities. No API key or signup — agents pay per request with x402 USDC micropayments (Base and Solana).MIT
- AlicenseAqualityCmaintenanceMCP server exposing 43 pay-per-call x402 tools (USDC on Base) for AI agents: validation, data lookup and utility APIs. No API key needed.59MIT
TDQS
Scored across 3 tools
The three tools map to a clean discovery → inspection → execution pipeline: find_tool locates a tool by description, tool_details returns its schema and pricing, and call_tool executes it. There is no overlap in purpose, and the descriptions explicitly tell the agent the order to use them in.
find_tool and call_tool follow a clear verb_noun snake_case pattern, and tool_details is close but uses a noun phrase rather than a verb. This is a minor deviation within an otherwise predictable three-name set.
Three meta-tools are exactly the right surface for proxying a 698-tool catalog; adding per-tool wrappers would be unmanageable. Each tool earns its place and the set stays minimal without being thin.
The gateway covers the full lifecycle an agent needs: search, schema/pricing lookup, and invocation with a max_price guard. Minor gaps exist (e.g. no browsing/listing the catalog by category, capped at ten results, no batch invocation), but these are workarounds rather than dead ends.