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

izhost-mcp

https://mcp.izhost.com

Registry code: 91b9220ce6869598

api record

izHost public read-only MCP. Use the tools to look up izHost service pricing, plans and domain availability. No authentication required.

endpoint
https://mcp.izhost.com
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 izhost-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is izhost-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does izhost-mcp have?
8 tools: get_email_pricing, check_domain_availability, get_ssl_products, get_domain_pricing, get_web_hosting_pricing, get_cloud_server_pricing, get_mail_relay_pricing, list_services.
Is izhost-mcp 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
99.6%

90 days 99.5%· all time 99.5%

latency
269ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 625 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
infrastructure & devops cloud & hosting
used for
  • check domain availability
  • get web hosting prices
  • get cloud server pricing
  • get ssl certificate products
takes → gives
text → data
tools
8 reads
_ 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
6 open 2 never probed 6 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.

  • get_ssl_products reads open 9h ago

    izHost SSL sertifikasi urunlerini (marka, tur, yillik fiyat) listeler.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_domain_pricing reads open 13h ago

    izHost alan adi (domain) uzantilarinin (TLD) kayit/yenileme/transfer fiyat listesini doner.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_web_hosting_pricing reads open 9h ago

    izHost web hosting (Linux ve Windows) paket ve fiyatlarini doner.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_cloud_server_pricing reads open 13h ago

    izHost bulut sunucu (Cloud Server / VDS) kaynak fiyatlandirmasini (CPU, RAM, disk vb.) ve planlarini doner.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_mail_relay_pricing reads open 13h ago

    izHost Mail Relay (SMTP gonderim) gunluk limit kademeleri ve fiyatlarini doner.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_services reads open 16h ago

    izHost'un sundugu tum hizmetlerin (bulut sunucu, hosting, kurumsal e-posta, mail relay, SSL, domain, IzDesk, AD Yonetimi) ozetini ve sayfa baglantilarini doner.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_email_pricing reads unknown never probed

    izHost kurumsal e-posta (izMail) paket ve fiyatlarini doner.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • check_domain_availability reads unknown 9h ago

    Bir alan adinin (domain) kayit icin musait olup olmadigini ve fiyatini sorgular. Ornek: "vizyonpay.com bos mu?". Yalnizca musaitlik ve fiyat bilgisi doner; kisisel/whois verisi donmez.

    mcp-tool

    {
  "type": "object",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "description": "Sorgulanacak tam alan adi, orn: example.com"
    }
  },
  "additionalProperties": false
}
    arguments 13 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 91b9220ce6869598.

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