Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
Huntay AzerTürk is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
7
tools declared
remote
at its publisher
—
calls last 7d
What it does
The official MCP server of Huntay AzerTürk, software architect and fractional CTO with 13+ years in software architecture, cloud and DevOps, AI agents, IoT platforms and security. Your agent can list his services and fixed-price packages (Technical Check-up, Security Quick Scan, Architecture & Cloud Cost Review, AI Agent Pilot, Fractional CTO, MVP), get details of one service, read his profile, case studies, FAQ and articles, and check his live calendar to book a 30-minute intro call once the user confirms. Remote Streamable HTTP endpoint, no sign-in needed. Answers in English or Turkish. Website: huntayazerturk.com
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http huntay-azerturk-mcp https://huntayazerturk.com/mcp
# 2 — ask your agent for something these tools do
# get_availability, book_intro_call, list_services and 4 more
Huntay AzerTürk costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publisher
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http huntay-azerturk-mcp https://huntayazerturk.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| timeZone | string | no | The user's IANA time zone, e.g. "Europe/Berlin". Defaults to Europe/Istanbul. |
| from | string | no | First day to search, YYYY-MM-DD. Defaults to today. |
| days | integer | no | Number of days to search (default 7, max 30). |
| language | string | no | Response language: "tr" for Turkish, otherwise "en". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | string | yes | Slot start from get_availability: "YYYY-MM-DDTHH:MM" in timeZone (ISO 8601 with offset also accepted). |
| timeZone | string | no | IANA time zone of start and of the attendee. Defaults to Europe/Istanbul. |
| name | string | yes | Attendee's full name. |
| string | yes | Attendee's email address; the invitation is sent here. | |
| notes | string | no | Optional topic of the call (company, project, goals). |
| language | string | no | Response language: "tr" for Turkish, otherwise "en". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| need | string | no | Optional: the user's need or project, e.g. "answer customer questions on WhatsApp". |
| language | string | no | Response language: "tr" for Turkish, otherwise "en". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Service slug from list_services, e.g. ai-agents. |
| language | string | no | Response language: "tr" for Turkish, otherwise "en". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Response language: "tr" for Turkish, otherwise "en". |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Keywords, e.g. "cloud cost reduction" or "RAG". |
Returns the full text of a document from search, by its id (e.g. "service:ai-agents" or "case-study:ai-ops").
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Document id returned by search. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Huntay AzerTürk or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.1.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestb7efbc36e08abe3dccf0be9ce039ffcd1366345ac92cca9ff5a2e9461c3fbc99
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_availability | no tags | |
| book_intro_call | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| list_services | no tags | |
| get_service | no tags | |
| get_profile | no tags | |
| search | untrusted-input | untrusted-input: keyword "fetch" |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestb7efbc36e08abe3d
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Huntay AzerTürk can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.