CountyLayer

io.github.Esoteric918Published by GitHub account Esoteric918v1.0.0Updated Oct 24, 2026

MCP server for querying Tulsa County, Oklahoma property and parcel data for AI agents.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote MCP server that lets an assistant query structured Tulsa County, Oklahoma property and parcel records for AI agents.

What you can do
Query Tulsa County, Oklahoma property and parcel data from a collection of over 250,000 records, returning structured results to the assistant.
When to use it
Useful when an assistant needs property or parcel information for Tulsa County, Oklahoma, such as research or lookups that would otherwise require manual searching.
Requirements
A remote streamable HTTP endpoint at countylayer.com. A paid CountyLayer API key is required, sent as a bearer token in the Authorization header; the key is delivered by email after subscribing to a pricing plan.
Before you install
Access is paid: a subscription is needed before use. The API key is a secret sent in the Authorization header and should be kept private. Queries are sent to a third-party service, countylayer.com.

Installation

In SourceWeft

  1. Open CountyLayer in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Esoteric918%2Fcountylayer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "countylayer": {
      "type": "http",
      "url": "https://countylayer.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

tulsa_data_mcp

Paid MCP server exposing structured Tulsa County, OK property data (250k+ records) for AI agents. FastMCP + Postgres + Stripe billing, deployed on DigitalOcean. Live at countylayer.com.

Source: README.md at commit 026f8ac

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 26, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.