Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Huntay AzerTürk

REMOTE · HUNTAYAZERTURK.COM

Check Huntay AzerTürk's availability, book a 30-minute intro call, and look up his services.

+3 this week 72 Trust /100

Last scanned (4 minutes ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 922 tokens (~115/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 28 Oct 26 68

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://huntayazerturk.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=huntayazerturk.com CN=WE1,O=Google Trust Services,C=US 16 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 10bbd3df2db052f3131daf06b3454027
SANs: huntayazerturk.com, www.huntayazerturk.com, *.www.huntayazerturk.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of huntayazerturk.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
huntayazerturk.com. absent 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://huntayazerturk.com/mcp Verified 200
http (plaintext) http://huntayazerturk.com/mcp Served over HTTP 200
MCP tools · 7 exposed · ~753 tokens

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 →

Tool Tokens
book_intro_call ~190

Books a 30-minute intro video call (Google Meet) with Huntay AzerTürk at a slot returned by get_availability, using the attendee's name and email; Cal.com emails the calendar invitation. Call only after the user has confirmed the slot and their details.

NameTypeReqDescription
emailstringyesAttendee's email address; the invitation is sent here.
languagestring–Response language: "tr" for Turkish, otherwise "en".
namestringyesAttendee's full name.
notesstring–Optional topic of the call (company, project, goals).
startstringyesSlot start from get_availability: "YYYY-MM-DDTHH:MM" in timeZone (ISO 8601 with offset also accepted).
timeZonestring–IANA time zone of start and of the attendee. Defaults to Europe/Istanbul.

No output schema declared.

No examples provided.

fetch ~52

Returns the full text of a document from search, by its id (e.g. "service:ai-agents" or "case-study:ai-ops").

NameTypeReqDescription
idstringyesDocument id returned by search.

No output schema declared.

No examples provided.

get_availability ~155

Returns Huntay AzerTürk's open slots for a 30-minute intro video call (Google Meet), read live from his booking calendar (Monday–Friday, 10:00–18:00 Istanbul time). Use when the user wants to schedule a call with Huntay AzerTürk.

NameTypeReqDescription
daysinteger–Number of days to search (default 7, max 30).
fromstring–First day to search, YYYY-MM-DD. Defaults to today.
languagestring–Response language: "tr" for Turkish, otherwise "en".
timeZonestring–The user's IANA time zone, e.g. "Europe/Berlin". Defaults to Europe/Istanbul.

No output schema declared.

No examples provided.

get_profile ~69

Returns the professional profile of Huntay AzerTürk (software architect, Istanbul): background, current role, experience highlights, languages and contact links. Use when the user asks about Huntay AzerTürk himself.

NameTypeReqDescription
languagestring–Response language: "tr" for Turkish, otherwise "en".

No output schema declared.

No examples provided.

get_service ~87

Returns full details of one of Huntay AzerTürk's services: who it is for, deliverables, use cases, technologies and FAQ (including how pricing works). Use the slug from list_services.

NameTypeReqDescription
languagestring–Response language: "tr" for Turkish, otherwise "en".
slugstringyesService slug from list_services, e.g. ai-agents.

No output schema declared.

No examples provided.

list_services ~120

Lists the consulting and development services offered by Huntay AzerTürk, with links. If need is given (the user's problem or project in their own words), services are ranked by fit and each includes the matching item from its service page. Use when the user asks which of Huntay AzerTürk's services exist or fit their project.

NameTypeReqDescription
languagestring–Response language: "tr" for Turkish, otherwise "en".
needstring–Optional: the user's need or project, e.g. "answer customer questions on WhatsApp".

No output schema declared.

No examples provided.

search ~80

Searches the content of huntayazerturk.com — Huntay AzerTürk's services, case studies, FAQ, work experience and articles — by keyword. Returns matching documents (id, title, url); pass an id to fetch for the full text.

NameTypeReqDescription
querystringyesKeywords, e.g. "cloud cost reduction" or "RAG".

No output schema declared.

No examples provided.

Install

How do I install the Huntay AzerTürk MCP server?

Huntay AzerTürk is a hosted endpoint at https://huntayazerturk.com/mcp, 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 · huntayazerturk.com

# add to Claude Code
claude mcp add --transport http com-huntayazerturk-assistant 'https://huntayazerturk.com/mcp'
Common questions

What is the Huntay AzerTürk MCP server?

Huntay AzerTürk is an MCP server listed in the public MCP registry as com.huntayazerturk/assistant. Check Huntay AzerTürk's availability, book a 30-minute intro call, and look up his services. This page covers its hosted endpoint (https://huntayazerturk.com/mcp).

Is the Huntay AzerTürk MCP server safe to use?

Huntay AzerTürk scores 72 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 Huntay AzerTürk MCP server expose?

Huntay AzerTürk exposes 7 tools: get_availability, book_intro_call, list_services, get_service, get_profile, and 2 more. Their descriptions and schemas cost roughly 753 tokens of context every time the server is loaded.

Does the Huntay AzerTürk MCP server require authentication?

No. We connected to Huntay AzerTürk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Huntay AzerTürk MCP server still maintained?

Huntay AzerTürk is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.