Foliora Managed AI Search MCP Server

by foliora Your server? Claim it

not responding

Foliora Managed AI Search is listed as active in the registry but did not answer our last check. It exposes 17 tools.

Foliora MCP for public discovery, account reads, and agent execution of human-approved changes.

Uptime history 26 days of history · worst day 0%

26 days agonow

7.6%

Uptime 24h

7 of 92 checks

Tools

read from the server

1179 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 18

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 September 2026. No other catalogue keeps this.

7 Sep 4 tools appeared approve_change, get_page_job, list_page_jobs and 1 more

5 Sep 4 tools appeared get_change_status, list_findings, report_finding_fix and 1 more

5 Sep a tool description was rewritten get_product

1 Sep 6 tools appeared get_approved_change, get_site_brief, list_approved_changes and 3 more

1 Sep 2 tools changed the parameters they ask for create_preview_link, get_snapshot

1 Sep a tool description was rewritten get_product

Foliora Managed AI Search does not always answer

Over the last week it answered 6.2% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add search --transport http https://www.foliora.ai/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "search": {
      "url": "https://www.foliora.ai/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.search]
url = "https://www.foliora.ai/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "search": {
      "url": "https://www.foliora.ai/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "search": {
      "url": "https://www.foliora.ai/mcp"
    }
  }
}

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

approved

get_approved_change

Return an already-approved canonical hash and its ordered typed operations. Apply exactly these values; do not reinterpret or regenerate them.

list_approved_changes

List exact change sets the customer already approved. Optionally filter by site. This never approves or publishes a change.

page

get_page_job

One proposed page change: why Foliora proposes it, the brief, the objectives it addresses, and the drafted change set with every operation's exact before and after values and its canonical hash. Read this with the customer before approve_change; never paraphrase the operations as approved text.

list_page_jobs

The current proposed page changes for one owned site, highest impact first, each with its drafted change set's status, canonical hash, and operation count. Use get_page_job to read a proposal in full before the customer decides.

report

report_finding_fix

After the agent fixes a finding on the site (a meta description, a robots rule, llms.txt), mark it fix_reported with a short note. Foliora's next crawl confirms it as resolved or reopens it; the report is never taken on faith. Requires execute access.

report_publication

Record proof that the customer's agent applied every operation from an already-approved canonical hash. This does not approve a change. Every receipt value must exactly match Foliora's stored operation.

approve

approve_change

Approve one drafted change set by its exact canonical hash. Call this only after the customer has read the operations from get_page_job and told you to approve that hash. A stale or mismatched hash is refused. Approval locks the hash; it does not publish anything. Requires OAuth or an API key with the approve scope.

change

get_change_status

For one change set: approval, publication (Foliora's or the agent's receipt), live verification outcome, and every re-asked question with whether ChatGPT or Gemini mentioned or cited the site afterwards. Read-only.

findings

list_findings

List the crawl findings still open on a site: SEO and AI-readiness plumbing such as missing descriptions, blocked AI crawlers, missing llms.txt, stale articles. Each row carries a code, severity, evidence URL, and plain-language fix guidance. Read-only.

preview

create_preview_link

Build a Foliora /preview URL for a public website. Does not crawl, does not take credentials, and does not change the site. Send the human to the returned previewUrl so they can start the snapshot in a browser.

product

get_product

Return Foliora product facts: brand, per-site plans, canonical URLs, and product boundaries. Use when the user asks what Foliora is, how much it costs, or which URL to open. Does not crawl a site.

reject

reject_change

Close one drafted change set without approving it. Call this only when the customer says so. The job stays proposed and can be drafted again later. Requires OAuth or an API key with the approve scope.

request

request_recrawl

Pull the site's next crawl forward so reported fixes are checked sooner. One crawl per six hours per site; the response says whether it was queued, already running, or on cooldown and when it can run next. Requires execute access.

site

get_site_brief

Return the authenticated customer's current site model, recent runs, open findings, measurement series, question panel, and page jobs.

sites

list_sites

List sites owned by the authenticated Foliora account with crawl and finding status. Requires OAuth or a Foliora API key with read scope.

snapshot

get_snapshot

Fetch a Foliora preview snapshot the human already started. Requires the 32-character hex token from /preview/{token}. Returns public findings and pages only. Unknown tokens are not_found. Does not start a crawl.

verify

verify_publication

Queue Foliora's rendered production verification after a valid external publication receipt exists. Safe to retry; the same open verification run is returned.

Endpoints

URL	Transport	State	Latency	Checked
https://www.foliora.ai/mcp	streamable-http	answering	100 ms	0 min ago

Alternatives to Foliora Managed AI Search

same job, measured the same way

AgencyAI Commerce MCP

by barnaby-coder

AgencyAI's public MCP for service discovery and AI-readiness assessment.

3 tools answering

Azeth Protocol

by azeth-protocol

Smart accounts, x402 payments, on-chain reputation, and service discovery for AI agents

38 installs/wk local only

ZenithEye Agent Commons

by zenitheye

Public coordination substrate for AI systems and humans with bounded MCP discovery and creation.

17 tools answering

Tinysearch

by tinysuitehq

Fast discovery search and self-hosted web research for MCP agents.

842 installs/wk local only

Looppause

by soteeabam

LoopPause MCP server — pause agent execution and route human approval requests

25 installs/wk local only

Secant Agent Research Pack

by jnilrac

Paid MCP web research for agents: search, extraction, citations, and x402 payment discovery.

5 tools answering

Talent

by d

Talent discovery for AI. Search and read agent-readable candidate profiles; cite by URL.

7 tools answering

SIMA MCP Server

by mustafashehab

Read-only MCP server for SIMA Solana AI agent protection discovery. No API keys required.

47 installs/wk local only

Foliora Managed AI Search — questions

Answers built from our own checks of this server.

What can Foliora Managed AI Search do?

It exposes 17 tools, read directly from the server on our last check. Among them: approve_change, create_preview_link, get_approved_change, get_change_status, get_page_job, get_product and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Foliora Managed AI Search mostly used for?

Its tools cluster around page, report and approved. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Foliora Managed AI Search working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 7 of 92 checks got a reply (7.6%), average response time 1179 ms. The bar chart above shows every period we have measured.

The registry lists Foliora Managed AI Search as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Foliora Managed AI Search?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Foliora Managed AI Search need an API key?

No. Foliora Managed AI Search completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Foliora Managed AI Search?

It answers our handshake in 1179 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.