Qtcl MCP Server vs MCP Victorialogs

A side-by-side look at the Qtcl MCP Server and MCP Victorialogs MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Qtcl MCP Server logoQtcl MCP ServerMonitoring · Remote HTTP/SSEAgent-native post-quantum blockchain. 11 tools: send, balance, quantum oracle metrics. Flat fee.48FairAuth: not declaredMCP Victorialogs logoMCP VictorialogsMonitoring · Remote HTTP/SSEMCP Server for VictoriaLogs. Provides integration with VictoriaLogs API and documentation63GoodAuth: not declared

Verdict: choose Qtcl MCP Server for monitoring work over a hosted endpoint; choose MCP Victorialogs for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Qtcl MCP Server logoChoose 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.
Explore Qtcl MCP Server

MCP Victorialogs logoChoose MCP Victorialogs when

  • You need dedicated capabilities in the Monitoring domain.
  • You prefer a remote HTTP/SSE transport.
  • You have the keys it needs: VL_INSTANCE_ENTRYPOINT, VL_INSTANCE_BEARER_TOKEN, VL_INSTANCE_HEADERS, MCP_PASSTHROUGH_HEADERS, VL_DEFAULT_TENANT_ID, MCP_SERVER_MODE.
  • You want tools like documentation, facets, field_names.
Explore MCP Victorialogs

Feature & specification comparison

Rows where the two servers differ are marked.

SpecQtcl MCP Server logoQtcl MCP ServerMCP Victorialogs logoMCP Victorialogs
CategoryMonitoringMonitoring
Quality signal48/100 · Fair63/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSERemote HTTP/SSE
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedVL_INSTANCE_ENTRYPOINTVL_INSTANCE_BEARER_TOKENVL_INSTANCE_HEADERSMCP_PASSTHROUGH_HEADERSVL_DEFAULT_TENANT_IDMCP_SERVER_MODE
Verified ownerCommunity listingCommunity listing
GitHub stars0105
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools1113

Tools & capabilities

Qtcl MCP Server tools 11

  • qtcl_create_walletGenerate a new post-quantum wallet address + keypair
  • qtcl_get_balanceCheck confirmed + pending balance for any address
  • qtcl_send_transactionSend QTCL with flat 1-qsat fee. Supports 256-char memo
  • qtcl_get_transactionLook up any transaction by hash
  • qtcl_get_chain_infoBlock height, mempool depth, oracle consensus status
  • qtcl_get_blockBlock by height or hash with quantum coherence metrics
  • qtcl_get_recent_transactionsLast 50 txs, filterable by address
  • qtcl_get_quantum_metricsLive W-state fidelity, entanglement witness, lattice coherence
  • qtcl_get_oracle_registry5 Byzantine consensus oracles — stake, uptime, heartbeat
  • qtcl_get_peersActive P2P peers and topology data
  • qtcl_get_priceLive QTCL/USD from Pyth Network oracle feed

MCP Victorialogs tools 13

  • documentationSearch documentation resources for the given search query, returning the URIs of the resources that match the search criteria sorted by relevance. This tool can help to get context for any VictoriaLogs related question.
  • facetsThe most frequent values per each log field seen in the logs returned by the given <query> on the given [<start> ... <end>] time range. This tool uses `/select/logsql/facets` endpoint of VictoriaLogs API.
  • field_namesGet field names from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field name. This tool uses `/select/logsql/field_names` endpoint of VictoriaLogs API.
  • field_valuesGet unique values for the given <fieldName> field from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field value. This tool uses `/select/logsql/field_values` endpoint of VictoriaLogs API.
  • flagsList of non-default flags (parameters) of the VictoriaLogs instance. This tools uses `/flags` endpoint of VictoriaLogs API.
  • hitsThe number of matching log entries for the given <query> on the given [<start> ... <end>] time range grouped by <step> buckets. The returned results are sorted by time. This tool uses `/select/logsql/hits` endpoint of VictoriaLogs API.
  • queryExecutes LogsQL query expression to search log entries. This tool uses `/select/logsql/query` endpoint of VictoriaLogs API.
  • stats_queryLog stats for the given query at the given timestamp (time) in the format compatible with Prometheus querying API. This tool uses `/select/logsql/stats_query` endpoint of VictoriaLogs API.
  • stats_query_rangeLog stats for the given query on the given [start ... end] time range with the given step interval. The stats is returned in the format compatible with Prometheus querying API. This tool uses `/select/logsql/stats_query_range` endpoint of VictoriaLogs API.
  • stream_field_namesGet log stream field names from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field name.. This tool uses `/select/logsql/stream_field_names` endpoint of VictoriaLogs API.
  • stream_field_valuesGet unique values for the given <fieldName> field from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every field value. This tool uses `/select/logsql/stream_field_values` endpoint of VictoriaLogs API.
  • stream_idsGet _stream_id values for the log streams from results of the given <query> on the given [<start> ... <end>] time range. The response also contains the number of log results per every _stream_id. This tool uses `/select/logsql/stream_ids` endpoint of VictoriaLogs API.
  • +1 more on the listing page

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.

Qtcl MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "qtcl-mcp-server": {
      "url": "https://qtcl-blockchain.koyeb.app/mcp/sse"
    }
  }
}

MCP Victorialogs

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-victorialogs": {
      "url": "https://play-vmlogs-mcp.victoriametrics.com/mcp"
    }
  }
}

Frequently asked questions

Qtcl MCP Server is categorized under Monitoring and uses a remote HTTP/SSE transport. MCP Victorialogs belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Qtcl MCP Server for monitoring work and MCP Victorialogs 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.

Qtcl MCP Server has no declared pricing — check the project's own site. MCP Victorialogs 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 qtcl-mcp-server and mcp-victorialogs as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Qtcl MCP Server has a quality signal of 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. MCP Victorialogs has 63/100 (Good) with 1 views, 0 installs and 105 GitHub stars.