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

EKO-IKSI

https://eko-iksi.uz

Registry code: 1bd6d30034e69d47

api record

EKO-IKSI is a fertility clinic in Tashkent, Uzbekistan: IVF (EKO), ICSI (IKSI), insemination, andrology,

gynaecology and urology, open 24/7, with two partner clinics. This server gives read-only access to what

endpoint
https://eko-iksi.uz/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
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
295ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 7 tools
3 open 4 never probed 3 of 7 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_clinic_information open 19m ago

    Contacts, addresses, opening hours, licence and the three clinics of EKO-IKSI, a fertility (IVF / ICSI) clinic in Tashkent, Uzbekistan. Use this to tell someone how to reach or visit the clinic.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "language": {
      "enum": [
        "uz",
        "ru",
        "en"
      ],
      "type": "string",
      "description": "Language of the answer: uz (Uzbek, the site's own language and the default), ru (Russian) or en (English)."
    }
  }
}
    arguments 14 lines
  • list_doctors open 19m ago

    All doctors of EKO-IKSI clinic: name, position, specialties and experience, with a link to each profile. Use get_doctor for one doctor's full biography.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "language": {
      "enum": [
        "uz",
        "ru",
        "en"
      ],
      "type": "string",
      "description": "Language of the answer: uz (Uzbek, the site's own language and the default), ru (Russian) or en (English)."
    }
  }
}
    arguments 14 lines
  • search_articles open 19m ago

    Search the articles and news EKO-IKSI clinic has published about infertility, IVF, ICSI, andrology, gynaecology and the clinic itself. Returns titles, dates, summaries and links; use read_article for the full text.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "type": {
      "enum": [
        "article",
        "news",
        "any"
      ],
      "type": "string",
      "description": "article, news, or any (the default)."
    },
    "limit": {
      "type": "integer",
      "maximum": 30,
      "minimum": 1,
      "description": "How many results to return (default 10, at most 30)."
    },
    "query": {
      "type": "string",
      "description": "Words to look for in the title or text. Leave empty for the latest publications."
    },
    "language": {
      "enum": [
        "uz",
        "ru",
        "en"
      ],
      "type": "string",
      "description": "Language of the answer: uz (Uzbek, the site's own language and the default), ru (Russian) or en (English)."
    }
  }
}
    arguments 33 lines
  • get_doctor unknown never probed

    One EKO-IKSI doctor's full profile: position, specialties, experience and biography. Pass the id from list_doctors, or part of the doctor's name.

    mcp-tool

    {
  "type": "object",
  "required": [
    "doctor"
  ],
  "properties": {
    "doctor": {
      "type": "string",
      "description": "The doctor's id from list_doctors (e.g. \"fayoz-aminov\"), or part of their name."
    },
    "language": {
      "enum": [
        "uz",
        "ru",
        "en"
      ],
      "type": "string",
      "description": "Language of the answer: uz (Uzbek, the site's own language and the default), ru (Russian) or en (English)."
    }
  }
}
    arguments 21 lines
  • list_services unknown never probed

    The treatments and services EKO-IKSI and its two partner clinics offer, grouped by the sections of their price lists. Without `clinic`: an overview of all three clinics' sections and how many services each holds. With `clinic`: every service of that clinic by name. Use search_prices for the prices themselves.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "clinic": {
      "enum": [
        "eko-iksi",
        "eko-iksi-ivf",
        "oilam"
      ],
      "type": "string",
      "description": "One clinic, to list every service by name: eko-iksi (the main clinic), eko-iksi-ivf (partner clinic) or oilam (Oilam Medical Centre). Leave empty for an overview of all three."
    },
    "language": {
      "enum": [
        "uz",
        "ru",
        "en"
      ],
      "type": "string",
      "description": "Language of the answer: uz (Uzbek, the site's own language and the default), ru (Russian) or en (English)."
    }
  }
}
    arguments 23 lines
  • search_prices unknown never probed

    Search the price lists of EKO-IKSI and its two partner clinics in Tashkent (IVF, ICSI, consultations, tests, procedures). Prices are in Uzbek so'm. Search works in Uzbek, Russian or English.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "How many results to return (default 20, at most 50)."
    },
    "query": {
      "type": "string",
      "description": "Words from the service name, in any of the three languages — e.g. \"EKO\", \"ЭКО\", \"IVF\", \"androlog\", \"анализ\". Leave empty to list services."
    },
    "clinic": {
      "enum": [
        "eko-iksi",
        "eko-iksi-ivf",
        "oilam"
      ],
      "type": "string",
      "description": "Only one clinic: eko-iksi (the main clinic), eko-iksi-ivf (partner clinic) or oilam (Oilam Medical Centre). Leave empty for all three."
    },
    "language": {
      "enum": [
        "uz",
        "ru",
        "en"
      ],
      "type": "string",
      "description": "Language of the answer: uz (Uzbek, the site's own language and the default), ru (Russian) or en (English)."
    }
  }
}
    arguments 33 lines
  • read_article unknown never probed

    The full text of one EKO-IKSI article or news item. Pass its URL (from search_articles, or any eko-iksi.uz article address) or its slug.

    mcp-tool

    {
  "type": "object",
  "required": [
    "article"
  ],
  "properties": {
    "article": {
      "type": "string",
      "description": "The article's URL (e.g. \"https://eko-iksi.uz/ru/blog/...\") or its slug."
    },
    "language": {
      "enum": [
        "uz",
        "ru",
        "en"
      ],
      "type": "string",
      "description": "Language of the answer: uz (Uzbek, the site's own language and the default), ru (Russian) or en (English)."
    }
  }
}
    arguments 21 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, it shows the verified badge, 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 1bd6d30034e69d47.

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

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ 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.