izHost
REMOTE · MCP.IZHOST.COM
izHost public read-only MCP: service pricing and live domain availability lookup.
Available components
Last scanned (7 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 22 Nov 2026.
Category Cloud Infrastructure
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 383 tokens (~47/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 −1
- Tool “get_ssl_products” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Probed https://mcp.izhost.com
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.izhost.com | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 12 Nov 2026 | 4 May 2027 | RSA 2048 | SHA256-RSA | 4a45ce7b1d8b7b1737d85bb87c16e4fa |
| SANs: *.izhost.com, izhost.com | ||||||
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
| CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 1 Feb 2010 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | 1fd6d30fca3ca51a81bbc640e35032d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.izhost.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| izhost.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.izhost.com | Verified | 200 | |
| http (plaintext) | http://mcp.izhost.com | HTTPS enforced | 301 | https://mcp.izhost.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_domain_availability ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Sorgulanacak tam alan adi, orn: example.com |
No output schema declared.
No examples provided.
get_cloud_server_pricing ~44
izHost bulut sunucu (Cloud Server / VDS) kaynak fiyatlandirmasini (CPU, RAM, disk vb.) ve planlarini doner.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_domain_pricing ~39
izHost alan adi (domain) uzantilarinin (TLD) kayit/yenileme/transfer fiyat listesini doner.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_email_pricing ~29
izHost kurumsal e-posta (izMail) paket ve fiyatlarini doner.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_mail_relay_pricing ~34
izHost Mail Relay (SMTP gonderim) gunluk limit kademeleri ve fiyatlarini doner.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_ssl_products ~31
izHost SSL sertifikasi urunlerini (marka, tur, yillik fiyat) listeler.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_web_hosting_pricing ~28
izHost web hosting (Linux ve Windows) paket ve fiyatlarini doner.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services ~59
izHost'un sundugu tum hizmetlerin (bulut sunucu, hosting, kurumsal e-posta, mail relay, SSL, domain, IzDesk, AD Yonetimi) ozetini ve sayfa baglantilarini doner.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the izHost MCP server?
izHost is a hosted endpoint at https://mcp.izhost.com/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.izhost.com
claude mcp add --transport http com-izhost-mcp 'https://mcp.izhost.com/'
What is the izHost MCP server?
izHost is an MCP server listed in the public MCP registry as com.izhost/mcp. izHost public read-only MCP: service pricing and live domain availability lookup. This page covers its hosted endpoint (https://mcp.izhost.com).
Is the izHost MCP server safe to use?
izHost scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the izHost MCP server expose?
izHost exposes 8 tools: check_domain_availability, get_domain_pricing, get_cloud_server_pricing, get_email_pricing, get_mail_relay_pricing, and 3 more. Their descriptions and schemas cost roughly 353 tokens of context every time the server is loaded.
Does the izHost MCP server require authentication?
No. We connected to izHost without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the izHost MCP server still maintained?
izHost is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the izHost MCP server?
VerifyMCP ran 12 checks on izHost, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about izHost: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.