Skip to content

QSIG Intelligence MCP server

net.qsig.x402/mcpx402.qsig.netstreamable-httpv1.2.0Scanned

Geopolitical risk, theme board and point-in-time gold macro context for agents, paid via x402

7 tools: 7 only read.

Tools: 0 delete, 0 irreversible, 0 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the QSIG Intelligence MCP server can do

The QSIG Intelligence MCP server is published by x402.qsig.net, a domain the MCP Registry verified. It has 7 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Only reads 7Show 7 read-only tools
  • get_geo_themesQSIG geopolitical theme board.No findings

    Why it is in this group

    • The name "get_geo_themes" says "get": a word for reading.
    Description, as the server wrote it
    QSIG geopolitical theme board. For each theme (HORMUZ_OIL, IRAN, LEVANT, RUSSIA_UKRAINE, CHINA_TAIWAN, FED, CRYPTO): the Polymarket crowd stress index and its 24h / 7d change on the same markets, tracked whale positions and 24h flows (aggregates only, no wallet addresses), the news-event count against its same-window baseline, and the top 3 markets. theme is an optional key; omit it for all themes. as_of is an optional ISO 8601 UTC timestamp such as "2026-10-05T12:00:00Z"; the latest hourly snapshot at or before it is returned. History begins 2026-09-29. Themes with coverage.sufficient = false are returned but should not be read as meaningful. stress_index is a direction and change gauge, not a probability: read change_24h and change_7d. This is a MEASURED STATE, not a forecast. Paid route: $0.02 USDC via x402. Call list_geo_themes first (free) to see keys and coverage before paying.
  • get_georiskQSIG geopolitical risk score (0-100, higher = more risk), with 24h change, 30/90-day percentile rank, regime label and event count.No findings

    Why it is in this group

    • The name "get_georisk" says "get": a word for reading.
    Description, as the server wrote it
    QSIG geopolitical risk score (0-100, higher = more risk), with 24h change, 30/90-day percentile rank, regime label and event count. Returns the current score, or a historical one if as_of is given. as_of is an ISO 8601 UTC timestamp such as "2026-09-15T12:00:00Z"; the most recent observation at or before it is returned, with match_offset_seconds showing how far back the match was. History begins 2026-09-09 and is sampled every ~15 minutes, so earlier timestamps return an error rather than a score. This is a MEASURED STATE, not a forecast. No directional or predictive claim is made. Paid route: $0.02 USDC via x402. Call get_track_record first if you want to evaluate the service before paying.
  • get_gold_contextQSIG gold macro context in one call, point-in-time correct.No findings

    Why it is in this group

    • The name "get_gold_context" says "get": a word for reading.
    Description, as the server wrote it
    QSIG gold macro context in one call, point-in-time correct. Returns: regime (trend-state label: ranging, trending or mixed, with since and hours_in_regime), positioning_cot (CFTC managed-money and commercials net, weekly change, share of open interest, extreme flag, with report_date and the official released_at), rates (FRED 10-year real yield and breakeven inflation with 30-day change), geo (QSIG GeoRisk score and gold-linked Polymarket theme stress) and analogs (the 5 most similar past gold episodes and what followed them over 24h and 72h). as_of is an optional ISO 8601 UTC timestamp such as "2026-09-01T12:00:00Z". The hourly snapshot at or before it is returned AS IT WAS KNOWABLE THEN: a COT report counts only after its Friday release, analogs use a 7-day embargo so every outcome had closed. Use it for backtests without look-ahead. History begins 2026-07-14. asset accepts only "gold" in v1. Every block carries status (ok, stale or missing) and knowable_at. recorded=true rows were written live; recorded=false rows were filled from stored history. Analog outcomes are history, not a forecast. This is a MEASURED STATE, not a forecast. No prices, no direction. Paid route: $0.02 USDC via x402. Call get_gold_context_fields first (free) for field definitions and the available history range.
  • get_gold_context_fieldsFree.No findings

    Why it is in this group

    • The name "get_gold_context_fields" says "get": a word for reading.
    Description, as the server wrote it
    Free. Field definitions, units, knowability rules and the available history range (earliest, latest, row counts) for get_gold_context. Use it to decide whether a paid call is worth making.
  • get_methodFree.No findings

    Why it is in this group

    • The name "get_method" says "get": a word for reading.
    Description, as the server wrote it
    Free. What QSIG sells - the georisk score, the geopolitical theme board (get_geo_themes) and the point-in-time gold macro context (get_gold_context) - what each does and does not claim, pricing, and the payment network.
  • get_track_recordFree.No findings

    Why it is in this group

    • The name "get_track_record" says "get": a word for reading.
    Description, as the server wrote it
    Free. QSIG's published validation policy: which products are live, what validation each carries, and which models were KILLED for failing the pre-registered criterion (walk-forward AUC < 0.55), with reasons. Use this to judge whether the paid data is worth buying.
  • list_geo_themesFree.No findings

    Why it is in this group

    • The name "list_geo_themes" says "list": a word for reading.
    Description, as the server wrote it
    Free. Theme keys, labels, linked assets, coverage (qualifying markets, whale USD held, sufficient flag), method version and field notes for get_geo_themes. Use it to decide whether a paid call is worth making.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
0
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 1 changed.+2 added~1 changedView diff

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http x402 https://x402.qsig.net/mcp
claude mcp add --transport http x402 https://x402.qsig.net/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__x402__get_georisk",
      "mcp__x402__get_geo_themes",
      "mcp__x402__list_geo_themes",
      "mcp__x402__get_track_record",
      "mcp__x402__get_gold_context",
      "mcp__x402__get_gold_context_fields",
      "mcp__x402__get_method"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as x402. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/net.qsig.x402/mcp/verify?hash=2a94c46f7de460c03b48ef0fd139b5a38acab3045e484b8410be68a5eca20198" | jq -e '.changed == false'

Pinned hash 2a94c46f7de4, from Nov 9, 2026, 11:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/net.qsig.x402/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for net.qsig.x402/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/net.qsig.x402/mcp.svg)](https://radar.anlyon.com/servers/net.qsig.x402/mcp)

Source: MCP Registry. Synced Oct 26, 2026, 15:18 UTC.

QSIG Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the QSIG Intelligence MCP server safe?

No scan can promise that. What its definitions show: 7 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the QSIG Intelligence MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the QSIG Intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the QSIG Intelligence MCP server have?

7 tools: 7 read. get_georisk, get_geo_themes, list_geo_themes, get_track_record, get_gold_context, get_gold_context_fields and get_method.

Does the QSIG Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the QSIG Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the QSIG Intelligence MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 26, 2026. Every change is on this page and in its Atom feed.