The Service Marketing Guys Audit

com.theservicemarketingguys由 theservicemarketingguys.com 發布官方發布者v0.1.0更新於 Oct 24, 2026

Read-only audit of any local service business, Open Service Profile conformance first.

已驗證Streamable HTTP可網頁執行開發者工具商業與電商

概覽

AI 產生的概覽

一個唯讀稽核端點，用來檢查在地服務業者的 Open Service Profile 清單是否符合 OSP 規範草案。

可以做什麼
讀取業者發布的 Open Service Profile 清單，並依規範草案的結構與限制檢查其一致性，回報符合情況與缺漏項目。該檔案本身描述業者身分、地點與營業時間、服務、郵遞區號涵蓋範圍及預約政策。相關規範定義了六個工具，用於讀取檔案、檢查涵蓋範圍、檢查可用性並送出預約請求，但本清單未列出任何工具。
適用情境
適合在助手要依賴某在地服務業者的機器可讀檔案之前，先確認其格式正確且符合規範；也適合在準備發布檔案時自我檢查。
執行需求
供應商網站上的遠端 streamable HTTP 端點；未宣告身分驗證、環境變數或標頭。受稽核的檔案須由該業者發布。
安裝前請注意
清單未宣告任何工具，因此此端點實際提供的能力無法從清單得知。該規範為草案（v0.1），可能變更。README 另述一個本機產生器，可讀取業者網站，並可選擇使用 GOOGLE_PLACES_API_KEY 讀取其 Google 商家資訊；該產生器不屬於此遠端端點。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 The Service Marketing Guys Audit，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.theservicemarketingguys%2Faudit/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "the-service-marketing-guys-audit": {
      "type": "http",
      "url": "https://www.theservicemarketingguys.com/api/audit-mcp"
    }
  }
}

README

Open Service Profile

Open Service Profile (OSP) is a machine-readable description of a local service business, published at /.well-known/open-service-profile, that tells AI agents what the business does, where it works, when it is open, and how to request a booking.

It covers dispatch-based and shop-based trades: HVAC, plumbing, electrical, landscaping, auto repair, marine repair, and similar. The manifest carries identity, locations and hours, services, ZIP coverage, and a booking policy. Six tools over the Model Context Protocol let an agent read the profile, check coverage, check availability, and submit a booking request. A booking request is a request, never a confirmation; the specification fixes that semantic so an agent cannot tell a customer an appointment exists when it does not.

Status

Draft v0.1, published 2026-09-07 and revised 2026-09-09 (0.1.0-draft.4, a text-only revision). The draft is stable enough to implement. Changes before 1.0 arrive as versioned releases with a changelog; see CONTRIBUTING.md for how changes are decided.

Specification

The Markdown in spec/ is the source text. The website is the canonical rendering, and citations should use the versioned URL above.

Maintainer

The Service Marketing Guys, an EasyServe company. Issues and pull requests are welcome here.

What is in this repository

spec/  v0.1.md                         specification source textschemas/v0.1/  manifest.schema.json            Appendix A, the manifest document  tools/    tools-common.schema.json      shared definitions for tool schemas    <tool>.input.schema.json      one per tool, Appendix B    <tool>.output.schema.json     one per tool, Appendix Bexamples/v0.1/  hvac-two-locations.json         Appendix C.1  auto-repair-single-location.json  Appendix C.2  marine-repair-yard.json         Appendix C.3  hvac-two-locations.level1.jsonld  Appendix C.4, Level 1 JSON-LD for the C.1 businessscripts/  validate-examples.mjs           validates the examples against the manifest schema and the Appendix A constraints  extract-from-spec.mjs           regenerates schemas/ and examples/ from spec/v0.1.mdbin/  open-service-profile.mjs        the generator CLI (npx open-service-profile init <url>)src/  validate.mjs                    the examples script's and the CLI's validator, a thin call into the generated core  crawl.mjs                       the CLI's bounded site crawl: pinned connections, private-address policy, host fence  places.mjs                      optional Google listing lookup (your own key)  core/                           GENERATED generator core; source of truth is the maintainer's TypeScripttests/  cli.test.mjs                    node --test; fixture sites under tests/fixtures/

Every tool output schema is oneOf a success shape and an error shape. The error shape is tools-common.schema.json#/$defs/ErrorResult, constrained in each tool's schema to that tool's error codes.

Run npm run validate to check the examples. There are no dependencies.

Generate your profile

The repository also ships a small command-line tool that drafts a business's Open Service Profile from its own website. It also writes the business's llms.txt. Node 20 or newer, no dependencies.

npx open-service-profile init example.com

It reads up to twelve pages (home, contact, schedule, about, then service and location pages from the sitemap) and writes five files into ./open-service-profile/:

