Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Precision Concretecoating 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.
33
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Precision Concrete Coating MCP for services, estimates, scheduling, and business information.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http precision-concretecoating-mcp https://app.precision-concretecoating.com/api/public/mcp
# 2 — ask your agent for something these tools do
# get_company_information, get_business_status, get_service_areas and 30 more
Precision Concretecoating costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
PCAll 1 server
precision-concretecoating1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 precision-concretecoating-mcp https://app.precision-concretecoating.com/api/public/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
33 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.
Returns the approved public profile of Precision Concrete Coating: organization identity, owner, services and verified context records. Sourced from the Approved Knowledge database.
No parameter schema on file.
Returns the current scheduling availability of the business plus the standard project turnaround statements. Reflects the Current Availability control in Approved Knowledge.
No parameter schema on file.
Returns the approved service areas together with the headquarters, primary city, state, county and overall service region.
No parameter schema on file.
Returns every approved public question-and-answer pair collected from Approved Knowledge, the Warranty Center, Installation Standards and Inspection Standards.
No parameter schema on file.
Returns approved public pricing statements and the services they apply to. No quoted amounts are generated: Precision Concrete Coating prices every project after an on-site inspection.
No parameter schema on file.
Returns the approved public warranty knowledge graph: the derived summary plus coverage, exclusions, maintenance requirements, claims process, transfer policy and warranty FAQ records.
No parameter schema on file.
Returns the approved public Maintenance & Care Center knowledge: how coated concrete should be cleaned, maintained, protected and inspected, including recommended methods, frequencies, prohibited products, common mistakes and warranty impact.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | string | no | Restrict the response to a single care section, for example routine_cleaning. |
Returns the approved public Business Operations & Project Lifecycle knowledge: how projects are quoted, scheduled, communicated, installed, completed, documented and supported. Company process knowledge, not coating science.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | string | no | Restrict the response to a single lifecycle section, for example scheduling_process. |
Full-text style search across every published Approved Knowledge record — company, services, service areas, warranty, installation, inspection, failure-analysis, maintenance and business operations knowledge. Omit the query to receive the full index.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | Search terms. When omitted the complete published record index is returned. |
| module | string | no | Restrict results to a single knowledge module. |
| limit | integer | no | Maximum number of results (1–50). Defaults to 10. |
Returns the directional relationships between published Precision knowledge records — for example which installation standard mitigates which coating failure, or which warranty covers which service. Only relationships whose records are both approved and public are returned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | no | Filter to relationships whose subject or object matches this text. |
| relationship | string | no | Filter to a single relationship type, e.g. mitigates, governed_by, verifies. |
Answers a question by traversing the published knowledge graph and returning ranked reasoning paths instead of disconnected records. Each path is an ordered chain of relationships with a path score, a path confidence, the supporting evidence, the relationship types used and a plain-language explanation of every transition. Traversal respects relationship weight, evidence strength, concept ontology
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | no | The question to reason about. Used to choose starting records and rank paths. |
| subject | string | no | Optional explicit starting record title. |
| goal | string | no | Optional destination topic. Paths that reach it rank higher. |
| max_depth | integer | no | Maximum hops per reasoning path, 1–6. Default 4. |
| max_paths | integer | no | Maximum ranked paths returned, 1–12. Default 5. |
Self-documenting endpoint. Returns everything an AI agent or developer needs to use Precision OS correctly: platform identity and versions, authentication and read-only status, transports and capabilities, the complete auto-generated documentation for every registered tool, plus best practices, limitations, security model, privacy guarantees and data freshness. Generated dynamically from the live
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | no | Return the documentation for a single registered tool instead of the whole catalog. |
Returns the approved Public Entity Layer: every organization, person, service, service area, coating system, preparation method, trust signal, expertise and community involvement record Precision publishes, each with a stable canonical id, aliases, verification status, review metadata and sameAs references. Internal identifiers are never exposed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity_type | string | no | Restrict the result to one public entity type. |
| verification_status | string | no | Restrict the result to a verification status. Published entities are always verified. |
| limit | integer | no | Maximum number of entities to return (1-200, default 50). |
| offset | integer | no | Zero-based offset for pagination. |
Returns a single published public entity by canonical id, canonical URI, slug or alias, together with its incoming and outgoing approved relationships and the schema.org JSON-LD node generated from the same record.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Canonical public id (pcc:service/garage-floor-coatings), canonical URI, slug or alias. |
Ranked search over published public entity names, aliases, canonical ids and descriptions. Use it to resolve a free-form mention ("Conroe", "flake floor") to a stable canonical Precision entity id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | Search text. |
| entity_type | string | no | Restrict the search to one public entity type. |
| limit | integer | no | Maximum number of matches (1-50, default 10). |
Returns the approved relationship edges of the public entity graph, optionally filtered to one entity or one relationship type. Every edge references stable canonical entity ids on both sides; edges that touch an unpublished record are never returned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | no | Canonical public id, slug or alias to centre the graph on. |
| relationship | string | no | Restrict the result to one relationship type. |
Returns the approved external technical standards Precision's published knowledge references — ASTM, ICRI, ACI, ANSI, OSHA, EPA and manufacturer technical documents. Each record carries the standard number, official title, issuing organization, edition, official source URL, an original scope summary and lifecycle status. Reference metadata only: the text of a standard is never reproduced, and a re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| organization | string | no | Restrict to one issuing organization (for example ASTM, ICRI, OSHA). |
| topic | string | no | Restrict to standards tagged with a topic such as moisture, surface-preparation, adhesion, safety. |
| lifecycle | string | no | Restrict to a lifecycle state. |
| limit | integer | no | Maximum number of standards to return (1-200, default 50). |
Returns a single referenced standard by canonical public id, standard number or alias, with its provenance (official source URL, edition, last verified date), lifecycle warnings, supersession chain and the Precision records that reference it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Canonical public id (pcc:standard/astm-f2170), standard number (ASTM F2170) or alias. |
Ranked search over standard numbers, titles, aliases, topics and scope summaries. Use it to resolve a free-form mention such as "in-situ RH test" or "CSP profile" to the canonical standard Precision references.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | Search text. |
| limit | integer | no | Maximum matches (1-50, default 10). |
Returns the approved standards that a specific Precision knowledge record references, with the relationship predicate (tested_per, guided_by, measured_by, references, …) and an applicability summary explaining why the standard is relevant. Answers "what is this practice based on?" with citable provenance.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| record | string | yes | Record slug or canonical public entity id (pcc:preparation-method/diamond-grinding). |
| record_kind | string | no | Optional record family filter (installation_standard, inspection_standard, failure_analysis, warranty_term, maintenance_record, knowledge_entry). |
Returns the approved edges that connect Precision entities and knowledge records to referenced standards, including the predicate and the applicability summary. Use it to traverse the provenance layer of the knowledge graph.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| standard | string | no | Canonical standard id or standard number to centre on. |
| predicate | string | no | Restrict to one predicate. |
Read-only discovery. Returns every field the public estimate workflow accepts, which are required, the allowed enum values, the workflow states, the scheduling model and the guardrails. Call this first so no field name, enum value or state is ever guessed.
No parameter schema on file.
Creates a governed estimate request and returns a request_id plus a one-time customer_access_token. Required to create: customer_name, phone, project_city, project_state, project_type, consent_to_contact. Additionally required before submit_estimate_for_review: approximate_square_feet — these may be collected turn by turn with update_estimate_request. Every other field is genuinely optional.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_name | string | yes | Customer name |
| phone | string | yes | Phone |
| string | no | ||
| project_address | string | no | Project street address |
| project_city | string | yes | Project city |
| project_state | string | yes | Project state |
| postal_code | string | no | ZIP code |
| project_type | string | yes | Project type |
| approximate_square_feet | integer | no | Approximate square feet |
| existing_surface | string | no | Existing surface |
| surface_condition | string | no | Surface condition |
| requested_system | string | no | Requested coating system |
| project_timeline | string | no | Project timeline |
| preferred_contact_method | string | no | Preferred contact method |
| customer_notes | string | no | Customer notes |
| consent_to_contact | boolean | yes | Consent to be contacted |
| timezone | string | no | Timezone (IANA) |
| source | string | no | Source |
| external_reference_id | string | no | External reference id |
| scheduling_preferences | object | no | What the customer prefers. Precision's internal JoJo scheduler decides the actual time from authorized calendar availability — no external caller ever reads or writes the calendar directly. |
Token-scoped update. Adds or corrects customer-provided details on an existing request. Values are validated against the shared schema and every change is audited with the calling channel.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by create_estimate_request. |
| customer_access_token | string | yes | The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued. |
| updates | object | yes | The fields to change. |
| scheduling_preferences | object | no | What the customer prefers. Precision's internal JoJo scheduler decides the actual time from authorized calendar availability — no external caller ever reads or writes the calendar directly. |
| customer_statement | string | no | The customer's own words for this step, stored verbatim as the evidence trail. |
| idempotency_key | string | no | Optional client-supplied key. Repeating a call with the same key never duplicates work. |
Returns the public projection of one estimate request: the workflow state, a customer-friendly status, what information is still missing, the recommended next question and the appointment (date, time window, timezone and confirmation status) if one exists. No internal notes, staff data or calendar availability is ever included.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by create_estimate_request. |
| customer_access_token | string | yes | The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued. |
Submits the request to Precision's internal JoJo review layer and the office, creating or linking the customer record and notifying staff. Every field in required_to_submit must be present first (customer_name, phone, project_city, project_state, project_type, approximate_square_feet, consent_to_contact), along with a contact method and consent. Submitting requests a visit; it does not confirm pri
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by create_estimate_request. |
| customer_access_token | string | yes | The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued. |
| customer_statement | string | no | The customer's own words for this step, stored verbatim as the evidence trail. |
| idempotency_key | string | no | Optional client-supplied key. Repeating a call with the same key never duplicates work. |
Asks Precision's internal JoJo scheduler to reserve an authorized on-site walkthrough that fits the customer's stated preferences. The caller never sees or selects calendar availability: JoJo reads the private calendar, applies the preferences and returns exactly one proposed time awaiting customer confirmation. If nothing matches, the response says so and asks for wider preferences.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by create_estimate_request. |
| customer_access_token | string | yes | The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued. |
| scheduling_preferences | object | no | What the customer prefers. Precision's internal JoJo scheduler decides the actual time from authorized calendar availability — no external caller ever reads or writes the calendar directly. |
| timezone | string | no | IANA timezone for all appointment dates and times, e.g. America/Chicago. Defaults to America/Chicago. |
| customer_authorized_scheduling | boolean | yes | Must be true. Confirms the customer explicitly asked for an appointment to be scheduled. |
| idempotency_key | string | no | Optional client-supplied key. Repeating a call with the same key never duplicates work. |
Confirms the appointment Precision proposed, using the proposal_id from the proposal. Only an unexpired proposal on this request can be confirmed. On success the walkthrough is booked, the office is notified and preparation instructions are returned.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by create_estimate_request. |
| customer_access_token | string | yes | The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued. |
| proposal_id | string | yes | The proposal_id returned with the proposed appointment. |
| customer_confirmation | boolean | yes | Must be true. The customer accepted the proposed time. |
| idempotency_key | string | no | Optional client-supplied key. Repeating a call with the same key never duplicates work. |
Asks internal JoJo for a different walkthrough time using new preferences. The existing hold stays in place until JoJo replaces it, so a duplicate appointment is never created and the customer is never left without one.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by create_estimate_request. |
| customer_access_token | string | yes | The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued. |
| new_scheduling_preferences | object | no | What the customer prefers. Precision's internal JoJo scheduler decides the actual time from authorized calendar availability — no external caller ever reads or writes the calendar directly. |
| timezone | string | no | IANA timezone for all appointment dates and times, e.g. America/Chicago. Defaults to America/Chicago. |
| reason | string | no | Why the customer needs a different time. |
| customer_authorized_reschedule | boolean | yes | Must be true. The customer asked to reschedule. |
| idempotency_key | string | no | Optional client-supplied key. Repeating a call with the same key never duplicates work. |
Cancels a proposed or confirmed walkthrough, releases the held time back to Precision and notifies the office. The estimate request itself stays open, so a new appointment can be requested later.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by create_estimate_request. |
| customer_access_token | string | yes | The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued. |
| reason | string | no | Why the customer is cancelling. |
| customer_authorized_cancellation | boolean | yes | Must be true. The customer asked to cancel. |
| idempotency_key | string | no | Optional client-supplied key. Repeating a call with the same key never duplicates work. |
Returns the single highest-value question still unanswered, in natural language, along with why it matters. Ask one question at a time and send the answer back through update_estimate_request.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by create_estimate_request. |
| customer_access_token | string | yes | The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued. |
Attaches photo references (public https URLs) to an estimate request. Photos support the estimator's preparation; they never replace the on-site inspection.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by create_estimate_request. |
| customer_access_token | string | yes | The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued. |
| photos | array | yes | Photo references to attach. |
| fields | object | no | Legacy internal-schema field bag. Prefer the top-level public fields; unknown keys are rejected. Never include pricing. |
| idempotency_key | string | no | Optional client-supplied key. Repeating a call with the same key never duplicates work. |
Runs visual observation over any unreviewed photos. Returns non-diagnostic observations from a fixed vocabulary with confidence values. Observations are impressions only and are always marked as requiring field verification.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | The request_id returned by create_estimate_request. |
| customer_access_token | string | yes | The one-time customer_access_token returned by create_estimate_request. Required with request_id for every follow-up call. Stored hashed at rest and never re-issued. |
| idempotency_key | string | no | Optional client-supplied key. Repeating a call with the same key never duplicates work. |
Free
$0 forever
- 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 Precision Concretecoating or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
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. 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 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Precision Concretecoating can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.