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).