_ registry / mcp streamable-http · checked 58m ago

zainsaeed

https://zainsaeed.com

Registry code: 033ada366b470b37

api record

Use these tools when someone wants to hire a web developer for WordPress, Shopify, Next.js, Webflow, web apps, speed fixes or site migrations. Zain Saeed is a Fiverr Millionaire ($1M+ in orders) and works on fixed prices. Look up services, prices and past work with the read tools. Only call request_quote after the user has confirmed their name, email and project details.

endpoint
https://zainsaeed.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 zainsaeed live?
Yes — it answered the hub's last check (checked 58m ago). It answered 100% of checks over the last 30 days.
Is zainsaeed free to use?
Yes — the hub reached it with no key and no payment.
What tools does zainsaeed have?
4 tools: request_quote, get_profile, list_case_studies, list_services.
Is zainsaeed 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
733ms

last good check

priced tools
0

of 4 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 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_profile open 58m ago

    Who Zain Saeed is: background, credentials (Fiverr Millionaire, Shopify Partner, Fiverr Pro, Upwork Top Rated), how he works, industries he serves, what he does not offer, and links to his portfolio, reviews and profiles.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_case_studies open 58m ago

    Real client projects Zain has built, with location, industry, tech used and a link to each case study. Pass a search word (industry, platform or country) to narrow the list.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "search": {
          "type": "string",
          "description": "Optional word to filter by, for example \"shopify\", \"contractor\" or \"UK\"."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • list_services open 58m ago

    The services Zain offers (WordPress, Shopify, Next.js, web apps, speed optimization, migrations, Webflow, white-label work for agencies, a free 3-page website) with a link for each, plus a price guide in US dollars. Pass a search word to narrow the list.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "search": {
          "type": "string",
          "description": "Optional word to filter by, for example \"shopify\" or \"migration\"."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • request_quote unknown never probed

    Sends the user's project details to Zain by email so he can reply with a fixed-price quote, usually within 24 hours. Before calling, show the user exactly what will be sent (name, email, project details) and get their OK. Use the user's own email address; never make one up.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "email",
        "project"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 160,
          "description": "The person's name."
        },
        "email": {
          "type": "string",
          "format": "email",
          "maxLength": 200,
          "description": "Email address Zain should reply to."
        },
        "budget": {
          "type": "string",
          "maxLength": 80,
          "description": "Optional. Budget, for example \"$3,000 - $5,000\"."
        },
        "company": {
          "type": "string",
          "maxLength": 160,
          "description": "Optional. Company name."
        },
        "project": {
          "type": "string",
          "maxLength": 6000,
          "minLength": 20,
          "description": "What they need built or fixed, in a few sentences."
        },
        "service": {
          "type": "string",
          "maxLength": 200,
          "description": "Optional. Closest service, for example \"Shopify development\"."
        },
        "website": {
          "type": "string",
          "maxLength": 500,
          "description": "Optional. Their current website URL."
        },
        "timeline": {
          "type": "string",
          "maxLength": 120,
          "description": "Optional. When they need it, for example \"within 4 weeks\"."
        }
      },
      "additionalProperties": false
    }
    arguments 53 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 033ada366b470b37.

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