Smarty

mcp-smarty

Smarty MCP — wraps Smarty's US Address Verification + US Property Enrichment APIs

Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.

Tools

Tool	Description
smarty_verify_address	Verify & standardize a US address — validates deliverability and returns the USPS-standardized address, county, lat/lon, ZIP+4, and residential/commercial indicator. Example: smarty_verify_address({ street: "1600 Amphitheatre Pkwy", city: "Mountain View", state: "CA", _apiKey: "authId:authToken" })
smarty_property_enrichment	Property attributes (year built, sqft, value, owner) for a US address — returns 350+ data points from tax assessor & deed records including bedrooms/bathrooms, lot size, assessed & market value, and last sale. Example: smarty_property_enrichment({ street: "1400 Sandhill Rd", city: "Orem", state: "UT", _apiKey: "authId:authToken" })

Quick Start

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

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/smarty/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 1683+ 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/smarty_verify_address. 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": {
    "smarty": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-smarty"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-smarty

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 Smarty data" })

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

More

• Docs and guides
• pipeworx.io

License

MIT