Mcp Ted

io.github.lexsocketPublished by GitHub account lexsocketv1.0.7Updated Oct 24, 2026

TED MCP Server: Real-time EU public tenders access. https://www.lexsocket.ai/

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that gives an assistant real-time access to EU public tender data from TED, authenticated with an API key.

What you can do
Retrieve EU public tender information from TED in real time through the hosted endpoint. The manifest lists no individual tools, so the exact operations are not documented; the stated purpose is real-time access to EU public tenders. Requests are authenticated with an API key sent in a header.
When to use it
Useful when an assistant needs current EU public procurement or tender information, for example to look up or monitor tender notices, rather than relying on stale knowledge.
Requirements
A remote MCP endpoint at the provider's hosted address; no local package or runtime is needed. A required API key supplied in the x-api-key header, obtained from the provider. Network access to the endpoint.
Before you install
The server requires an API key in the x-api-key header; treat it as a secret and avoid exposing it in shared logs or transcripts. The manifest lists no tools and there is no README, so what data is returned and whether any actions write or change anything cannot be verified before connecting.

Installation

In SourceWeft

  1. Open Mcp Ted in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. 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.lexsocket%2Fmcp-ted/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": {
    "ted": {
      "type": "http",
      "url": "https://mcp.lexsocket.ai/ted/",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.7LatestSep 16, 2026

Score

35% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 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.