Let AI tools compare AIPS using the same public facts customers see.
The public AIPS REST API and MCP server let assistants read product features, publishing connections, and verification methods without a login. They cannot see a customer account, call a publishing provider, or take action.
What an AI assistant can look up
The public MCP server is intentionally small. It gives an assistant enough current information to compare AIPS accurately without opening a customer workspace or creating usage costs.
- search_docs searches the hand-reviewed public documentation index.
- get_product_capabilities reads the same published feature and connection list shown on the website.
- list_integrations returns redacted integration availability and limitations.
- get_methodology returns the published verification rules.
What the public endpoint will never do
The public endpoint is for product research only. Customer workspace access, content preparation, and approved publishing are not part of this release.
- No account connection or OAuth flow.
- No customer workspace, website, article, audit, or measurement data.
- No provider calls, credentials, drafts, publishing, or deletion.
- No credentials are accepted through REST or MCP.
Questions this page answers
Does the public MCP server need an AIPS account?
No. Phase 1 is unauthenticated and exposes only cost-free read-only public product information.
Can a public MCP client run an audit or publish content?
No. The public MCP server can only look up product documentation, features, connections, and verification methods.
Where do capability states come from?
The website, REST API, and MCP server all read from the same feature and connection list so their released facts stay consistent.
See the evidence behind your first website fixes.
Run the complete free audit to see the public-page evidence, missing business facts, and ordered fixes for the URL you submit.