Ext Ops Panel
Open dashboard
Comparison

io.github.lexsocket/mcp-ted vs io.github.malkreide/swiss-procurement-mcp

io.github.lexsocket/mcp-ted is an MCP server published by lexsocket. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.malkreide/swiss-procurement-mcp is an MCP server published by malkreide. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceio.github.lexsocket/mcp-tedio.github.malkreide/swiss-procurement-mcp
Official MCP Registry Listed
Version: 1.0.7
No figure published
Not marked · First seen
Listed
Version: 0.19.0
Downloads/month (PyPI): 300
Downloads/week (PyPI): 91
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

io.github.lexsocket/mcp-ted vs io.github.malkreide/swiss-procurement-mcp
Factio.github.lexsocket/mcp-tedio.github.malkreide/swiss-procurement-mcp
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.lexsocket.ai/ted)On your machine (swiss-procurement-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/lexsocket/mcp-tedgithub.com/malkreide/swiss-procurement-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-13no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

io.github.lexsocket/mcp-ted

In its own words, on Official MCP Registry:

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

io.github.malkreide/swiss-procurement-mcp

In its own words, on Official MCP Registry:

Swiss public procurement (simap.ch): tenders, awards, CPV codes, all cantons + federal, read-only

How to run each

io.github.lexsocket/mcp-ted As a remote MCP server

Claude Code
claude mcp add --transport http mcp-ted https://mcp.lexsocket.ai/ted/ --header "x-api-key: <YOUR_X_API_KEY>"

Requires: x-api-key header

io.github.malkreide/swiss-procurement-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio swiss-procurement-mcp -- uvx swiss-procurement-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.lexsocket/mcp-ted has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.lexsocket/mcp-ted · What it can do: io.github.malkreide/swiss-procurement-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built