TX ESBD Procurement MCP Server

by j0401 Your server? Claim it

answering

TX ESBD Procurement is answering right now. Last checked 10 min ago.

Texas procurement search with NIGP codes, change tracking, 60k+ bids, $0.01+.

Uptime history 74 days of history · worst day 98%

74 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

365 ms

Response time

average over 24h

API key

Access

streamable-http

TX ESBD Procurement missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add tx-esbd --transport http 'https://mcp.apify.com?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes'

Settings → Connectors → Add custom connector, then paste this address

https://mcp.apify.com?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes

~/.codex/config.toml

[mcp_servers.tx-esbd]
url = "https://mcp.apify.com?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes"

.cursor/mcp.json

{
  "mcpServers": {
    "tx-esbd": {
      "url": "https://mcp.apify.com?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "tx-esbd": {
      "type": "http",
      "url": "https://mcp.apify.com?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.apify.com?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes	streamable-http	needs key	328 ms	10 min ago

Alternatives to TX ESBD Procurement

same job, measured the same way

Procureport

by cloudcorprecords

Korean public procurement: bids, awards, contracts, statistics, products and mall search.

317 installs/wk local only

Cashbackpro

by cashbackpro

Search AliExpress with real prices, live promo codes and the true post-cashback cost.

5 tools answering

US Code of Federal Regulations

by mccallar

Look up, search, and track changes to the US Code of Federal Regulations (eCFR).

198 installs/wk local only

New Jersey Code

by pipeworx-io

New Jersey Statutes (N.J.S.A.) — section by citation (with amendment history), plus topic search.

325 installs/wk 46 tools answering

Oko

by bartlomein

Code search for coding agents: ranked, exact excerpts with line numbers.

local only

Swiss Procurement MCP

by malkreide

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

202 installs/wk local only

Memory Fts

by kurovu146

Long-term memory for Claude Code with SQLite FTS5 search and BM25 ranking

61 installs/wk local only

Deepsearch

by cloudcorprecords

Neural web search, code context, and page crawling through the Exa API.

88 installs/wk local only

TX ESBD Procurement — questions

Answers built from our own checks of this server.

Why is there no tool list for TX ESBD Procurement?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is TX ESBD Procurement working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 365 ms. The bar chart above shows every period we have measured.

How do I connect TX ESBD Procurement?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key: it refuses anonymous clients.

Does TX ESBD Procurement need an API key?

Yes. Every time we knock, TX ESBD Procurement answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is TX ESBD Procurement?

It answers our handshake in 365 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.