CrowdCent Challenge
REMOTE · MCP.CROWDCENT.COM
AI agents build, backtest and run ML prediction models: market data, cloud GPUs, live trading.
Available components
Last scanned (16 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
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 1 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 Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2629 tokens (~175/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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 Nov 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.
- 20 Nov 26 0
- Tool “get_performance” rewrote its description, which is the text the model reads security
- “get_performance” added an optional parameter “daily” cosmetic
- “get_performance” added an optional parameter “user” cosmetic
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 +32
- Authorization: fail → unverified ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 13 Nov 26 33
First indexed and scored.
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 Nov 2026 · Probed https://mcp.crowdcent.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.crowdcent.com | CN=WR3,O=Google Trust Services,C=US | 6 Nov 2026 | 4 Feb 2027 | RSA 2048 | SHA256-RSA | cec7e2193ecfb6112a3fd82e7442734 |
| SANs: mcp.crowdcent.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.crowdcent.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| crowdcent.com. | No DS | 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://mcp.crowdcent.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.crowdcent.com/mcp | HTTPS enforced | 302 | https://mcp.crowdcent.com/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 →
blend_simulations ~256
Blend up to 5-50 weighted sleeves (tier-capped: 5 Challenger, 10 Contender, 25 Centurion, 50 Sovereign) into one ensemble book; returns blend stats plus the sleeve correlation matrix. Sizing is the blend's, never a sleeve's: weights shape the blend, and the netted book is sized once by leverage / target_vol.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| leverage | number | – | Gross book as a multiple of equity (default 1.0). |
| oos_days | integer | – | Out-of-sample period, the final N days (default 90, 0 = none); `is_stats` covers the days before, `oos_stats` the test, and `split` echoes the cut. |
| sleeves | array | yes | [{"config": {...} or "config_token": "...", "weight": 1.0, "label": "fast"}, ...]. Low correlation between sleeves is what makes a blend worth deploying. |
| target_vol | number | – | Annualized vol target under `leverage` (0 = off). |
Structured output declared, but exposes no named fields.
No examples provided.
get_challenge_info ~43
Get detailed information about a challenge.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
Structured output declared, but exposes no named fields.
No examples provided.
get_inference_data_info ~68
Get details for one inference period ('current' works).
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| release_date | string | yes | YYYY-MM-DD, or 'current' for the active period. |
Structured output declared, but exposes no named fields.
No examples provided.
get_inference_data_url ~68
Get a signed, time-limited download URL for inference features.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| release_date | string | – | YYYY-MM-DD, or 'current' (default). |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_meta_model_url ~53
Get a signed, time-limited download URL for the consolidated meta-model file.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_performance ~146
Get a member's submission performance, newest first. Every member's scores are public. Percentiles run 0 to 100.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| daily | boolean | – | Instead, return one row per metric and day for the member's pending submissions (the ones still being scored). `is_final` marks the day that becomes the final score. |
| scored_only | boolean | – | Only include submissions that have been scored. |
| slot | – | – | Optional slot filter (1-5). |
| user | – | – | The member's username. Leave empty for your own. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
get_submission ~59
Get details for one of your submissions by id.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| submission_id | integer | yes | The submission id from list_submissions. |
Structured output declared, but exposes no named fields.
No examples provided.
get_training_dataset_info ~64
Get details for one training dataset version.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| version | string | yes | A dataset version such as '1.0', or 'latest'. |
Structured output declared, but exposes no named fields.
No examples provided.
get_training_dataset_url ~87
Get a signed, time-limited download URL for a training dataset. Works everywhere (no local filesystem needed): fetch the URL with any HTTP client.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| version | string | yes | A dataset version such as '1.0', or 'latest'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_all_challenges ~32
List all active CrowdCent challenges. Use this to discover challenge slugs before calling challenge-scoped tools.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_submissions ~61
List your prediction submissions for a challenge.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| period | – | – | Optional filter: 'current' or a YYYY-MM-DD release date. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
list_training_datasets ~45
List all training dataset versions for a challenge.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
run_simulation ~995
Backtest one portfolio config against the live meta-model. The simulator trades the meta-model's published rankings as a long/short portfolio with your chosen construction (cohort sizes, cadence, optimizer, fees, funding). Returns stats split into in-sample (`is_stats`) and out-of-sample (`oos_stats`, the final `oos_days`), a config_token, and a web_url the user can open on crowdcent.com. Config knobs (all optional; omitted knobs use the site's defaults: pred_30d, 40/40, "10t", a $1.5M open-interest floor, 3.5 bps fees and funding on, and the best optimizer the key's tier unlocks — min_var at Contender, with carry_penalty 0.25 at Centurion): - rank_by: "pred_10d" | "pred_30d" | "blend" (Centurion tier) - n_long / n_short: names per leg, 1-100 each - net_exposure: long gross minus short gross, -1 to 1 in 0.01 steps (default 0, dollar-neutral at any leg sizes) - rebalance_days: "1"|"5"|"10"|"30", or tranched "5t"|"10t"|"30t" - optimizer: "equal" | "inv_vol"/"hrp" (Challenger); higher tiers unlock covariance optimizers (Contender) and conviction sizing (Centurion) — the capabilities listing names the keys your tier unlocks - fee_bps: 0-20 bps per side (default 3.5, Hyperliquid taker); include_funding: bool (default true) - signal_lag: 0-14 days; risk_lookback: 10-365 days in 5d steps, 0 = the optimizer's own window (Challenger) - impact_book: 0-1e9 USD gross (0 = off). Contender. Sizing is NOT a config knob: pass `leverage` (0.25-3.0 gross as a multiple of equity, default 1.0) and `target_vol` (0-0.5 annualized, 0 = off, adapts the multiple under that leverage ceiling, never above it) as their own arguments; both Contender. Gross past 6x equity is liquidated (stats.liquidated_on). - hedge_btc: bool and carry_penalty: 0-1.0 (Centurion); lw_shrinkage: bool. Continuous knobs snap to the step the capabilities listing reports (min/max/step per knob). - min_oi / min_volume / min_trades: liquidity floors (USD, USD, count) - meta_construction: how the meta-m…
| Name | Type | Req | Description |
|---|---|---|---|
| benchmark_trials | integer | – | 0-100 random-ranking portfolios to score the signal against. |
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| config | object | yes | Knob dict, e.g. {"n_long": 10, "n_short": 10, "rebalance_days": "10t", "optimizer": "inv_vol", "include_funding": True}. |
| include_curve | boolean | – | Also return the full daily equity series. |
| include_holdings | boolean | – | Also return the current simulated book. |
| leverage | number | – | Gross book as a multiple of equity (default 1.0). |
| oos_days | integer | – | Out-of-sample period, the final N days (default 90, 0 = none); `is_stats` covers the days before, `oos_stats` the test, and `split` echoes the cut. |
| target_vol | number | – | Annualized vol target under `leverage` (0 = off). |
Structured output declared, but exposes no named fields.
No examples provided.
submit_predictions_from_dataframe ~108
Submit predictions from a JSON representation of a dataframe. The dataframe must contain the challenge's required columns (for hyperliquid-ranking: id, pred_10d, pred_30d).
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| df | string | yes | JSON string in the {"column": [values, ...]} orientation. |
| slot | integer | – | Submission slot 1-5. |
Structured output declared, but exposes no named fields.
No examples provided.
sweep_simulations ~351
Grid-search up to your tier's budget (96 configs at Contender, 24 below) of portfolio constructions in one call. IMPORTANT: choose candidates on in-sample numbers (`is_stats`), prefer settings whose neighbors also perform, and read out-of-sample numbers (`oos_stats`) only after choosing: picking on the out-of-sample period makes it in-sample.
| Name | Type | Req | Description |
|---|---|---|---|
| challenge_slug | string | – | Challenge slug, such as hyperliquid-ranking. list_all_challenges gives the slugs. |
| config | object | yes | Base configuration; swept knobs override it. |
| oos_days | integer | – | Out-of-sample period, the final N days (default 90, 0 = none); `is_stats` covers the days before, `oos_stats` the test, and `split` echoes the cut. |
| sweep | object | yes | Sweepable knob -> list of values, e.g. {"n_long": [5, 10, 20], "rebalance_days": ["5t", "10t"]}. Sweepable: n_long, n_short, net_exposure, rebalance_days, optimizer, lw, fee_bps, funding, lag, risk_l… |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the CrowdCent Challenge MCP server?
CrowdCent Challenge is a hosted endpoint at https://mcp.crowdcent.com/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 · mcp.crowdcent.com
claude mcp add --transport http com-crowdcent-challenge 'https://mcp.crowdcent.com/mcp'
What is the CrowdCent Challenge MCP server?
CrowdCent Challenge is an MCP server listed in the public MCP registry as com.crowdcent/challenge. AI agents build, backtest and run ML prediction models: market data, cloud GPUs, live trading. This page covers its hosted endpoint (https://mcp.crowdcent.com/mcp).
Is the CrowdCent Challenge MCP server safe to use?
CrowdCent Challenge scores 67 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 CrowdCent Challenge MCP server expose?
CrowdCent Challenge exposes 15 tools: list_all_challenges, get_challenge_info, list_training_datasets, get_training_dataset_info, get_inference_data_info, and 10 more. Their descriptions and schemas cost roughly 2,436 tokens of context every time the server is loaded.
Does the CrowdCent Challenge MCP server require authentication?
No. We connected to CrowdCent Challenge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CrowdCent Challenge MCP server still maintained?
CrowdCent Challenge is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the CrowdCent Challenge MCP server?
VerifyMCP ran 12 checks on CrowdCent Challenge, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about CrowdCent Challenge: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.