huntayazerturk
Registry code: fad1fc0d3d7f7466
Tools for Huntay AzerTürk's software and AI consulting practice (https://huntayazerturk.com): his services, case studies, FAQ and profile, and his live booking calendar for a 30-minute intro call.
- Scheduling: call get_availability (pass the user's IANA time zone if known), let the user choose a time, collect their name and email, confirm the details with the user, then call book_intro_call. Do not book without the user's explicit confirmation.
- endpoint
- https://huntayazerturk.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 huntayazerturk live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is huntayazerturk free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does huntayazerturk have?
- 7 tools: get_service, search, book_intro_call, list_services, fetch, get_availability, get_profile.
- Is huntayazerturk 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.
90 days 100%· all time 100%
last good check
of 7 tools
- unknown → live
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.
through this hub
successful
what callers paid
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_availability open 1h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "days": { "type": "integer", "maximum": 30, "minimum": 1, "description": "Number of days to search (default 7, max 30)." }, "from": { "type": "string", "maxLength": 10, "description": "First day to search, YYYY-MM-DD. Defaults to today." }, "language": { "enum": [ "en", "tr" ], "type": "string", "description": "Response language: \"tr\" for Turkish, otherwise \"en\"." }, "timeZone": { "type": "string", "maxLength": 64, "description": "The user's IANA time zone, e.g. \"Europe/Berlin\". Defaults to Europe/Istanbul." } } }arguments 30 linesget_profile open 1h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "language": { "enum": [ "en", "tr" ], "type": "string", "description": "Response language: \"tr\" for Turkish, otherwise \"en\"." } } }arguments 14 linesget_service unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "slug" ], "properties": { "slug": { "enum": [ "ai-agents", "fractional-cto", "startup-product-development", "web-mobile-development", "cloud-devops", "microservices-modernization", "iot-platforms", "digital-transformation" ], "type": "string", "description": "Service slug from list_services, e.g. ai-agents." }, "language": { "enum": [ "en", "tr" ], "type": "string", "description": "Response language: \"tr\" for Turkish, otherwise \"en\"." } } }arguments 31 linessearch unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "query": { "type": "string", "maxLength": 300, "minLength": 1, "description": "Keywords, e.g. \"cloud cost reduction\" or \"RAG\"." } } }arguments 15 linesbook_intro_call unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "start", "name", "email" ], "properties": { "name": { "type": "string", "maxLength": 100, "minLength": 2, "description": "Attendee's full name." }, "email": { "type": "string", "maxLength": 254, "minLength": 5, "description": "Attendee's email address; the invitation is sent here." }, "notes": { "type": "string", "maxLength": 1000, "description": "Optional topic of the call (company, project, goals)." }, "start": { "type": "string", "maxLength": 40, "description": "Slot start from get_availability: \"YYYY-MM-DDTHH:MM\" in timeZone (ISO 8601 with offset also accepted)." }, "language": { "enum": [ "en", "tr" ], "type": "string", "description": "Response language: \"tr\" for Turkish, otherwise \"en\"." }, "timeZone": { "type": "string", "maxLength": 64, "description": "IANA time zone of start and of the attendee. Defaults to Europe/Istanbul." } } }arguments 46 lineslist_services unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "need": { "type": "string", "maxLength": 500, "description": "Optional: the user's need or project, e.g. \"answer customer questions on WhatsApp\"." }, "language": { "enum": [ "en", "tr" ], "type": "string", "description": "Response language: \"tr\" for Turkish, otherwise \"en\"." } } }arguments 19 linesfetch unknown 1h ago
Returns the full text of a document from search, by its id (e.g. "service:ai-agents" or "case-study:ai-ops").
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "maxLength": 120, "minLength": 1, "description": "Document id returned by search." } } }arguments 15 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idfad1fc0d3d7f7466.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fad1fc0d3d7f7466/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fad1fc0d3d7f7466?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.