Ekap Tender Mcp

io.github.sercanmetalorePublished by GitHub account sercanmetalorev0.1.0Updated Oct 24, 2026

Resmî Kamu İhale Bülteni (EKAP) üzerinden CAPTCHA'sız/girişsiz ihale ilanı arşivleme ve arama,…

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant search and archive Turkish public tender notices from the official EKAP bulletin without CAPTCHA or login.

What you can do
Search and archive tender notices published in Turkey's official public procurement bulletin (EKAP). Retrieve tender announcements without CAPTCHA or sign-in. The manifest lists no individual tools, so exact operations are not documented.
When to use it
Useful when you want an assistant to look up or keep a record of Turkish public tender announcements, for example to track procurement opportunities or research past notices.
Requirements
A remote MCP endpoint at mcp.boykaf.com over streamable HTTP; no package, account, API key, header or environment variable is declared. Network access to the endpoint is required.
Before you install
The server is hosted by a third party and the manifest declares no authentication, so requests are not tied to a verified identity. Tender data is passed through that third-party endpoint. No tool list is published, so what it can read or store cannot be verified in advance.

Installation

In SourceWeft

  1. Open Ekap Tender Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.sercanmetalore%2Fekap-tender-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "ekap-tender": {
      "type": "http",
      "url": "https://mcp.boykaf.com/ekap-tender/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.