FractalAI MCP Server
Related Servers
Alternatives to FractalAI MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP 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
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to access pay-per-call onchain and URL safety APIs over MCP, covering transaction explanations, token approval checks, address inspection, contract risk heuristics, URL safety, gas snapshots, ENS resolution, calldata decoding, and wallet portfolio data. Payments are handled per call in USDC on Base via x402, with no signup or API key required.1MIT
- FlicenseNot gradedqualityDmaintenanceProduction-grade Model Context Protocol (MCP) server delivering paywalled Web3 micro-services powered by autonomous x402 payment challenges on Base Mainnet.-
- AlicenseNot gradedqualityDmaintenanceMCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.MIT

gatefareio/mcp-serverofficial
AlicenseAqualityDmaintenanceMarketplace MCP for paid HTTP APIs. Pay per call in USDC on Base via the open x402 standard — non-custodial. 13 tools for discovery, buying, and publishing APIs.752 npm2MIT- FlicenseAqualityCmaintenanceMCP server for a live x402 payment gateway on Base (USDC). Lets AI agents discover, preview for free, then pay per call — with prepaid gasless payments, signed receipts, and delta delivery.7-
TDQS
Scored across 5 tools
Three tools (seal_provenance, pqc_sign, attest_decision) all produce a paid ML-DSA-65 signature, distinguished only by what is being signed (content, arbitrary bytes, agent decision). The descriptions do work to separate them, but the boundaries are conceptual rather than structural, and an agent could easily reach for pqc_sign when seal_provenance is intended.
All names use snake_case consistently, which is the important part. The patterns mix verb_noun (seal_provenance, verify_proof, attest_decision) with prefix-style names (x402_checkout, pqc_sign), a minor but noticeable deviation.
Five tools is a well-scoped surface for a narrow signing/attestation service: one payment discovery tool, one free verifier, and three seal/sign operations. Nothing feels padded or missing at the count level.
signature-level verification exists via verify_proof, but there is no tool to re-verify a seal_provenance record or an attest_decision receipt end-to-end (drand round, on-chain anchor, Black Box chain), despite both being advertised as re-verifiable. An agent that seals something has no symmetric read/verify path for that artifact.