mcpField
D
Datafiniti

Datafiniti

Remote
pipeworx.ioBusiness & Marketing0Updated 4d ago

About Datafiniti

Datafiniti is an MCP server that wraps the Datafiniti Data API for searching US property, business, and product records. It uses Datafiniti’s field:value query syntax and requires users to supply their own API key.

Key features

  1. 01Search US property records
  2. 02Search business and location records
  3. 03Search product records
  4. 04Filter with field:value queries
  5. 05Supply an API key for searches

Use cases

  1. 01Find US properties matching location and bedroom criteria
  2. 02Research businesses by category and location
  3. 03Look up product prices and identifiers by brand

MCP support

Exposes property, business, and product search tools to MCP clients. Searches require a user-provided Datafiniti API key; the server can run locally over stdio or through the Pipeworx gateway.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/datafiniti/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-datafiniti

Datafiniti MCP — wraps the Datafiniti Data API (datafiniti.co)

Part of Pipeworx — an MCP gateway connecting AI agents to 1878+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

ToolDescription
datafiniti_property_searchSearch Datafiniti's US property database (100M+ records) — returns address, square footage, bed/bath counts, property type, ownership (people), and tax/assessment data. Uses the Datafiniti field:value query language. Example: datafiniti_property_search({ query: "country:US AND city:"Austin" AND numBedroom:3", num_records: 5, _apiKey: "your-token" })
datafiniti_business_searchSearch Datafiniti's business/location database — returns name, address, category, phone, website, lat/lon, and reviews. Uses the Datafiniti field:value query language. Example: datafiniti_business_search({ query: "country:US AND categories:Restaurant AND city:"Seattle"", num_records: 5, _apiKey: "your-token" })
datafiniti_product_searchSearch Datafiniti's product database (250M+ records) — returns name, brand, categories, prices (amount/currency/merchant), and identifiers (UPC/ASIN/SKU). Uses the Datafiniti field:value query language. Example: datafiniti_product_search({ query: "brand:Nike AND categories:Shoes", num_records: 5, _apiKey: "your-token" })

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "datafiniti": {
      "url": "https://gateway.pipeworx.io/datafiniti/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/datafiniti/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1878+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/datafiniti_property_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "datafiniti": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-datafiniti"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-datafiniti

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Datafiniti data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.