TensorFeed x402 Base Reader vs Qtcl MCP Server
A side-by-side look at the TensorFeed x402 Base Reader and Qtcl MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose TensorFeed x402 Base Reader for monitoring work as a local process; choose Qtcl MCP Server for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose TensorFeed x402 Base Reader when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TENSORFEED_RPC_URL. - You want tools like
balance, usdc_balance, block_number.
Choose Qtcl MCP Server when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
qtcl_create_wallet, qtcl_get_balance, qtcl_send_transaction.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 53/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | TENSORFEED_RPC_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 15 | 11 |
| Full listing | View TensorFeed x402 Base Reader | View Qtcl MCP Server |
Tools & capabilities
TensorFeed x402 Base Reader tools 15
balanceNative ETH balance for an addressusdc_balanceUSDC (Circle native bridged) balance for an addressblock_numberLatest Base block numberget_tx_receiptFull tx receipt with status, gas, and logs summarycallRead-only contract call (eth_call, never broadcasts)recent_transfersUSDC Transfer events involving an address over N blocksverify_x402_settlementGiven a tx hash, expected recipient, and expected USDC amount, returns a structured verdict on whether the on-chain Transfer event matches.parse_x402_manifestFetches `https://{domain}/.well-known/x402.json`, returns the structured manifest.usdc_recent_payments_toUSDC transfers TO an address over N blocks; the merchant-side view.probe_x402_endpointProbes any https URL and reports whether it returns a canonical x402-paid 402 response with `accepts[]`.decode_x402_payment_payloadOffline decode of a base64 `X-PAYMENT` header (Coinbase x402 V2): returns scheme, network, version, EIP-3009 authorization, signature.verify_afta_federationCalls TensorFeed's AFTA certification endpoint for a domain, returns a scored checklist.- +3 more on the listing page
Qtcl MCP Server tools 11
qtcl_create_walletGenerate a new post-quantum wallet address + keypairqtcl_get_balanceCheck confirmed + pending balance for any addressqtcl_send_transactionSend QTCL with flat 1-qsat fee. Supports 256-char memoqtcl_get_transactionLook up any transaction by hashqtcl_get_chain_infoBlock height, mempool depth, oracle consensus statusqtcl_get_blockBlock by height or hash with quantum coherence metricsqtcl_get_recent_transactionsLast 50 txs, filterable by addressqtcl_get_quantum_metricsLive W-state fidelity, entanglement witness, lattice coherenceqtcl_get_oracle_registry5 Byzantine consensus oracles — stake, uptime, heartbeatqtcl_get_peersActive P2P peers and topology dataqtcl_get_priceLive QTCL/USD from Pyth Network oracle feed
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
TensorFeed x402 Base Reader
{
"mcpServers": {
"tensorfeed-x402-base-reader": {
"command": "npx",
"args": [
"-y",
"@tensorfeed/x402-base-mcp"
],
"env": {
"TENSORFEED_RPC_URL": "YOUR_TENSORFEED_RPC_URL_HERE"
}
}
}
}
Qtcl MCP Server
{
"mcpServers": {
"qtcl-mcp-server": {
"url": "https://qtcl-blockchain.koyeb.app/mcp/sse"
}
}
}
Frequently asked questions
TensorFeed x402 Base Reader is categorized under Monitoring and uses a local stdio subprocess. Qtcl MCP Server belongs to Monitoring and uses a remote HTTP/SSE transport. Pick TensorFeed x402 Base Reader for monitoring work and Qtcl MCP Server for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
TensorFeed x402 Base Reader has no declared pricing — check the project's own site. Qtcl MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add tensorfeed-x402-base-reader and qtcl-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TensorFeed x402 Base Reader has a quality signal of 53/100 (Good) with 0 views, 0 installs and 2 GitHub stars. Qtcl MCP Server has 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.