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

leadsfreshdb

https://leadsfreshdb.com

Registry code: 70b0a7051e8e0402

api record

Leads Fresh DB sells fresh, filtered phone leads (any country; 6 ready: NL, DK, UK, IT, PT, AT). Use get_catalog for the live price list, get_quote to price lists, get_free_sample for the free 200-number test. Ordering and payment happen on https://leadsfreshdb.com or on Telegram by the user — never claim an order was placed.

endpoint
https://leadsfreshdb.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 leadsfreshdb live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is leadsfreshdb free to use?
Yes — the hub reached it with no key and no payment.
What tools does leadsfreshdb have?
3 tools: get_quote, get_free_sample, get_catalog.
Is leadsfreshdb 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
590ms

last good check

priced tools
0

of 3 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 3 tools
2 open 1 never probed 2 of 3 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_free_sample open 2h ago

    How to get 200 numbers free (your country, your filter) to test before ordering: the Telegram link and the message to send. Nothing is sent for the user — they send it themselves.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "filter": {
          "enum": [
            "old",
            "mixed",
            "business",
            "ios",
            "rcs",
            "photo",
            "carrier"
          ],
          "type": "string",
          "description": "Which list: old = Old people 55+ — men, women or both, aged 55 to 100 (option: gender); mixed = Any age & gender — the age range and gender the campaign needs (options: gender, age_min, age_max); business = Business numbers only — shops, clinics, garages, cafés; ios = iPhone users only; rcs = RCS-ready numbers (rich cards, images, buttons); photo = Chosen by what the profile photo shows, e.g. dog lovers, garden lovers (option: interest); carrier = Only numbers on one mobile network (option: carrier); any other filter can be limited to a network too"
        },
        "country": {
          "type": "string",
          "description": "Two-letter code of a ready country (nl, dk, gb, it, pt, at) or the English name of any other country (prepared on request, same prices)."
        }
      }
    }
    arguments 22 lines
  • get_catalog open 2h ago

    Leads Fresh DB live price list for fresh, filtered phone leads (B2C and B2B): the seven filters (seniors 55+, any age & gender, business numbers, iPhone users, RCS-ready, by profile photo, one mobile network), the ready countries (Netherlands, Denmark, United Kingdom, Italy, Portugal, Austria; any other country on request), the price per 1,000 numbers and the volume discounts. Read this before talking about prices.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_quote unknown 2h ago

    Price one or more phone-lead lists exactly as the Leads Fresh DB shop charges them (live prices, volume discounts included) and get the link to order. Nothing is ordered.

    mcp-tool

    {
      "type": "object",
      "required": [
        "lists"
      ],
      "properties": {
        "lists": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "country",
              "filter",
              "quantity"
            ],
            "properties": {
              "filter": {
                "enum": [
                  "old",
                  "mixed",
                  "business",
                  "ios",
                  "rcs",
                  "photo",
                  "carrier"
                ],
                "type": "string",
                "description": "Which list: old = Old people 55+ — men, women or both, aged 55 to 100 (option: gender); mixed = Any age & gender — the age range and gender the campaign needs (options: gender, age_min, age_max); business = Business numbers only — shops, clinics, garages, cafés; ios = iPhone users only; rcs = RCS-ready numbers (rich cards, images, buttons); photo = Chosen by what the profile photo shows, e.g. dog lovers, garden lovers (option: interest); carrier = Only numbers on one mobile network (option: carrier); any other filter can be limited to a network too"
              },
              "gender": {
                "enum": [
                  "Both",
                  "Female",
                  "Male"
                ],
                "type": "string",
                "description": "For old and mixed only. Default Both."
              },
              "age_max": {
                "type": "integer",
                "maximum": 100,
                "minimum": 18,
                "description": "For mixed only."
              },
              "age_min": {
                "type": "integer",
                "maximum": 100,
                "minimum": 18,
                "description": "For mixed only."
              },
              "carrier": {
                "type": "string",
                "description": "Optional mobile network, e.g. \"KPN\" or \"Vodafone\". Works with every filter."
              },
              "country": {
                "type": "string",
                "description": "Two-letter code of a ready country (nl, dk, gb, it, pt, at) or the English name of any other country (prepared on request, same prices)."
              },
              "interest": {
                "type": "string",
                "description": "For photo only, e.g. \"Dog lovers\" or \"Garden lovers\"."
              },
              "quantity": {
                "type": "integer",
                "maximum": 50000,
                "minimum": 1000,
                "multipleOf": 1000,
                "description": "How many numbers: 1000 to 50000, in steps of 1000."
              }
            }
          },
          "maxItems": 20,
          "minItems": 1
        }
      }
    }
    arguments 76 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 70b0a7051e8e0402.

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

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.