MCP server for Izzet Yildirim: ask your AI agent about his research, papers, and CV.
An MCP server for Izzet Yildirim. Connect it to your AI agent and ask about his research, papers, CV, and availability.
It is read-only and needs no sign-in. It answers from the public data on iyildirim.com, including the full text of his published papers.
Claude Code
claude mcp add iyildirim -- npx -y iyildirim
Claude Desktop, Cursor, VS Code, Windsurf (any client that launches local servers): add to the MCP config.
{
"mcpServers": {
"iyildirim": { "command": "npx", "args": ["-y", "iyildirim"] }
}
}
No install: most clients can connect straight to the hosted server, which is what this package forwards to.
claude mcp add --transport http iyildirim https://iyildirim.com/api/mcp
Claude, ChatGPT, and Cursor also accept https://iyildirim.com/api/mcp as a custom connector URL.
What has Izzet published on I/O tracing?
Read the system design section of the AgentStage paper and summarize it.
Is Izzet a fit for this role? (paste a job description)
| Tool | What it does |
|---|---|
get_profile | Overview, what he is looking for, contact, profiles |
find_publications | Search publications by topic, system, or venue |
get_publication | Everything public about one publication |
search_papers | Search the full text of public papers for passages |
read_paper | Read a paper section by section |
get_cv | Experience, education, service, certifications, and skills |
This package is a thin stdio-to-HTTP bridge. It holds no tools or data of its own: each message goes to https://iyildirim.com/api/mcp and the reply comes back unchanged, so the tools are always as current as the site. No dependencies.
Set IYILDIRIM_MCP_URL to point it at another endpoint, for example a preview deployment.
npm install
npm run validate # format check, types, tests, build
Releases are published to npm, and then listed in the official MCP registry as io.github.izzet/mcp, by publish.yml when a version tag is pushed.
version in package.json and in server.json (both version and packages[0].version) in a pull request and merge it. A test and the workflow check that they match.main: git tag v0.1.1 && git push origin v0.1.1 (the tag must match the version).To rehearse, run the workflow from the Actions tab: a manual run only does an npm dry run and validates server.json.
The registry login uses GitHub OIDC, so it needs no secret.
Publishing needs either a trusted publisher configured for this repo and publish.yml on npmjs.com (no secret), or an NPM_TOKEN repository secret.
MIT licensed.
FAQs
MCP server for Izzet Yildirim: ask your AI agent about his research, papers, and CV.
The npm package iyildirim receives a total of 0 weekly downloads. As such, iyildirim popularity was classified as not popular.
We found that iyildirim demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Security News
GitHub is tightening GitHub Actions security with new restrictions on privileged pull request workflows. Here's what changes and how maintainers are affected.
Security News
/Application Security
A practical guide to securing GitHub Actions against supply chain attacks, covering malicious pull requests, credential theft, dependency risks, and release pipelines.
Security News
Composer 2.11 adds dependency cooldowns, joining package managers that delay new releases to reduce supply chain risks while allowing urgent security updates.