VELQIRIS Market Truth MCP Server
Related Servers
Alternatives to VELQIRIS Market Truth MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server providing on-chain price oracle data from Chainlink and Pyth Network, with tools for latest and historical prices, feed discovery, and staleness flags. No API keys required; uses free public RPCs and Hermes API.7MIT
- AlicenseNot gradedqualityCmaintenanceEd25519-signed market-state receipts for 28 exchanges: is the venue open right now, as a receipt any agent can verify without trusting the operator, fail-closed (unknown is reported as closed). MCP tools: get_market_status, get_market_schedule, list_exchanges, get_payment_options. Free tier 500 calls a day with an instant key; x402 pay-per-call at 0.001 USDC on Base; Builder 99 USDC a monthMIT
- AlicenseNot gradedqualityDmaintenanceReal-time currency exchange rates and crypto prices via MCP. Convert between 60+ fiat currencies and 30+ cryptocurrencies with multi-source failover. No API keys needed for upstream data.7 npmISC
- FlicenseNot gradedqualityCmaintenanceEnables MCP clients to retrieve crypto price quotes, momentum signals, trending coins, and a composite scored market verdict from CoinGecko's free public API.-
- AlicenseNot gradedqualityCmaintenanceReserve Asset Intelligence MCP — live gold/silver prices as ES256K-signed evidence payloads, 80+ RWA token profiles (PAXG, XAUT, BlackRock BUIDL) with issuer LEI, custody, MiCA Art.36 context, and real cryptographic signatures.MIT
- AlicenseNot gradedqualityDmaintenanceCrypto intelligence MCP: 104 tools for market data, ML signals, on-chain analytics, derivatives, and Bittensor subnets. Pay-per-call via x402 USDC on Base/Solana/Algorand/Stellar or $9.99/mo API key.MIT
TDQS
Scored across 2 tools
The two tools target clearly different concerns: one returns cross-venue spot price consensus, the other evaluates a risk regime. There is no plausible scenario where an agent would confuse them, and the failure semantics (fail-closed) are described for each.
Both names use snake_case with a leading verb (get_/verify_) followed by a noun phrase, which is predictable and readable. The only minor deviation is that the verbs differ in style ('get' is retrieval, 'verify' implies validation), but this reflects genuinely different operations rather than inconsistency.
Two tools is thin for a server, though the scope here is deliberately narrow (trustworthy market data primitives). Each tool earns its place, but the surface feels like a partial slice rather than a complete server.
Core operations exist for price consensus and risk regime, but there is no way to discover supported assets or venues, check venue health/freshness, or query historical/stale data. Agents hitting an unsupported asset have no recovery path within the tool set.