Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sorqen

REMOTE · SORQEN.FLASHODDS.LIVE · SCANNED SEP 21

Sportsbook-derived no-vig fair value with confidence, provenance, and history over REST/MCP.

+3 this week 74 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 635 tokens (~63/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Sorqen MCP server?

Sorqen is a hosted endpoint at https://sorqen.flashodds.live/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 · sorqen.flashodds.live

# add to Claude Code
claude mcp add --transport http ifan6oy-sorqen 'https://sorqen.flashodds.live/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ifan6oy-sorqen": {
      "url": "https://sorqen.flashodds.live/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ifan6oy-sorqen": {
      "type": "http",
      "url": "https://sorqen.flashodds.live/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ifan6oy-sorqen]
url = "https://sorqen.flashodds.live/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ifan6oy-sorqen": {
      "type": "remote",
      "url": "https://sorqen.flashodds.live/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ifan6oy-sorqen --url 'https://sorqen.flashodds.live/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ifan6oy-sorqen:
    url: "https://sorqen.flashodds.live/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ifan6oy-sorqen": {
      "Transport": "http",
      "Url": "https://sorqen.flashodds.live/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ifan6oy-sorqen -t streamable-http -u 'https://sorqen.flashodds.live/mcp'
// mcp.json
{
  "mcpServers": {
    "ifan6oy-sorqen": {
      "type": "http",
      "url": "https://sorqen.flashodds.live/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 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.

  • 14 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.

  • 12 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.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 21 Sept 2026 · Probed https://sorqen.flashodds.live/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=flashodds.live CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 12 Dec 2026 ECDSA 256 ECDSA-SHA256 a8a48d8fc43d0dda0eb5dfe329d950f9
SANs: flashodds.live, *.flashodds.live
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 sorqen.flashodds.live. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
live. present 36322 8 Verified
flashodds.live. 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sorqen.flashodds.live/mcp Verified 200
http (plaintext) http://sorqen.flashodds.live/mcp HTTPS enforced 301 https://sorqen.flashodds.live/mcp
MCP tools · 10 exposed · ~635 tokens

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 →

Tool Tokens
describe_authentication ~30

Explain the discovery/data boundary and how to attach a Sorqen API key. No API key required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

describe_methods ~42

Describe the versioned fair-value method and refusal philosophy. No API key required. Use it to interpret Sorqen numbers; use list_fair_values for current data.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

describe_plans ~33

Describe public plan limits and entitlements. No API key required. Free is authenticated real access, not anonymous data access.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_fair_value ~52

Return one current fair value by canonical outcome id. Requires a Sorqen key. Use when the outcome id is already known; use list_fair_values for discovery.

NameTypeReqDescription
outcome_idstringyes

No output schema declared.

No examples provided.

get_fair_value_history ~59

Return fair-value history for one outcome, bounded by the caller plan. Requires a Sorqen key. Free has no history; Builder and above unlock history windows.

NameTypeReqDescription
daysinteger
outcome_idstringyes

No output schema declared.

No examples provided.

get_plan ~37

Return the caller plan, limits and entitlements. Requires a Sorqen key. Use when a field is locked or a limit is reached.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_settlement_rules ~45

Return Sorqen settlement-context rules and tie prior used by the local client comparison path. Requires a Sorqen key. This is context, not a venue market feed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

grade ~188

Grade a pregame price or probability against Sorqen's fair value at that timestamp, Sorqen Close when available, and the settled result when available. Requires a Sorqen key. Sorqen uses only information that existed at or before observed_at, so the answer carries no look-ahead. Before kickoff the close and result come back as pending and their metrics are null, never zero. `venue` is a label for your own records; Sorqen never fetches it.

NameTypeReqDescription
observed_atstringyesISO 8601 timestamp of when you saw the price. Must be before the scheduled start.
outcome_idstringyes
priceobjectyesThe format is declared, never inferred: 1.91 is decimal odds to one caller and nonsense to another.
venuestringOptional label for where your price came from. Metadata only.

No output schema declared.

No examples provided.

list_fair_values ~101

Return current no-vig sportsbook-consensus probabilities for supported upcoming markets. Requires a Sorqen key. Free keys receive real values within Free limits; evidence is available on paid plans. Use for scanning/filtering; use get_fair_value for one known outcome.

NameTypeReqDescription
cursorstring
leaguearray
limitinteger
market_typearray
min_confidencenumber

No output schema declared.

No examples provided.

list_leagues ~48

List supported league ids, market types and periods. No API key required. Use before a fair-value query when you do not already know the allowed ids; do not use it for live prices.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the Sorqen MCP server?

Sorqen is an MCP server listed in the public MCP registry as io.github.iFan6oy/sorqen. Sportsbook-derived no-vig fair value with confidence, provenance, and history over REST/MCP. This page covers its hosted endpoint (https://sorqen.flashodds.live/mcp).

Is the Sorqen MCP server safe to use?

Sorqen scores 74 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 Sorqen MCP server expose?

Sorqen exposes 10 tools: list_leagues, describe_methods, describe_plans, describe_authentication, list_fair_values, and 5 more. Their descriptions and schemas cost roughly 635 tokens of context every time the server is loaded.

Does the Sorqen MCP server require authentication?

No. We connected to Sorqen without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Sorqen MCP server still maintained?

Sorqen is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.