# com.precision-concretecoating/mcp (remote · app.precision-concretecoating.com)

Precision Concrete Coating MCP for services, estimates, scheduling, and business information.

- Trust score: 79/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `app.precision-concretecoating.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-precision-concretecoating-mcp/api-public-mcp.md), [page](https://verifymcp.io/servers/com-precision-concretecoating-mcp/api-public-mcp)

## Channel facts

- Endpoint: `https://app.precision-concretecoating.com/api/public/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4195 tokens (~127/item across 33 items; 33 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.precision-concretecoating/mcp server?

com.precision-concretecoating/mcp is a hosted endpoint at https://app.precision-concretecoating.com/api/public/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-precision-concretecoating-mcp 'https://app.precision-concretecoating.com/api/public/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-precision-concretecoating-mcp": {
      "url": "https://app.precision-concretecoating.com/api/public/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-precision-concretecoating-mcp": {
      "type": "http",
      "url": "https://app.precision-concretecoating.com/api/public/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-precision-concretecoating-mcp]
url = "https://app.precision-concretecoating.com/api/public/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-precision-concretecoating-mcp": {
      "type": "remote",
      "url": "https://app.precision-concretecoating.com/api/public/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-precision-concretecoating-mcp --url 'https://app.precision-concretecoating.com/api/public/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-precision-concretecoating-mcp:
    url: "https://app.precision-concretecoating.com/api/public/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-precision-concretecoating-mcp": {
      "Transport": "http",
      "Url": "https://app.precision-concretecoating.com/api/public/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-precision-concretecoating-mcp -t streamable-http -u 'https://app.precision-concretecoating.com/api/public/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-precision-concretecoating-mcp": {
      "type": "http",
      "url": "https://app.precision-concretecoating.com/api/public/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 79, 0)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 78, −1)

- [functional] Stability: pass → 0.90

### 2026-09-12 (score 79, 0)

- [security] Stability: 0.97 → pass

### 2026-09-11 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (33)

### `get_company_information` (~39 tokens)

Company information

Returns the approved public profile of Precision Concrete Coating: organization identity, owner, services and verified context records. Sourced from the Approved Knowledge database.

### `get_business_status` (~34 tokens)

Current business availability

Returns the current scheduling availability of the business plus the standard project turnaround statements. Reflects the Current Availability control in Approved Knowledge.

### `get_service_areas` (~31 tokens)

Service areas

Returns the approved service areas together with the headquarters, primary city, state, county and overall service region.

### `get_faq` (~32 tokens)

Frequently asked questions

Returns every approved public question-and-answer pair collected from Approved Knowledge, the Warranty Center, Installation Standards and Inspection Standards.

### `get_pricing` (~40 tokens)

Pricing information

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.

### `get_warranty` (~38 tokens)

Warranty information

Returns the approved public warranty knowledge graph: the derived summary plus coverage, exclusions, maintenance requirements, claims process, transfer policy and warranty FAQ records.

### `get_maintenance_care` (~71 tokens)

Maintenance and care instructions

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.

Input parameters:

- `section` (string): Restrict the response to a single care section, for example routine_cleaning.

### `get_business_operations` (~66 tokens)

Business operations and project lifecycle

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.

Input parameters:

- `section` (string): Restrict the response to a single lifecycle section, for example scheduling_process.

### `search_knowledge` (~106 tokens)

Search approved knowledge

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.

Input parameters:

- `limit` (integer): Maximum number of results (1–50). Defaults to 10.
- `module` (string): Restrict results to a single knowledge module.
- `q` (string): Search terms. When omitted the complete published record index is returned.

### `get_knowledge_relationships` (~92 tokens)

Knowledge graph relationships

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.

Input parameters:

- `relationship` (string): Filter to a single relationship type, e.g. mitigates, governed_by, verifies.
- `subject` (string): Filter to relationships whose subject or object matches this text.

### `explain_knowledge_reasoning` (~183 tokens)

Reason across the knowledge graph

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, semantic clusters and inverse relationships, and prunes weak branches automatically.

Input parameters:

- `goal` (string): Optional destination topic. Paths that reach it rank higher.
- `max_depth` (integer): Maximum hops per reasoning path, 1–6. Default 4.
- `max_paths` (integer): Maximum ranked paths returned, 1–12. Default 5.
- `question` (string): The question to reason about. Used to choose starting records and rank paths.
- `subject` (string): Optional explicit starting record title.

### `describe_platform` (~103 tokens)

Describe the platform

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 tool registry, so it never goes out of date.

Input parameters:

- `tool` (string): Return the documentation for a single registered tool instead of the whole catalog.

### `get_public_entities` (~141 tokens)

List public entities

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.

Input parameters:

- `entity_type` (string): Restrict the result to one public entity type.
- `limit` (integer): Maximum number of entities to return (1-200, default 50).
- `offset` (integer): Zero-based offset for pagination.
- `verification_status` (string): Restrict the result to a verification status. Published entities are always `verified`.

### `get_public_entity` (~77 tokens)

Get one public entity

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.

Input parameters:

- `id` (string, required): Canonical public id (`pcc:service/garage-floor-coatings`), canonical URI, slug or alias.

### `search_public_entities` (~93 tokens)

Search public entities

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.

Input parameters:

- `entity_type` (string): Restrict the search to one public entity type.
- `limit` (integer): Maximum number of matches (1-50, default 10).
- `q` (string, required): Search text.

### `get_entity_relationships` (~87 tokens)

Public entity relationships

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.

Input parameters:

- `entity` (string): Canonical public id, slug or alias to centre the graph on.
- `relationship` (string): Restrict the result to one relationship type.

### `get_standards` (~187 tokens)

List referenced technical standards

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 reference is not a certification or compliance claim.

Input parameters:

- `lifecycle` (string): Restrict to a lifecycle state.
- `limit` (integer): Maximum number of standards to return (1-200, default 50).
- `organization` (string): Restrict to one issuing organization (for example `ASTM`, `ICRI`, `OSHA`).
- `topic` (string): Restrict to standards tagged with a topic such as `moisture`, `surface-preparation`, `adhesion`, `safety`.

### `get_standard` (~86 tokens)

Get one referenced standard

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.

Input parameters:

- `id` (string, required): Canonical public id (`pcc:standard/astm-f2170`), standard number (`ASTM F2170`) or alias.

### `search_standards` (~81 tokens)

Search referenced standards

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.

Input parameters:

- `limit` (integer): Maximum matches (1-50, default 10).
- `q` (string, required): Search text.

### `get_record_standards` (~133 tokens)

Standards referenced by a Precision record

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.

Input parameters:

- `record` (string, required): Record slug or canonical public entity id (`pcc:preparation-method/diamond-grinding`).
- `record_kind` (string): Optional record family filter (`installation_standard`, `inspection_standard`, `failure_analysis`, `warranty_term`, `maintenance_record`, `knowledge_entry`).

### `get_standard_relationships` (~74 tokens)

Standard relationship edges

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.

Input parameters:

- `predicate` (string): Restrict to one predicate.
- `standard` (string): Canonical standard id or standard number to centre on.

### `get_estimate_intake_requirements` (~63 tokens)

Estimate intake requirements

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.

### `create_estimate_request` (~452 tokens)

Create an estimate request

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.

Input parameters:

- `approximate_square_feet` (integer): Approximate square feet
- `consent_to_contact` (boolean, required): Consent to be contacted
- `customer_name` (string, required): Customer name
- `customer_notes` (string): Customer notes
- `customer_statement` (string): The customer's own words for this step, stored verbatim as the evidence trail.
- `email` (string): Email
- `existing_surface` (string): Existing surface
- `external_reference_id` (string): External reference id
- `idempotency_key` (string): Optional client-supplied key. Repeating a call with the same key never duplicates work.
- `phone` (string, required): Phone
- `postal_code` (string): ZIP code
- `preferred_contact_method` (string): Preferred contact method
- `project_address` (string): Project street address
- `project_city` (string, required): Project city
- `project_state` (string, required): Project state
- `project_timeline` (string): Project timeline
- `project_type` (string, required): Project type
- `requested_system` (string): Requested coating system
- `scheduling_preferences` (object): 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.
- `source` (string): Source
- `surface_condition` (string): Surface condition
- `test_mode` (boolean): Diagnostics only. Marks the request as a synthetic smoke-test record: it is excluded from reporting, never holds real calendar availability and never notifies the office. Never set this for a real cu…
- `test_run_id` (string): Diagnostics only. Correlates a synthetic test record with one automated smoke-test run. Ignored unless test_mode is true.
- `timezone` (string): Timezone (IANA)

### `update_estimate_request` (~202 tokens)

Update an estimate request

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.

Input parameters:

- `customer_access_token` (string, required): 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): The customer's own words for this step, stored verbatim as the evidence trail.
- `idempotency_key` (string): Optional client-supplied key. Repeating a call with the same key never duplicates work.
- `request_id` (string, required): The request_id returned by create_estimate_request.
- `scheduling_preferences` (object): 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.
- `updates` (object, required): The fields to change.

### `get_estimate_request_status` (~127 tokens)

Get estimate request status

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.

Input parameters:

- `customer_access_token` (string, required): 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.
- `request_id` (string, required): The request_id returned by create_estimate_request.

### `submit_estimate_for_review` (~204 tokens)

Submit for review

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 pricing, scope or a time.

Input parameters:

- `customer_access_token` (string, required): 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): The customer's own words for this step, stored verbatim as the evidence trail.
- `idempotency_key` (string): Optional client-supplied key. Repeating a call with the same key never duplicates work.
- `request_id` (string, required): The request_id returned by create_estimate_request.

### `request_estimate_appointment` (~255 tokens)

Request an on-site walkthrough

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.

Input parameters:

- `customer_access_token` (string, required): 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_authorized_scheduling` (boolean, required): Must be true. Confirms the customer explicitly asked for an appointment to be scheduled.
- `idempotency_key` (string): Optional client-supplied key. Repeating a call with the same key never duplicates work.
- `request_id` (string, required): The request_id returned by create_estimate_request.
- `scheduling_preferences` (object): 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): IANA timezone for all appointment dates and times, e.g. America/Chicago. Defaults to America/Chicago.

### `confirm_estimate_appointment` (~174 tokens)

Confirm the proposed walkthrough

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.

Input parameters:

- `customer_access_token` (string, required): 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_confirmation` (boolean, required): Must be true. The customer accepted the proposed time.
- `idempotency_key` (string): Optional client-supplied key. Repeating a call with the same key never duplicates work.
- `proposal_id` (string, required): The proposal_id returned with the proposed appointment.
- `request_id` (string, required): The request_id returned by create_estimate_request.

### `request_appointment_reschedule` (~242 tokens)

Request a different walkthrough time

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.

Input parameters:

- `customer_access_token` (string, required): 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_authorized_reschedule` (boolean, required): Must be true. The customer asked to reschedule.
- `idempotency_key` (string): Optional client-supplied key. Repeating a call with the same key never duplicates work.
- `new_scheduling_preferences` (object): 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.
- `reason` (string): Why the customer needs a different time.
- `request_id` (string, required): The request_id returned by create_estimate_request.
- `timezone` (string): IANA timezone for all appointment dates and times, e.g. America/Chicago. Defaults to America/Chicago.

### `cancel_estimate_appointment` (~165 tokens)

Cancel the walkthrough

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.

Input parameters:

- `customer_access_token` (string, required): 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_authorized_cancellation` (boolean, required): Must be true. The customer asked to cancel.
- `idempotency_key` (string): Optional client-supplied key. Repeating a call with the same key never duplicates work.
- `reason` (string): Why the customer is cancelling.
- `request_id` (string, required): The request_id returned by create_estimate_request.

### `get_next_estimate_question` (~104 tokens)

Next best intake question

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.

Input parameters:

- `customer_access_token` (string, required): 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.
- `request_id` (string, required): The request_id returned by create_estimate_request.

### `attach_estimate_photos` (~164 tokens)

Attach photos

Attaches photo references (public https URLs) to an estimate request. Photos support the estimator's preparation; they never replace the on-site inspection.

Input parameters:

- `customer_access_token` (string, required): 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.
- `fields` (object): Legacy internal-schema field bag. Prefer the top-level public fields; unknown keys are rejected. Never include pricing.
- `idempotency_key` (string): Optional client-supplied key. Repeating a call with the same key never duplicates work.
- `photos` (array, required): Photo references to attach.
- `request_id` (string, required): The request_id returned by create_estimate_request.

### `analyze_estimate_photos` (~133 tokens)

Observe attached photos

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.

Input parameters:

- `customer_access_token` (string, required): 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): Optional client-supplied key. Repeating a call with the same key never duplicates work.
- `request_id` (string, required): The request_id returned by create_estimate_request.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-precision-concretecoating-mcp/api-public-mcp#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 79
- 2026-09-22: 79
- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 75
- 2026-09-03: 75
- 2026-09-02: 74
- 2026-09-01: 74
- 2026-08-31: 74
- 2026-08-30: 73
- 2026-08-29: 73
- 2026-08-28: 72
- 2026-08-27: 72
- 2026-08-26: 71

## Common questions

### What is the com.precision-concretecoating/mcp server?

com.precision-concretecoating/mcp is listed in the public MCP registry as com.precision-concretecoating/mcp. Precision Concrete Coating MCP for services, estimates, scheduling, and business information. This page covers its hosted endpoint (https://app.precision-concretecoating.com/api/public/mcp).

### Is the com.precision-concretecoating/mcp server safe to use?

com.precision-concretecoating/mcp scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the com.precision-concretecoating/mcp server expose?

com.precision-concretecoating/mcp exposes 33 tools: get_company_information, get_business_status, get_service_areas, get_faq, get_pricing, and 28 more. Their descriptions and schemas cost roughly 4,079 tokens of context every time the server is loaded.

### Does the com.precision-concretecoating/mcp server require authentication?

No. We connected to com.precision-concretecoating/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.precision-concretecoating/mcp server still maintained?

com.precision-concretecoating/mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://app.precision-concretecoating.com/api/public/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-precision-concretecoating-mcp/api-public-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-precision-concretecoating-mcp/api-public-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-precision-concretecoating-mcp/api-public-mcp