INITE Agents

ai.inite由 inite.ai 發布官方發布者v0.1.0更新於 Oct 30, 2026

Per-business MCP servers serving owner-confirmed facts: services, prices, hours, places, FAQ.

發布方自己的服務：INITE Visibility

已驗證Streamable HTTP可網頁執行知識與記憶商業與電商

服務詳細資訊

識別碼: ai.inite/site-agents
傳輸: Streamable HTTP
執行環境: Web executable
信任: Verified
發布於: Oct 22, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此服務的命名空間屬於 inite.ai，且該網域同時執行其端點。這可以確認發布者，但並不代表該服務的工具是安全的。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/ai.inite%2Fsite-agents.svg)](https://sourceweft.com/mcp/ai.inite%2Fsite-agents?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

依商家提供的遠端 MCP 伺服器，向 AI 代理提供經業主確認的事實：服務、價格、營業時間、地點與常見問題。

可以做什麼: 透過唯讀工具讀取商家事實、服務、價格、營業時間、地點與常見問題
與產生的 llms.txt、代理卡片和 MCP 伺服器卡片一起，向讀取網站的代理提供同一批已確認事實
可選擇發布依搜尋需求撰寫的文章，且每篇都須先經核准
可透過 WordPress、Next.js、頁首程式碼片段、Ghost 或帶簽章 webhook 的 REST 介面接入
適用情境: 適合希望 AI 助理和瀏覽器代理讀到準確、經業主核可的服務、價格與營業時間資訊，而不是從網站自行猜測的商家。若你已在 INITE 後台維護這些事實，並希望將其提供給 ChatGPT、Claude、Perplexity 或瀏覽器內代理，則適用。
執行需求: 使用商家自有子網域上的遠端端點，透過 streamable HTTP 存取。需先在 INITE 後台確認事實，並安裝連接器（WordPress 外掛、Next.js 套件、頁首程式碼片段、Ghost 或帶站台金鑰的 REST）才能從自有網域提供這些檔案。MCP 端點未宣告需要驗證。

安裝前請注意

MCP 端點被描述為唯讀，但整體產品會寫入你的網站：新增檔案、robots.txt 列、頁首標籤，並可選擇發布文章，因此應審查每個連接器的變更。REST 與 webhook 整合使用站台金鑰，README 稱其只傳送至 INITE 來源。文章僅在核准後發布，但核准環節需由你自行把關。

安裝

在 SourceWeft 中

開啟儀表板中的 INITE Agents，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

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

其他 MCP 客戶端

參照儲存庫中的啟動說明。

README

INITE Agents

An AI agent that comes to your site gets the facts your business confirmed. That is the whole promise, and it is narrow on purpose. INITE Agents does not promise more recommendations or more traffic. It promises that ChatGPT, Claude, Perplexity or an agent in a visitor's browser gets your real services, prices, hours, locations and answers when it reads your site, and gets nothing you did not confirm.

You confirm the facts once in the INITE cabinet. INITE generates the files agents look for and runs an MCP server for your business. A connector on your site then serves everything from your own domain.

What agents get	Where
`llms.txt`	`/llms.txt`
A2A agent card	`/.well-known/agent-card.json`
MCP server card (`server.json` shape)	`/.well-known/mcp.json`
API catalog (RFC 9727)	`/.well-known/api-catalog`
`Content-Signal` line (contentsignals.org): search and answers yes, training no	`robots.txt`
WebMCP tools for an agent in the browser, `<link>` tags to the files, JSON-LD (Organization or LocalBusiness, FAQPage)	the page `<head>`
A remote MCP server with read-only tools: business facts, services, hours, locations, FAQ	`https://<your-slug>.inite.ai/mcp`
Optional: articles written from measured search demand, published only after you approve each one	your CMS

Connectors

Platform	Connector	Get it	Docs
WordPress	Plugin: root files, robots.txt, head, abilities for the WordPress MCP Adapter, articles	Releases · inite.ai zip · source	docs/wordpress.md
Next.js	npm package: two route files and one head component, plus the article queue	`@inite/site-agents` · source	docs/nextjs.md
Any site with a head-code box (Tilda, Squarespace, Wix, Webflow, Framer, Ghost, Shopify, Bitrix, Joomla, hand-made)	The snippet: one `<script>` tag, no key	the cabinet	docs/any-site.md
Ghost	INITE publishes approved articles through Ghost's Admin API; the snippet for the head	the cabinet	docs/ghost.md
Any stack	REST endpoints with a site key, and signed webhooks	the cabinet	docs/webhooks-and-rest.md · examples/
Webflow, Shopify, Framer, Wix, Notion, WordPress.com	Apps of their own are coming. Until then, the snippet connects all of these except Notion		docs/any-site.md

The full API reference is at https://inite.ai/en/mcp#site-api.

What INITE never does

Publishes a fact or a price you did not confirm.
Puts an article on your site that you did not approve.
Keeps a route claimed by a switched-off connector. Every connector switches off whole, and a feature that is off claims no URL and prints nothing.
Sends your site key anywhere but https://inite.ai. Connectors build every address from that origin and never follow a redirect with the key.
Lets an INITE outage take your site down. Connectors keep a copy and refresh it on a timer: hourly from WP-Cron in WordPress, at most once per period in Next.js, with a five-second limit. If INITE is down, the last good copy is served.

This repository

docs/: setup for each platform.
examples/: webhook receivers that verify the signature, in Node.js, PHP and Python, and a script that sends a signed test event.
Issues for every connector go here: open an issue.

The connectors' code lives in INITE's private monorepo. inite-agents-wordpress and site-agents are read-only mirrors of it, updated on every change. See CONTRIBUTING.md.

Security reports: [email protected] (SECURITY.md).