QSIG Intelligence
REMOTE · X402.QSIG.NET · SCANNED SEP 28
Geopolitical risk score with a published kill criterion. Measured state, not forecasts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 316 tokens (~105/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the QSIG Intelligence MCP server?
QSIG Intelligence is a hosted endpoint at https://x402.qsig.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · x402.qsig.net
claude mcp add --transport http net-qsig-x402-mcp 'https://x402.qsig.net/mcp'
{
"mcpServers": {
"net-qsig-x402-mcp": {
"url": "https://x402.qsig.net/mcp"
}
}
} {
"servers": {
"net-qsig-x402-mcp": {
"type": "http",
"url": "https://x402.qsig.net/mcp"
}
}
} [mcp_servers.net-qsig-x402-mcp] url = "https://x402.qsig.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-qsig-x402-mcp": {
"type": "remote",
"url": "https://x402.qsig.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-qsig-x402-mcp --url 'https://x402.qsig.net/mcp' --transport streamable-http
mcp_servers:
net-qsig-x402-mcp:
url: "https://x402.qsig.net/mcp" {
"McpServers": {
"net-qsig-x402-mcp": {
"Transport": "http",
"Url": "https://x402.qsig.net/mcp"
}
}
} assistant mcp add net-qsig-x402-mcp -t streamable-http -u 'https://x402.qsig.net/mcp'
{
"mcpServers": {
"net-qsig-x402-mcp": {
"type": "http",
"url": "https://x402.qsig.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −2
- Tool “get_georisk” rewrote its description, which is the text the model reads security
- Schema quality: 69 → 105 ▼ functional
- First check of Tool coverage: 0 functional
- Schema quality: excellent → good functional
- “get_georisk” added an optional parameter “as_of” cosmetic
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://x402.qsig.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=qsig.net | CN=WE1,O=Google Trust Services,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 56cb1c2901515e650ea21fa33fa67a89 |
| SANs: qsig.net, *.qsig.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402.qsig.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| qsig.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402.qsig.net/mcp | Verified | 200 | |
| http (plaintext) | http://x402.qsig.net/mcp | HTTPS enforced | 301 | https://x402.qsig.net/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_georisk ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_method ~35
Free. How the georisk score is built, what it does and does not claim, pricing, and the payment network.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_track_record ~72
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the QSIG Intelligence MCP server?
QSIG Intelligence is an MCP server listed in the public MCP registry as net.qsig.x402/mcp. Geopolitical risk score with a published kill criterion. Measured state, not forecasts. This page covers its hosted endpoint (https://x402.qsig.net/mcp).
Is the QSIG Intelligence MCP server safe to use?
QSIG Intelligence scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the QSIG Intelligence MCP server expose?
QSIG Intelligence exposes 3 tools: get_georisk, get_track_record, get_method. Their descriptions and schemas cost roughly 316 tokens of context every time the server is loaded.
Does the QSIG Intelligence MCP server require authentication?
No. We connected to QSIG Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the QSIG Intelligence MCP server still maintained?
QSIG Intelligence is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.