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 分