Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.precision-concretecoating/mcp

REMOTE · APP.PRECISION-CONCRETECOATING.COM

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

0 this week 86 Trust /100

Last scanned (18 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 0
    • Stability: pass → 0.90 functional
  • 12 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://app.precision-concretecoating.com/api/public/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.precision-concretecoating.com CN=WE1,O=Google Trust Services,C=US 15 Oct 2026 14 Jan 2027 ECDSA 256 ECDSA-SHA256 c02dc1e3b2d3d1a31370a1cc44f4c6eb
SANs: app.precision-concretecoating.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.precision-concretecoating.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
precision-concretecoating.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.precision-concretecoating.com/api/public/mcp Verified 200
http (plaintext) http://app.precision-concretecoating.com/api/public/mcp HTTPS enforced 301 https://app.precision-concretecoating.com/api/public/mcp
MCP tools · 33 exposed · ~4,079 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_estimate_photos ~133

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.

NameTypeReqDescription
customer_access_tokenstringyesThe 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_keystring–Optional client-supplied key. Repeating a call with the same key never duplicates work.
request_idstringyesThe request_id returned by create_estimate_request.

No output schema declared.

No examples provided.

attach_estimate_photos ~164

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

NameTypeReqDescription
customer_access_tokenstringyesThe 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.
fieldsobject–Legacy internal-schema field bag. Prefer the top-level public fields; unknown keys are rejected. Never include pricing.
idempotency_keystring–Optional client-supplied key. Repeating a call with the same key never duplicates work.
photosarrayyesPhoto references to attach.
request_idstringyesThe request_id returned by create_estimate_request.

No output schema declared.

No examples provided.

cancel_estimate_appointment ~165

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.

NameTypeReqDescription
customer_access_tokenstringyesThe 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_cancellationbooleanyesMust be true. The customer asked to cancel.
idempotency_keystring–Optional client-supplied key. Repeating a call with the same key never duplicates work.
reasonstring–Why the customer is cancelling.
request_idstringyesThe request_id returned by create_estimate_request.

No output schema declared.

No examples provided.

confirm_estimate_appointment ~174

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.

NameTypeReqDescription
customer_access_tokenstringyesThe 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_confirmationbooleanyesMust be true. The customer accepted the proposed time.
idempotency_keystring–Optional client-supplied key. Repeating a call with the same key never duplicates work.
proposal_idstringyesThe proposal_id returned with the proposed appointment.
request_idstringyesThe request_id returned by create_estimate_request.

No output schema declared.

No examples provided.

create_estimate_request ~452

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.

NameTypeReqDescription
approximate_square_feetinteger–Approximate square feet
consent_to_contactbooleanyesConsent to be contacted
customer_namestringyesCustomer name
customer_notesstring–Customer notes
customer_statementstring–The customer's own words for this step, stored verbatim as the evidence trail.
emailstring–Email
existing_surfacestring–Existing surface
external_reference_idstring–External reference id
idempotency_keystring–Optional client-supplied key. Repeating a call with the same key never duplicates work.
phonestringyesPhone
postal_codestring–ZIP code
preferred_contact_methodstring–Preferred contact method
project_addressstring–Project street address
project_citystringyesProject city
project_statestringyesProject state
project_timelinestring–Project timeline
project_typestringyesProject type
requested_systemstring–Requested coating system
scheduling_preferencesobject–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.
sourcestring–Source
surface_conditionstring–Surface condition
test_modeboolean–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_idstring–Diagnostics only. Correlates a synthetic test record with one automated smoke-test run. Ignored unless test_mode is true.
timezonestring–Timezone (IANA)

No output schema declared.

No examples provided.

describe_platform ~103

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.

NameTypeReqDescription
toolstring–Return the documentation for a single registered tool instead of the whole catalog.

No output schema declared.

No examples provided.

explain_knowledge_reasoning ~183

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.

NameTypeReqDescription
goalstring–Optional destination topic. Paths that reach it rank higher.
max_depthinteger–Maximum hops per reasoning path, 1–6. Default 4.
max_pathsinteger–Maximum ranked paths returned, 1–12. Default 5.
questionstring–The question to reason about. Used to choose starting records and rank paths.
subjectstring–Optional explicit starting record title.

No output schema declared.

No examples provided.

get_business_operations ~66

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.

NameTypeReqDescription
sectionstring–Restrict the response to a single lifecycle section, for example scheduling_process.

No output schema declared.

No examples provided.

get_business_status ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_company_information ~39

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_entity_relationships ~87

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.

NameTypeReqDescription
entitystring–Canonical public id, slug or alias to centre the graph on.
relationshipstring–Restrict the result to one relationship type.

No output schema declared.

No examples provided.

get_estimate_intake_requirements ~63

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_estimate_request_status ~127

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.

NameTypeReqDescription
customer_access_tokenstringyesThe 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_idstringyesThe request_id returned by create_estimate_request.

No output schema declared.

No examples provided.

get_faq ~32

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_knowledge_relationships ~92

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.

NameTypeReqDescription
relationshipstring–Filter to a single relationship type, e.g. mitigates, governed_by, verifies.
subjectstring–Filter to relationships whose subject or object matches this text.

No output schema declared.

No examples provided.

get_maintenance_care ~71

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.

NameTypeReqDescription
sectionstring–Restrict the response to a single care section, for example routine_cleaning.

No output schema declared.

No examples provided.

get_next_estimate_question ~104

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.

NameTypeReqDescription
customer_access_tokenstringyesThe 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_idstringyesThe request_id returned by create_estimate_request.

No output schema declared.

No examples provided.

get_pricing ~40

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_public_entities ~141

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.

NameTypeReqDescription
entity_typestring–Restrict the result to one public entity type.
limitinteger–Maximum number of entities to return (1-200, default 50).
offsetinteger–Zero-based offset for pagination.
verification_statusstring–Restrict the result to a verification status. Published entities are always `verified`.

No output schema declared.

No examples provided.

get_public_entity ~77

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.

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

No output schema declared.

No examples provided.

get_record_standards ~133

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.

NameTypeReqDescription
recordstringyesRecord slug or canonical public entity id (`pcc:preparation-method/diamond-grinding`).
record_kindstring–Optional record family filter (`installation_standard`, `inspection_standard`, `failure_analysis`, `warranty_term`, `maintenance_record`, `knowledge_entry`).

No output schema declared.

No examples provided.

get_service_areas ~31

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_standard ~86

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.

NameTypeReqDescription
idstringyesCanonical public id (`pcc:standard/astm-f2170`), standard number (`ASTM F2170`) or alias.

No output schema declared.

No examples provided.

get_standard_relationships ~74

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.

NameTypeReqDescription
predicatestring–Restrict to one predicate.
standardstring–Canonical standard id or standard number to centre on.

No output schema declared.

No examples provided.

get_standards ~187

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.

NameTypeReqDescription
lifecyclestring–Restrict to a lifecycle state.
limitinteger–Maximum number of standards to return (1-200, default 50).
organizationstring–Restrict to one issuing organization (for example `ASTM`, `ICRI`, `OSHA`).
topicstring–Restrict to standards tagged with a topic such as `moisture`, `surface-preparation`, `adhesion`, `safety`.

No output schema declared.

No examples provided.

get_warranty ~38

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_appointment_reschedule ~242

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.

NameTypeReqDescription
customer_access_tokenstringyesThe 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_reschedulebooleanyesMust be true. The customer asked to reschedule.
idempotency_keystring–Optional client-supplied key. Repeating a call with the same key never duplicates work.
new_scheduling_preferencesobject–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.
reasonstring–Why the customer needs a different time.
request_idstringyesThe request_id returned by create_estimate_request.
timezonestring–IANA timezone for all appointment dates and times, e.g. America/Chicago. Defaults to America/Chicago.

No output schema declared.

No examples provided.

request_estimate_appointment ~255

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.

NameTypeReqDescription
customer_access_tokenstringyesThe 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_schedulingbooleanyesMust be true. Confirms the customer explicitly asked for an appointment to be scheduled.
idempotency_keystring–Optional client-supplied key. Repeating a call with the same key never duplicates work.
request_idstringyesThe request_id returned by create_estimate_request.
scheduling_preferencesobject–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.
timezonestring–IANA timezone for all appointment dates and times, e.g. America/Chicago. Defaults to America/Chicago.

No output schema declared.

No examples provided.

search_knowledge ~106

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.

NameTypeReqDescription
limitinteger–Maximum number of results (1–50). Defaults to 10.
modulestring–Restrict results to a single knowledge module.
qstring–Search terms. When omitted the complete published record index is returned.

No output schema declared.

No examples provided.

search_public_entities ~93

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.

NameTypeReqDescription
entity_typestring–Restrict the search to one public entity type.
limitinteger–Maximum number of matches (1-50, default 10).
qstringyesSearch text.

No output schema declared.

No examples provided.

search_standards ~81

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.

NameTypeReqDescription
limitinteger–Maximum matches (1-50, default 10).
qstringyesSearch text.

No output schema declared.

No examples provided.

submit_estimate_for_review ~204

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.

NameTypeReqDescription
customer_access_tokenstringyesThe 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_statementstring–The customer's own words for this step, stored verbatim as the evidence trail.
idempotency_keystring–Optional client-supplied key. Repeating a call with the same key never duplicates work.
request_idstringyesThe request_id returned by create_estimate_request.

No output schema declared.

No examples provided.

update_estimate_request ~202

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.

NameTypeReqDescription
customer_access_tokenstringyesThe 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_statementstring–The customer's own words for this step, stored verbatim as the evidence trail.
idempotency_keystring–Optional client-supplied key. Repeating a call with the same key never duplicates work.
request_idstringyesThe request_id returned by create_estimate_request.
scheduling_preferencesobject–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.
updatesobjectyesThe fields to change.

No output schema declared.

No examples provided.

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.

remote · app.precision-concretecoating.com

# add to Claude Code
claude mcp add --transport http com-precision-concretecoating-mcp 'https://app.precision-concretecoating.com/api/public/mcp'
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 86 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.precision-concretecoating/mcp server?

VerifyMCP ran 13 checks on com.precision-concretecoating/mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.