← Registry

API Tools

buildscottsbluff.com

Provides agent-accessible Build Scotts Bluff economic development data and services, including site listings, funding matches, service profiles, and an x402-priced catalog.

x402 supported1 endpoint6 known toolsFirst detected October 21, 2026Last detected October 21, 2026

ENDPOINT 1

https://buildscottsbluff.com/mcp

No auth detected

MCP server metadata

Name
build-scotts-bluff
Version
1.1.0
Capabilities
tools
Server instructions

Free tools: get_discovery, search_listings, match_funding, get_catalog, get_pricing. The priced parcel + tax-sale data is bought per call with x402 (see get_pricing). The public map at buildscottsbluff.com is free for people.

Known tools 6

get_discovery

List the Build Scotts Bluff machine on-ramps: OpenAPI service description, free search endpoints, MCP tool manifest, x402 payment discovery, RFC 9727 API catalog, agent/auth registration, and the docs.

Potential side effects
get_service_profile

Machine context brief for Build Scotts Bluff: what it is, which paid products it replaces (Candid, Instrumentl, Cause IQ, Beacon, gWorks, PolicyMap) with their published list prices, a measured system inventory, and a replacement-cost estimate at Nebraska BLS wages with the methodology and citations stated.

Inferred read-only
search_listings

Search the county for-sale / available-sites inventory (LocationOne) by city, type (Site|Building), and price.

Inferred read-only
match_funding

Match a use-case to grant / lending / incentive programs (with amounts, match requirements, portals, and first-party source URLs).

Inferred read-only
get_catalog

The full Build Scotts Bluff data + service catalog sold to agents per call in USDC over x402: id, name, price, availability, description.

Inferred read-only
get_pricing

How to pay for the two live paid endpoints with x402: the per-parcel full record and the county tax-sale / delinquency list.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.build-scotts-bluff]
url = "https://buildscottsbluff.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "build-scotts-bluff": {
      "type": "http",
      "url": "https://buildscottsbluff.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: build-scotts-bluff
Remote MCP URL: https://buildscottsbluff.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "build-scotts-bluff": {
      "url": "https://buildscottsbluff.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "build-scotts-bluff": {
      "type": "http",
      "url": "https://buildscottsbluff.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "build-scotts-bluff",
  "transport": "streamable-http",
  "url": "https://buildscottsbluff.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.