# TX ESBD Procurement (remote · mcp.apify.com)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.apify.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/j0401-tx-esbd/mcp.md), [page](https://verifymcp.io/servers/j0401-tx-esbd/mcp)

## Channel facts

- Endpoint: `https://mcp.apify.com?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 86/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 55/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 733 tokens (~733/item across 0 items; 0 tools + 0 resources), over budget; trim descriptions and params.
  - Nothing to assess: this server has no tools to check for usage examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the TX ESBD Procurement MCP server?

TX ESBD Procurement is a hosted endpoint at https://mcp.apify.com/?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "j0401-tx-esbd": {
      "type": "remote",
      "url": "https://mcp.apify.com/?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add j0401-tx-esbd --url 'https://mcp.apify.com/?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes' --transport streamable-http
```

### Hermes

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

### Netclaw

```json
{
  "McpServers": {
    "j0401-tx-esbd": {
      "Transport": "http",
      "Url": "https://mcp.apify.com/?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes"
    }
  }
}
```

### Vellum

```bash
assistant mcp add j0401-tx-esbd -t streamable-http -u 'https://mcp.apify.com/?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 69, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-19 (score 69, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-18 (score 68, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-17 (score 68, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-16 (score 67, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-15 (score 67, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-14 (score 66, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-09-13 (score 66, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/j0401-tx-esbd/mcp#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 69
- 2026-09-18: 68
- 2026-09-17: 68
- 2026-09-16: 67
- 2026-09-15: 67
- 2026-09-14: 66
- 2026-09-13: 66
- 2026-09-12: 65
- 2026-09-11: 65
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 63
- 2026-09-07: 63
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 61
- 2026-09-03: 61
- 2026-09-02: 61
- 2026-09-01: 60
- 2026-08-31: 60
- 2026-08-30: 59
- 2026-08-29: 59
- 2026-08-28: 58

## Common questions

### What is the TX ESBD Procurement MCP server?

TX ESBD Procurement is an MCP server listed in the public MCP registry as io.github.J0401/tx-esbd. Texas procurement search with NIGP codes, change tracking, 60k+ bids, $0.01+. This page covers its hosted endpoint (https://mcp.apify.com?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes).

### Is the TX ESBD Procurement MCP server safe to use?

TX ESBD Procurement scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### Does the TX ESBD Procurement MCP server require authentication?

Yes. TX ESBD Procurement asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the TX ESBD Procurement MCP server still maintained?

TX ESBD Procurement is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.apify.com/?tools=j0401/tx-esbd-search,j0401/tx-esbd-get,j0401/tx-esbd-changes
- Changelog RSS feed: https://verifymcp.io/servers/j0401-tx-esbd/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/j0401-tx-esbd/mcp.json
- HTML version of this page: https://verifymcp.io/servers/j0401-tx-esbd/mcp