Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Small Business Intelligence by Brick & Mortar is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Free joined public records for small business and CRE: Twin Cities parcels, sales, licences
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http small-business-intelligence-by-brick-mortar-mcp https://brickandmortar.dev/mcp
# 2 — ask your agent for something these tools do
# data_source_atlas, what_we_have_for_you, twin_cities_lookup and 13 more
Small Business Intelligence by Brick & Mortar costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http small-business-intelligence-by-brick-mortar-mcp https://brickandmortar.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Given a real question about a local market or a specific property, returns a source-first RESEARCH PLAN: which public record actually settles the question, how to reach it directly (county parcel GIS, Census CBP/ACS/permits, BLS series, state registries, licences, inspections), what the answer will be worth, and what the public record cannot answer at all. Use it before researching a local market,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | The real question, in plain words — e.g. 'is there room for another coffee shop in Bend' or 'what did the building at 412 Main last sell for'. Not a dataset name; the point of this tool is to work out |
| place | string | yes | The specific geography — 'Hennepin County, MN', 'Wichita, KS', 'the 78704 ZIP'. State matters more than people expect: it decides whether sale prices exist at all. |
| already_tried | string | no | What you already looked at and what it failed to answer, if anything. Keeps the plan from re-recommending a dead end. |
The front door of brickandmortar.dev, as a tool. The platform is organised by WHO YOU ARE — an SBA lender, a business buyer, a landlord, a contractor, a journalist, a site selector, an appraiser, a city planner, 18 roles — and each role has a shelf of cards: joined public-records datasets for the Minneapolis–St. Paul metro, tools that read a file you bring against those records, a one-address look
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | no | A role id from the list this tool returns when called with no arguments — e.g. 'sba', 'buyer', 'landlord', 'press'. |
| who | string | no | If you do not know the id yet: what the person does, in their words — 'I underwrite restaurants', 'I'm buying a plumbing company'. Returns the closest roles to pick from. |
One address in the Minneapolis–St. Paul metro → what the public record says about that parcel, in one call: land use, build year, assessed value, last recorded sale, any MPCA contamination or storage-tank file, and the parcels that touch it with how many owners they have. Each field is a value or a miss WITH ITS REASON — 'the county records no build year' — never a blank. Free, no account, nothing
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | A street address in the seven-county Minneapolis–St. Paul metro. Include the city — 'Grand Ave' exists in several of them. |
Lists the public-records datasets Brick & Mortar publishes for the seven-county Minneapolis-St. Paul metro, with real row counts, column names, the filtered cuts available, and the counties each one actually covers. Free, no account. Call this FIRST to learn what can be answered, then call twin_cities_records to ask it. These are joined county and federal records — parcels and lot lines, recorded
| Parameter | Type | Required | Notes |
|---|---|---|---|
| about | string | no | Optional plain-words filter — 'sales', 'who owns it', 'contamination'. Matches dataset titles and subjects. Omit to list everything. |
Answers a question about the Minneapolis-St. Paul metro from joined public records — what a property sold for and when, who owns it and what else they hold, what shares its lot line, whether it has a contamination or storage-tank file, who is licensed to trade there, how the neighbourhood's census tract compares. Give an address to answer about one property and its surroundings; omit it to ask a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset | string | yes | A dataset id from twin_cities_datasets — e.g. 'sales', 'owners', 'adjacency'. |
| scope | string | no | A scope key from that dataset's scopes. Omit for the dataset's first cut. |
| address | string | no | A street address inside the seven-county metro, to answer about ONE property instead of the whole market. Include the city after a comma when the street name is common — 'Grand Ave' exists in several |
| within_ft | integer | no | Radius in feet around address. Default 5280 (one mile), capped at 26400. |
| columns | array | no | Column keys to return. Omit for the dataset's default set. |
Reads a document the person has — a P&L, a lease, a comp set, a schedule of locations, a member list, a story's addresses, a single claim — against the Minneapolis–St. Paul public record, and returns a table that cites the file behind every cell. This is the half of the platform the public record cannot do alone: their private file, our joined records, one answer. Free, no account. The document is
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | A tool slug from a what_we_have_for_you card where api_tool is true — e.g. 'pl', 'leasecheck', 'compgrade', 'claim-check', 'registercheck'. |
| text | string | no | The document as plain text — a pasted P&L, a lease, a list of addresses one per line, a comp table. Their content, untouched. For 'claim-check' use claim instead. |
| claim | string | no | For tool 'claim-check' only: the one sentence to check against the record, exactly as written. |
| context | object | no | — |
Returns a research framework, not the finished analysis: the procedure, output schema and quality rubric for a structured teardown of ONE named small business — digital presence, review signal, competitive position, pricing posture, visibility gaps, and prioritized, evidence-cited recommendations. Start here for any single-business question.. This tool fetches no data; the calling model runs the p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_name | string | yes | The business's name as it appears on its own signage/website, not a guess. |
| city_metro | string | yes | City + state/region, e.g. 'Saint Paul, MN' — narrows the trade area and comp set. |
| category | string | no | Category if known (e.g. 'nail salon', 'brewery taproom'). If omitted, step 2 of the procedure confirms it — don't guess from the name alone. |
Returns a research framework, not the finished analysis: the procedure, output schema and quality rubric for mapping the local competitive set for a category + metro — true competitors vs. adjacent players, a positioning matrix, and saturation signals.. This tool fetches no data; the calling model runs the procedure with its own web search and produces the result. Example invocations: - "Map the
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | yes | The business category/vertical, e.g. 'nail salon', 'brewery taproom'. |
| city_metro | string | yes | City + state/region defining the trade area, e.g. 'Denver, CO'. |
| radius_note | string | no | Optional — a specific radius or neighborhood if the default trade-area logic in the procedure shouldn't apply. |
Returns a research framework, not the finished analysis: the procedure, output schema and quality rubric for mining public reviews for signal — a complaint taxonomy, theme extraction, sentiment trajectory over time, the differentiators customers actually cite, and red flags for a buyer. It does not read any review itself.. This tool fetches no data; the calling model runs the procedure with its ow
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_name | string | yes | The business's name as it appears on its own signage/website. |
| city_metro | string | yes | City + state/region, e.g. 'Wichita, KS' — disambiguates same-named businesses. |
| category | string | no | Category if known — helps set expectations for review volume/velocity norms. |
Returns a research framework, not the finished audit: a scored checklist of what to check in a business's local search presence — map-pack factors, listing consistency, category selection, site fundamentals — and in what order. This tool reads no listing; the calling model runs the checks with its own web search. Example invocations: - "Run a local visibility audit on Fern & Fig Nail Bar in Cedar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_name | string | yes | The business's name as it appears on its own signage/website. |
| city_metro | string | yes | City + state/region, e.g. 'Aurora, CO'. |
| category | string | no | Category if known — narrows which map-pack searches are the right ones to check. |
Returns a research framework, not the finished analysis: the procedure, output schema and quality rubric for a defensible local pricing comparison within a category — how to normalize across differing service bundles, and what to do when competitors don't publish prices at all. It holds no prices itself.. This tool fetches no data; the calling model runs the procedure with its own web search and p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | yes | The business category/vertical, e.g. 'massage spa', 'full-service restaurant'. |
| city_metro | string | yes | City + state/region defining the comparison market, e.g. 'Wichita, KS'. |
| services | array | no | Specific services/items to benchmark if known (e.g. ['30-min massage', 'gel manicure']) — otherwise the procedure derives a comparable bundle. |
Pre-diligence framework for a business broker or buyer evaluating a target: SDE framing (why the discretionary-earnings figure, not net income or raw EBITDA, is the relevant number, and what typically gets added back), a category multiple range the model must research fresh and date-stamp (never a hardcoded table), a public-signal red-flag checklist run before any financials are shared, and a prio
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_name | string | yes | The target business's name. |
| city_metro | string | yes | City + state/region, e.g. 'Denver, CO'. |
| category | string | no | Category if known — determines the relevant SDE-multiple range. |
| asking_price | number | no | Listed asking price, if known — used to sanity-check against the multiple range, never to validate it. |
Returns a research framework, not the finished analysis: the procedure, output schema and quality rubric for a gap analysis of a category x metro — how to tell underserved demand, oversaturation and genuine whitespace apart using only public signals, for someone deciding whether/where to open, expand, or invest.. This tool fetches no data; the calling model runs the procedure with its own web sear
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | yes | The business category/vertical to scan for whitespace, e.g. 'coffee shop', 'massage spa'. |
| city_metro | string | yes | City + state/region defining the market, e.g. 'Aurora, CO'. |
Returns a research framework, not the finished analysis: the procedure, output schema and quality rubric for assembling results already in the conversation into one client-ready report — section order, executive-summary rules, evidence-citation standards, and tone guidance matched to the audience. The calling model writes the report; this tool returns only the structure.. This tool fetches no data
| Parameter | Type | Required | Notes |
|---|---|---|---|
| business_name | string | yes | The business the report is about. |
| audience | string | yes | Who will read this report — drives section order, tone, and what gets emphasized vs. cut. |
| completed_analyses | array | yes | The completed write-ups from any prior tool calls this session, to be assembled — not re-researched. |
Asks a person at Brick & Mortar to read the public record for them, for a fixed fee: a site screen for a lender or environmental consultant, a diligence packet on a deal, a register check across a landlord's portfolio, a weekly work route for a contractor. Call with no arguments to see the engagements, their prices and turnaround — those come from the live page, never from memory. Call with `engag
| Parameter | Type | Required | Notes |
|---|---|---|---|
| engagement | string | no | An engagement id from the list this tool returns when called empty — e.g. 'site-screen', 'diligence', 'register-check', 'route'. |
| who | string | no | What the person does, in their words. Required to file — it decides which records a person pulls. |
| string | no | Where a person should reply. VERBATIM — never guess, complete or correct an address. Required to file. | |
| detail | string | no | The site, deal, portfolio or route in their own words — addresses, the deadline, what they need to know. VERBATIM. |
Sends a feature request, a data request or a correction straight to the person who builds this server — free, no account, and it reaches a real inbox. Use it whenever this server falls short of what the user actually wanted: a question it cannot answer, a dataset or column it does not hold, a city or sector it does not cover, or an answer from one of these tools that looks wrong. Reaching a wall i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request | string | no | The person's own words, VERBATIM — do not summarise, rewrite or tidy them. Omit only if they have not said it yet; you will be asked for it. |
| kind | string | no | feature = make a tool do something it does not do. data = hold or expose a record we do not. correction = a tool here gave a wrong or misleading answer. Default: feature. |
| context | string | no | Your summary of what they were actually trying to do when they hit this. This one is yours to write. |
| subject | string | no | The city, sector, dataset or tool name this is about — 'Duluth', 'dental practices', 'twin_cities_records'. |
| reply_email | string | no | Optional, and only if they offer it. VERBATIM — never guess, complete or correct an address. Omit it rather than approximate it. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Small Business Intelligence by Brick & Mortar or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Small Business Intelligence by Brick & Mortar can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.