filehost it at
open-service-profile.json/.well-known/open-service-profile, served as application/json with Access-Control-Allow-Origin: *
llms.txt/llms.txt
llms-full.txt/llms-full.txt (every fact with the page it was read from, and how each derived value was produced)
robots-ai-section.txtmerge into /robots.txt (a commented template until you answer the two crawler questions)
jsonld.htmlpaste inside <head> on the home page (the Level 1 JSON-LD: a LocalBusiness node with a ScheduleAction)

One rule governs every line: a fact the pages do not state becomes a # TODO: line, never a plausible default. No price, hour, service, or certification is invented; a service is listed only from a page that was actually read; ratings or review counts found in the page markup are never copied (the standard forbids them). The draft claims Level 1 only when every Level 1 fact is established, no value is an inference from wording, the manifest validates against Appendix A, and the home page already carries the Level 1 JSON-LD; it never claims Level 2, because the tool builds no MCP server.

Some things no website states, so the tool asks rather than guess: the booking policy (earliest day you accept requests for, weekend requests, emergency or after-hours availability, how you confirm), the two robots.txt choices (may AI assistants read your pages; may they be used for training), and, only when the pages do not settle them, the service model (one recognized trade settles it), the primary location (one location is primary by definition), and the time zone (a state in one zone settles it). Pass them as flags, or run in a terminal and answer the questions; unanswered fields stay TODO lines. The three standard windows are written by id only, with no clock times.

npx open-service-profile init example.com --min-days-ahead 1 --weekend-requests saturday_only --emergency no --contact-methods call,email --ai-read yes --ai-train no

Options:

  • --min-days-ahead <n> (0 to 60), --weekend-requests <allowed|saturday_only|not_allowed>, --emergency <yes|no>, --contact-methods <call,text,email>: the booking policy, in your own words.
  • --ai-read <yes|no>, --ai-train <yes|no>: the robots.txt choices. Without them the section is a commented template that changes nothing.
  • --service-model <on_site|in_shop|both>, --primary <city or id>, --time-zone <IANA zone>: asked only when the pages do not settle them.
  • --place-id <id> also reads the business's Google Business Profile listing through the Places API, using your own GOOGLE_PLACES_API_KEY. Listing facts fill only what the site lacks and never override it, and the listing is used only once it is confirmed as this business (its website is the crawled site, or, when it lists none, its phone or its name and postal code match the site).
  • --out <dir> chooses where the files go. --json prints the whole result (manifest, files, TODO list, facts with sources) to stdout instead.
  • --verbose prints each URL as it is fetched.

The crawl refuses private, loopback, link-local, unique-local, multicast, and cloud-metadata addresses, in IPv4 and in every IPv6 form that embeds an IPv4 address (mapped, compatible, NAT64). Each hostname is resolved once, judged, and the connection is pinned to the judged addresses; redirects and sitemap children may name only the same host or its www twin. There is no switch that loosens this.

The same generator runs as a web tool on the parent site: https://www.theservicemarketingguys.com/tools/open-service-profile

The generator's core (src/core/) is generated from the maintainer's TypeScript and carries a header saying so; edit it there, not here. The manifest validator is part of that core, so the web tool, the public audit, this CLI, and npm run validate judge a manifest by one implementation. src/crawl.mjs, src/places.mjs, src/validate.mjs, and bin/ are this repository's own. Run npm test for the CLI tests (Node's built-in runner, fixture sites served locally over a pinned connection).

Skills

skills/ holds two Agent Skills: open-service-profile for an agent acting on a customer's behalf (discover the manifest, read it, call the tools, send a booking request under the consent rule) and open-service-profile-publish for a developer or site owner publishing a profile. Install with npx skills add buildmodus/open-service-profile. See skills/README.md.

Implementations

The Service Marketing Guys serves Level 2 manifests on its client sites, built from the same data that drives each site. Example: https://coastalecoheatair.com/.well-known/open-service-profile

Appendix D of the specification lists where the reference implementation and the specification still differ.

How to propose changes

Open an issue or a pull request. CONTRIBUTING.md describes what a proposal should include and how decisions and releases are made. Reports of places where the specification and a real implementation disagree are especially welcome.

Citation

Cite the versioned specification, not this repository. CITATION.cff carries the preferred citation, and GitHub's "Cite this repository" button reads it.

Licensing

Two licenses apply, by artifact:

  • Specification text (spec/): Creative Commons Attribution 4.0 International. See LICENSE-SPEC.md.
  • JSON Schemas, examples, scripts, and the generator (schemas/, examples/, scripts/, src/, bin/, tests/): MIT. See LICENSE.

Copyright 2026 EasyServe LLC.

來源：README.md，提交 8f41304

工具

0
SourceWeft 尚未讀取此伺服器的工具。

版本歷史

1
  1. v0.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分