com.editalmd/editalmd vs TX ESBD Procurement
com.editalmd/editalmd is an MCP server published by editalmd.com. Marketplaces we read that list it: 1 (Official MCP Registry). TX ESBD Procurement is an MCP server published by J0401. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
| Marketplace |  com.editalmd/editalmd |  TX ESBD Procurement |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 No figure published 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
| Fact | com.editalmd/editalmd | TX ESBD Procurement |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-15 | Not published |
| Where it runs (differs) | Remote server (editalmd.com/mcp) | Remote server (mcp.apify.com) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/wrpbr/editalmd | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 9 h ago | Status out of date: last check 30 h ago returned HTTP 401 |
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
com.editalmd/editalmd
Brazilian public procurement (PNCP): search, deadlines, tender markdown, alerts and watches.
TX ESBD Procurement
Texas procurement search with NIGP codes, change tracking, 60k+ bids, $0.01+.
How to run each
com.editalmd/editalmd As a remote MCP server
claude mcp add --transport http editalmd https://editalmd.com/mcpTX ESBD Procurement
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither the marketplaces of TX ESBD Procurement nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: com.editalmd/editalmd · What it can do: TX ESBD Procurement · 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.