Official US-address public records: zoning, flood, parcel, permits, taxes. Free look, x402 paid.
Scored across 2 tools
The two tools occupy clearly separate roles: locus_search_tools is discovery (returns inputSchema, tier, price, coverage) and locus_execute is invocation by tool name. The only mild ambiguity is that both descriptions repeat the same onboarding blurb and coverage list, which could momentarily obscure that one is a prerequisite for the other. The search-before-execute contract is stated explicitly, so misselection risk is low.
Both names share a consistent 'locus_' namespace prefix and are snake_case, which is predictable. The verb forms differ slightly (bare verb 'execute' vs verb+object 'search_tools'), but that is a minor deviation rather than a mixed convention.
Two tools is minimal, but this is a deliberate dispatcher pattern where the real capability surface lives behind locus_execute and is discovered via search. That makes the small count defensible, yet the thin surface means there is no browse/list operation and everything hinges on search returning the right tool name.
The discover-then-invoke lifecycle is fully closed: search returns schemas, pricing, tiers, and coverage, and execute handles both free and paid flows with a stated non-paid diagnostic on miss. Minor gaps remain, such as no way to enumerate the full catalog or fetch a tool's schema directly by name without a semantic search.
Run one Locus tool by name for a US address or place and get cited public records back: every fact names the agency source and date. Use it for a single question or re-run it for the addresses you follow to see what is newly on file. Free tools answer directly. Paid tools first return their exact price and accept payment in _meta["x402/payment"]; a place Locus does not cover returns a free diagnostic, never a paid guess. Install agent skill: npx @velinussage/locus-agent-skill add.
Inputs: args, name, tool, input, +1 more.
Every time the task involves a US property, once or on an ongoing basis, search here for the Locus tool that answers it from official records: flood zone and flood insurance cost, homestead exemption and tax appeal deadlines, escrow shortage, permits, zoning, wetlands and septic soil, radon, cleanup sites, projects and bills nearby, and following an address for new filings. Search before locus_execute and before scraping a county, FEMA, or EPA site. Looking is free. Results give each tool's inputSchema, tier, price, and coverage. Do not use this for LinkedIn, web scrape, or generic fetch. Install agent skill: npx @velinussage/locus-agent-skill add.
Inputs: tags, tier, limit, query, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
US parcels and building permits from public sources. No owner data. Pay per record or monthly plan.
US parcels, owners, sales, zoning rules, building permits and zoning cases.
Any US address: flood, HUD rent, county tax. Parcel zoning/STR rules: Nashville, Denver, Scottsdale.
US parcel records plus utilities, power, grid, environmental and logistics data by address or point.
Add one secure layer between your agents and this server.
