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.

PropScorer

REMOTE · MCP.PROPSCORER.COM · SCANNED SEP 20

Read-only MCP tools for prop firm scores, comparisons, payouts, deals, and rules.

+3 this week 73 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 Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 783 tokens (~71/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the PropScorer MCP server?

PropScorer is a hosted endpoint at https://mcp.propscorer.com/, 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.propscorer.com

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

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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 13 Sept 26 +1

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

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

  • 8 Sept 26 +1

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

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 20 Sept 2026 · Probed https://mcp.propscorer.com

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.propscorer.com CN=YR2,O=Let's Encrypt,C=US 28 Aug 2026 26 Nov 2026 RSA 2048 SHA256-RSA 61fa7a5e6ea0aeacf74a629789015076d90
SANs: mcp.propscorer.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.propscorer.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
propscorer.com. 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=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.propscorer.com Verified 200
http (plaintext) http://mcp.propscorer.com HTTPS enforced 308 https://mcp.propscorer.com/
MCP tools · 11 exposed · ~783 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
ask_propfirm_question ~122

Answer a complex prop firm question with PropScorer live data, KB-backed source context, citations, and freshness/debug metadata. Use for multi-firm comparisons or nuanced rules questions; use get_firm_score first for a simple single-firm score lookup.

NameTypeReqDescription
firm_slugstringOptional firm slug to restrict retrieval.
include_raw_sourcesbooleanInclude retrieved source excerpts for audit/debug use.
limitnumber
questionstringyesQuestion about prop firm rules, pricing, payouts, terms, restrictions, or comparisons.

No output schema declared.

No examples provided.

compare_firm_rules ~86

Retrieve KB-backed rule excerpts for multiple firms so an agent can compare drawdown, payouts, consistency, news trading, and prohibited practices.

NameTypeReqDescription
limit_per_firmnumber
questionstringOptional comparison focus, for example news trading, drawdown, payouts, EAs, copy trading.
slugsarrayyesFirm slugs to compare.

No output schema declared.

No examples provided.

compare_firms ~35

Compare several prop firms side by side using PropScorer metrics.

NameTypeReqDescription
slugsarrayyesFirm slugs to compare.

No output schema declared.

No examples provided.

find_firms_by_rules ~60

Search the KB for firms matching a rule preference, such as static drawdown, news trading allowed, daily payouts, or no consistency rule.

NameTypeReqDescription
limitnumber
querystringyesRule preference or restriction to search for.

No output schema declared.

No examples provided.

get_deals ~41

Get currently visible PropScorer promo codes and deals, ranked by discount and public availability.

NameTypeReqDescription
categorystring
limitnumber

No output schema declared.

No examples provided.

get_firm_rules ~58

Return KB-backed rules, pricing, payout, FAQ, and terms excerpts for one firm, with source URLs and freshness metadata.

NameTypeReqDescription
categorystring
limitnumber
slugstringyesFirm slug.

No output schema declared.

No examples provided.

get_firm_score ~102

Get the PropScore, health signals, rules, plans, promos, and editorial notes for one firm. Use this before broad Q&A when the user names a single firm. Example: get_firm_score({"slug":"apex-trader-funding"}) or get_firm_score({"slug":"topstep"}).

NameTypeReqDescription
slugstringyesFirm slug, for example apex-trader-funding, topstep, take-profit-trader, or tradeify.

No output schema declared.

No examples provided.

get_kb_freshness ~46

Return knowledge base coverage and freshness for one or more firms.

NameTypeReqDescription
slugsarrayOptional firm slugs. Omit to inspect all firms with KB rows.

No output schema declared.

No examples provided.

get_payout_intel ~40

Return payout-related intelligence for one firm, including payout speed, transparency, and payout stats when available.

NameTypeReqDescription
slugstringyesFirm slug.

No output schema declared.

No examples provided.

rank_firms_for_trader_profile ~122

Rank firms for a trader profile using price, account size, payout, platform, and rule preferences.

NameTypeReqDescription
categorystring
daily_payoutsbooleanPrefer firms with daily payouts.
limitnumber
max_pricenumberMaximum challenge price.
min_account_sizenumberMinimum account size.
one_day_passbooleanPrefer firms with one-day-pass rules.
platformstringPreferred platform, for example Tradovate, NinjaTrader, TradingView.

No output schema declared.

No examples provided.

search_firms ~71

Search PropScorer's prop firm database by name, category, platform, instrument, or rule preference.

NameTypeReqDescription
categorystring
limitnumber
querystringOptional text query, for example Apex, Topstep, Tradovate, crypto, or daily payouts.

No output schema declared.

No examples provided.

Common questions

What is the PropScorer MCP server?

PropScorer is an MCP server listed in the public MCP registry as io.github.r2hb-assistant/propscorer. Read-only MCP tools for prop firm scores, comparisons, payouts, deals, and rules. This page covers its hosted endpoint (https://mcp.propscorer.com).

Is the PropScorer MCP server safe to use?

PropScorer scores 73 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 PropScorer MCP server expose?

PropScorer exposes 11 tools: search_firms, get_firm_score, compare_firms, get_payout_intel, rank_firms_for_trader_profile, and 6 more. Their descriptions and schemas cost roughly 783 tokens of context every time the server is loaded.

Does the PropScorer MCP server require authentication?

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

Is the PropScorer MCP server still maintained?

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