# Izzet Yildirim (remote · iyildirim.com)

Ask your AI agent about Izzet Yildirim's research, papers, CV, and availability.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `iyildirim.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/izzet-mcp/api-mcp.md), [page](https://verifymcp.io/servers/izzet-mcp/api-mcp)
- npm · `iyildirim`: 49/100, [markdown](https://verifymcp.io/servers/izzet-mcp/iyildirim.md), [page](https://verifymcp.io/servers/izzet-mcp/iyildirim)

## Channel facts

- Endpoint: `https://iyildirim.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 670 tokens (~95/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Izzet Yildirim MCP server?

Izzet Yildirim is a hosted endpoint at https://iyildirim.com/api/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.

### Claude

```bash
claude mcp add --transport http izzet-mcp 'https://iyildirim.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "izzet-mcp": {
      "url": "https://iyildirim.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "izzet-mcp": {
      "type": "http",
      "url": "https://iyildirim.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.izzet-mcp]
url = "https://iyildirim.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "izzet-mcp": {
      "type": "remote",
      "url": "https://iyildirim.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add izzet-mcp --url 'https://iyildirim.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  izzet-mcp:
    url: "https://iyildirim.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "izzet-mcp": {
      "Transport": "http",
      "Url": "https://iyildirim.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add izzet-mcp -t streamable-http -u 'https://iyildirim.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "izzet-mcp": {
      "type": "http",
      "url": "https://iyildirim.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 79, +1)

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

### 2026-11-03 (score 78, +1)

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

### 2026-11-01 (score 77, +1)

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

### 2026-10-29 (score 76, +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.

### 2026-10-27 (score 75, +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.

### 2026-10-25 (score 74, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 73)

First indexed and scored.

## MCP tools (7)

### `get_cv_section` (~41 tokens)

Get one section of Izzet's CV: experience (roles and highlights), education, service, certifications, or skills.

Input parameters:

- `section` (string, required)

### `get_paper_section` (~92 tokens)

Get the text of one section of a public paper, by paper id and section title (from list_paper_sections or search_paper_text). Long sections come in parts: pass part to get the next one.

Input parameters:

- `id` (string, required): Publication id, e.g. 'agentstage'
- `part` (integer)
- `section` (string, required): Section title, e.g. 'System Design'

### `get_profile` (~61 tokens)

Start here. A short overview of Izzet: who he is, what he works on, what he is looking for, how to contact him, and links to his public profiles. For research use search_publications; for career detail use get_cv_section.

### `get_publication` (~74 tokens)

Get the catalog entry for one publication by its id: authors, venue, date, summary, headline results, abstract, and links. Not the paper's full text: use list_paper_sections and get_paper_section to read the paper.

Input parameters:

- `id` (string, required): Publication id, e.g. 'agentstage'

### `list_paper_sections` (~57 tokens)

List the sections of one public paper by its id, with how many parts each has. Use it to find a section title for get_paper_section.

Input parameters:

- `id` (string, required): Publication id, e.g. 'agentstage'

### `search_paper_text` (~101 tokens)

Search the full text of Izzet's public papers and posters for passages about a method, result, dataset, or term. Returns the best passages with their paper id and section; follow up with get_paper_section to read more. Covers only papers with a public PDF or preprint: use search_publications for the catalog of all work.

Input parameters:

- `query` (string, required): Specific terms, e.g. 'how AgentStage infers file paths'

### `search_publications` (~92 tokens)

Search the catalog of Izzet's publications by topic, system, or venue. Returns each match's title, venue, date, summary and page link. Catalog entries only, not the text of the papers: use search_paper_text to search what the papers say. Work under review appears only as a one-line summary.

Input parameters:

- `query` (string, required): Topic keywords, e.g. 'GPU storage tracing'

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/izzet-mcp/api-mcp#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 74
- 2026-10-25: 74
- 2026-10-24: 73

## Common questions

### What is the Izzet Yildirim MCP server?

Izzet Yildirim is an MCP server listed in the public MCP registry as io.github.izzet/mcp. Ask your AI agent about Izzet Yildirim's research, papers, CV, and availability. This page covers its hosted endpoint (https://iyildirim.com/api/mcp).

### Is the Izzet Yildirim MCP server safe to use?

Izzet Yildirim scores 79 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 Izzet Yildirim MCP server expose?

Izzet Yildirim exposes 7 tools: get_cv_section, get_paper_section, get_profile, get_publication, list_paper_sections, and 2 more. Their descriptions and schemas cost roughly 518 tokens of context every time the server is loaded.

### Does the Izzet Yildirim MCP server require authentication?

No. We connected to Izzet Yildirim without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Izzet Yildirim MCP server still maintained?

Izzet Yildirim 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.

### What did VerifyMCP test on the Izzet Yildirim MCP server?

VerifyMCP ran 13 checks on Izzet Yildirim, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.

## Links

- Remote endpoint: https://iyildirim.com/api/mcp
- Repository: https://github.com/izzet/mcp
- Website: https://iyildirim.com/
- Changelog RSS feed: https://verifymcp.io/servers/izzet-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/izzet-mcp/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/izzet-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/izzet-mcp/api-mcp