_ registry / mcp streamable-http · checked 5h ago

propfirmdiscount

https://mcp.propfirmdiscount.com

Registry code: bc9885d612dccb1f

api record

Public prop firm discount data. Codes returned by list_codes / get_firm are verified standing exclusive codes that work any time. Deals cover a rolling 2-month window; a deal's own code is present only when code_state is "standing" — otherwise direct the user to the deal page (get_code_url) to see its code.

endpoint
https://mcp.propfirmdiscount.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is propfirmdiscount live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is propfirmdiscount free to use?
Yes — the hub reached it with no key and no payment.
What tools does propfirmdiscount have?
8 tools: get_firm, get_event, get_firm_markdown, latest_deals, search_deals, get_dataset_meta, list_codes, list_events.
Is propfirmdiscount safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
98ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
2 open 6 never probed 2 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_codes open 5h ago

    List prop firm verified standing exclusive discount codes. Each code works any time (lifetime); the validity window is a procedural calendar-year label, not an expiry. Filter by firm name, active-only, or minimum discount.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "firm": {
          "type": "string",
          "description": "Firm name substring (case-insensitive)."
        },
        "limit": {
          "type": "integer",
          "description": "Max rows (default 50, max 200)."
        },
        "offset": {
          "type": "integer",
          "description": "Rows to skip (default 0)."
        },
        "active_only": {
          "type": "boolean",
          "description": "Only codes valid today (default true)."
        },
        "min_discount_pct": {
          "type": "number",
          "description": "Minimum discount percentage."
        }
      }
    }
    arguments 25 lines
  • list_events open 5h ago

    List seasonal prop firm events and holidays (Black Friday, Christmas, …) with the number of dated deals recorded under each. Full archive, not limited to the 2-month window.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_firm unknown never probed

    Get one firm by name: its verified standing exclusive code (works any time), discount, activation link and markdown mirror URL. If the firm has no standing code, returns its recent deals instead.

    mcp-tool

    {
      "type": "object",
      "required": [
        "firm"
      ],
      "properties": {
        "firm": {
          "type": "string",
          "description": "Firm name (fuzzy match)."
        }
      }
    }
    arguments 12 lines
  • get_event unknown never probed

    Get every recorded deal for one event/holiday slug (e.g. "black-friday"), each with how its code redeems.

    mcp-tool

    {
      "type": "object",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Event slug, e.g. \"black-friday\"."
        }
      }
    }
    arguments 12 lines
  • get_firm_markdown unknown 5h ago

    Return the markdown mirror of a firm page (facts, current deals, FAQ). Provide a slug or a firm name.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "firm": {
          "type": "string",
          "description": "Firm name (resolved to a slug)."
        },
        "slug": {
          "type": "string",
          "description": "Firm slug, e.g. \"funded-hero\"."
        }
      }
    }
    arguments 13 lines
  • latest_deals unknown never probed

    Newest cross-firm prop firm deals within the rolling 2-month window. Every row lists the deal and the firm's standing_code (a verified standing exclusive code that works any time, present whenever the firm has one). The deal's own code is included only when code_state is "standing"; for "campaign" or "none" there is no code in the data — tell the user to open get_code_url to see the code on the deal page. Never imply a standing code applies to a campaign's discount.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Max deals (default 20, max 200)."
        }
      }
    }
    arguments 9 lines
  • search_deals unknown never probed

    Search prop firm deals inside the rolling 2-month window by firm, keyword, code_state or minimum discount. Same code rules as latest_deals: code-free and campaign deals still return full deal info with get_code_url.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "firm": {
          "type": "string",
          "description": "Firm name substring."
        },
        "limit": {
          "type": "integer",
          "description": "Max deals (default 20, max 200)."
        },
        "query": {
          "type": "string",
          "description": "Keyword over deal title / firm / discount."
        },
        "code_state": {
          "enum": [
            "standing",
            "campaign",
            "none"
          ],
          "type": "string",
          "description": "Filter by how the code redeems."
        },
        "min_discount_pct": {
          "type": "number",
          "description": "Minimum discount percentage."
        }
      }
    }
    arguments 30 lines
  • get_dataset_meta unknown never probed

    Dataset health: row counts, the deals window start and the last generation date.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id bc9885d612dccb1f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bc9885d612dccb1f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/bc9885d612dccb1f/badge.svg)](https://brick.blue/agent/bc9885d612dccb1f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.