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

sales-legends

https://saleslegends.co

Registry code: 423e12f1364834d4

api record

Sales Legends is a board of open sales jobs (SDR and BDR, account executive, account manager, customer success, sales engineering, sales leadership, sales operations and more), read every hour from the careers systems of the companies hiring, each role listed once with the pay its posting states. search_sales_jobs finds roles, get_sales_pay gives the posted pay for each kind of sales work, and get_sales_market counts the open roles by kind and by company. Give the user the role links: each opens the role on Sales Legends, where they apply. For investors and analysts, get_hiring_radar…

endpoint
https://saleslegends.co/api/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 sales-legends live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is sales-legends free to use?
Yes — the hub reached it with no key and no payment.
What tools does sales-legends have?
4 tools: get_sales_pay, get_sales_market, search_sales_jobs, get_hiring_radar.
Is sales-legends 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
431ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 3 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 4 tools
3 open 1 never probed 3 of 4 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.

  • get_sales_market open 4h ago

    How many sales roles are open today and how many went up in the past 7 days, broken down by kind of sales role and by employer (with the slug search_sales_jobs accepts). Give a country to count only roles open to people there. Call it to size the market for salespeople, to see which employers are hiring most, or to look up an employer's slug before search_sales_jobs with platform. The roles themselves come from search_sales_jobs and the pay from get_sales_pay.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "country": {
          "type": "string",
          "description": "An ISO 3166-1 two-letter country code ('US', 'DE' and so on); the counts cover only roles open to people in that country."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • search_sales_jobs open 4h ago

    Searches the open sales roles (sales and SDR managers, directors and heads of sales, every level of sales. A result carries the title, the employer, the kind of sales role, the posted pay, the location and a link to the role on Sales Legends, where the application starts. No filter is required. Call it when the user wants real openings to read or apply to, a pay floor included (min_pay_usd). For what a kind of sales role pays across the market call get_sales_pay; for counts of open roles by kind or employer call get_sales_market.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "kind": {
          "enum": [
            "sales-development",
            "account-executive",
            "account-management",
            "customer-success",
            "sales-engineering",
            "partner-sales",
            "revenue-operations",
            "sales-leadership",
            "retail-sales"
          ],
          "type": "string",
          "description": "One kind of sales role, as one of the slugs listed."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 25,
          "minimum": 1,
          "description": "How many roles come back, 1 to 25."
        },
        "query": {
          "type": "string",
          "description": "Words matched against role titles, such as 'VP of sales', 'SDR manager', 'EMEA', 'healthcare' or 'renewals'."
        },
        "country": {
          "type": "string",
          "description": "An ISO 3166-1 two-letter country code ('US', 'GB', 'CA' and so on); returns only roles that people in that country can take."
        },
        "platform": {
          "type": "string",
          "description": "A single employer, by slug; get_sales_market returns each employer with open roles and the slug to pass here."
        },
        "min_pay_usd": {
          "type": "integer",
          "maximum": 4160000,
          "minimum": 1,
          "description": "Returns roles whose posted range tops out at this many US dollars a year or more, for example 250000 for a $250k base or OTE. Pay quoted by the hour is counted at 2,080 hours a year."
        },
        "min_hourly_usd": {
          "type": "integer",
          "maximum": 2000,
          "minimum": 1,
          "description": "The floor as an hourly figure, turned into a year at 2,080 hours. Use min_pay_usd unless the user named an hourly rate."
        }
      },
      "additionalProperties": false
    }
    arguments 52 lines
  • get_hiring_radar open 4h ago

    Hiring radar, the dataset Sales Legends keeps on sales hiring for investors and analysts: each sales opening read from employers' careers boards since the board started, a row per role with its posted pay, kind, countries and the days it opened and closed, with every employer day by day and a change log. The answer gives today's coverage, the files, who they are for, the price and how to request a sample. Call it only for someone buying or evaluating the full history. Today's counts come from get_sales_market and single roles from search_sales_jobs.

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    arguments 4 lines
  • get_sales_pay unknown never probed

    Today's posted pay for every kind of sales role: the median and the 25th to 75th percentile of the figures employers state, with the number of figures and employers behind each. A kind is included only when at least three employers state pay for it. Call it when the user asks what a sales role pays, such as a first-line sales manager or a VP of sales. It returns no roles; to find roles above a pay figure, call search_sales_jobs with min_pay_usd.

    mcp-tool

    {
      "type": "object",
      "additionalProperties": false
    }
    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 423e12f1364834d4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/423e12f1364834d4/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/423e12f1364834d4/badge.svg)](https://brick.blue/agent/423e12f1364834d4?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
80%

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.