Foliora Managed AI Search
REMOTE · WWW.FOLIORA.AI · SCANNED SEP 20
Foliora MCP for public discovery, account reads, and agent execution of human-approved changes.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the Foliora Managed AI Search MCP server?
Foliora Managed AI Search is a hosted endpoint at https://www.foliora.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.foliora.ai
claude mcp add --transport http ai-foliora-search 'https://www.foliora.ai/mcp'
{
"mcpServers": {
"ai-foliora-search": {
"url": "https://www.foliora.ai/mcp"
}
}
} {
"servers": {
"ai-foliora-search": {
"type": "http",
"url": "https://www.foliora.ai/mcp"
}
}
} [mcp_servers.ai-foliora-search] url = "https://www.foliora.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-foliora-search": {
"type": "remote",
"url": "https://www.foliora.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-foliora-search --url 'https://www.foliora.ai/mcp' --transport streamable-http
mcp_servers:
ai-foliora-search:
url: "https://www.foliora.ai/mcp" {
"McpServers": {
"ai-foliora-search": {
"Transport": "http",
"Url": "https://www.foliora.ai/mcp"
}
}
} assistant mcp add ai-foliora-search -t streamable-http -u 'https://www.foliora.ai/mcp'
{
"mcpServers": {
"ai-foliora-search": {
"type": "http",
"url": "https://www.foliora.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Sept 26 −42
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: 0.67 → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 16 Sept 26 0
- A breaking change shipped without a version bump: still 0.4.0 ▼ security
- Tool “get_change_status” was removed ▼ security
- Tool “get_site_brief” was removed ▼ security
- Tool “list_approved_changes” was removed ▼ security
- Tool “request_recrawl” was removed ▼ security
- Tool “verify_publication” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “approve_change” rewrote its description, which is the text the model reads security
- Tool “get_page_job” rewrote its description, which is the text the model reads security
- Tool “list_page_jobs” rewrote its description, which is the text the model reads security
- Tool “report_finding_fix” rewrote its description, which is the text the model reads security
- Tool “report_publication” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 0
- Schema quality: 853 → 1142 ▼ functional
- New tool “approve_change” functional
- New tool “get_page_job” functional
- New tool “list_page_jobs” functional
- New tool “reject_change” functional
- 6 Sept 26 0
- Tool “get_product” rewrote its description, which is the text the model reads security
- Tool coverage: 20% → 13% ▼ functional
- Schema quality: 568 → 853 ▼ functional
- New tool “get_change_status” functional
- New tool “list_findings” functional
- New tool “report_finding_fix” functional
- New tool “request_recrawl” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://www.foliora.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.foliora.ai | CN=YR2,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | RSA 2048 | SHA256-RSA | 598b511a66b6cfc06e742d10d2d6673bf34 |
| SANs: www.foliora.ai | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.foliora.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| foliora.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://www.foliora.ai/.well-known/oauth-protected-resource/mcp", scope="openid email"
Bearer resource_metadata="https://www.foliora.ai/.well-known/oauth-protected-resource/mcp", scope="openid email"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| www-authenticate | Bearer resource_metadata="https://www.foliora.ai/.well-known/oauth-protected-resource/mcp", scope="openid email" |
Protected resource metadata
| Document | https://www.foliora.ai/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://www.foliora.ai/mcp |
| Authorisation server | https://afetanckensrtdlijhmq.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.foliora.ai/mcp | Auth required | 401 | |
| http (plaintext) | http://www.foliora.ai/mcp | HTTPS enforced | 308 | https://www.foliora.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
approve_change Approve a drafted change on the customer's instruction ~122
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 is the customer's only decision: on a site with a connected publisher Foliora publishes and verifies from here on its own (fix.publisherReady true); otherwise the agent applies the exact operations and calls report_publication. Requires OAuth or an API key with the approve scope.
| Name | Type | Req | Description |
|---|---|---|---|
| changeSetId | string | yes | – |
| expectedHash | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| approvedAt | string|null | – | – |
| approvedVia | string | yes | – |
| canonicalHash | string | – | – |
| changeSetId | string | yes | – |
| status | string | – | – |
No examples provided.
create_preview_link Create a Foliora preview link ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| websiteUrl | string | yes | Public website URL or host. https is optional. |
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | – |
| previewUrl | string | yes | – |
| websiteUrl | string | yes | – |
No examples provided.
get_approved_change Get one approved Foliora change ~43
Return an already-approved canonical hash and its ordered typed operations. Apply exactly these values; do not reinterpret or regenerate them.
| Name | Type | Req | Description |
|---|---|---|---|
| changeSetId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| approvedAt | string | yes | – |
| brief | string | yes | – |
| canonicalHash | string | yes | – |
| changeSetId | string | yes | – |
| host | string | yes | – |
| jobId | string | yes | – |
| operations | array | yes | – |
| rationale | string | yes | – |
| siteId | string | yes | – |
| title | string | yes | – |
No examples provided.
get_page_job Read one Foliora proposal in full ~111
One proposed page change: why Foliora proposes it, the brief, the objectives it addresses, the drafted change set with every operation's exact before and after values and its canonical hash, and `fix` — its customer-facing state, reason, live finding statuses, older editions and nextAction. A stale edition is readable history with a null hash; it can never be approved. Read this with the customer before approve_change; never paraphrase the operations as approved text.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | yes | – |
| changeSet | object|null | yes | – |
| citationGap | string | – | – |
| citationObjectives | array | – | – |
| competingHosts | array | – | – |
| compile | object|null | – | – |
| createdAt | string | – | – |
| findingObjectives | array | – | – |
| host | string | yes | – |
| impactScore | number | yes | – |
| jobId | string | yes | – |
| rationale | string | yes | – |
| searchObjectives | array | – | – |
| siteId | string | yes | – |
| status | string | yes | – |
| targetUrl | string | yes | – |
| title | string | yes | – |
No examples provided.
get_product Get Foliora product facts ~54
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| addons | array | yes | – |
| brand | string | yes | – |
| category | string | yes | – |
| doesNot | array | yes | – |
| hero | string | yes | – |
| links | object | yes | – |
| mcpUrl | string | yes | – |
| plans | array | yes | – |
| previewUrl | string | yes | – |
| pricingUrl | string | yes | – |
| support | string | yes | – |
| workflow | string | yes | – |
No examples provided.
get_snapshot Get a Foliora preview snapshot ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | Public snapshot token from a Foliora preview URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| aiPresence | object|null | yes | – |
| errorCode | string|null | yes | – |
| findings | array | yes | – |
| googlePresence | object|null | yes | – |
| host | string | yes | – |
| locked | boolean | yes | – |
| pageCount | number | yes | – |
| pages | array | yes | – |
| phase | string|null | yes | – |
| processing | boolean | yes | – |
| status | string | yes | – |
| token | string | yes | – |
| websiteUrl | string | yes | – |
No examples provided.
list_findings List a site's open findings ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| siteId | string | yes | – |
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | – |
No examples provided.
list_page_jobs List what Foliora proposes for a site ~119
The page changes Foliora proposes for one owned site, highest impact first — the same list the customer's dashboard shows. Each row carries `fix`: the customer-facing state (Foliora is working / Your turn / Published / Verified live / Needs a hand), why there is no draft to act on when there is none, the live status of every finding it set out to fix, and nextAction. Use get_page_job to read a proposal in full before the customer decides.
| Name | Type | Req | Description |
|---|---|---|---|
| siteId | string | yes | – |
| status | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| jobs | array | yes | – |
No examples provided.
list_sites List the customer's Foliora sites ~35
List sites owned by the authenticated Foliora account with crawl and finding status. Requires OAuth or a Foliora API key with read scope.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| sites | array | yes | – |
No examples provided.
reject_change Reject a drafted change on the customer's instruction ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| changeSetId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| changeSetId | string | yes | – |
| rejectedVia | string | yes | – |
| status | string | – | – |
No examples provided.
report_finding_fix Report a finding as fixed ~95
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. It shows as done on the customer's Fixes list; Foliora's next scheduled read confirms it as resolved or reopens it. The report is never taken on faith. Requires execute access.
| Name | Type | Req | Description |
|---|---|---|---|
| findingId | string | yes | – |
| note | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| findingId | string | yes | – |
| fixReportedAt | string|null | – | – |
| fixReportedBy | string|null | – | – |
| status | string | yes | – |
No examples provided.
report_publication Report an approved change was published ~100
Record proof that the customer's agent applied every operation from an already-approved canonical hash. Foliora verifies the live page from here on its own and the change shows as done on the customer's dashboard. This does not approve a change. Every receipt value must exactly match Foliora's stored operation.
| Name | Type | Req | Description |
|---|---|---|---|
| changeSetId | string | yes | – |
| expectedHash | string | yes | – |
| idempotencyKey | string | yes | – |
| receipt | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| created | boolean | yes | – |
| executionId | string | yes | – |
| nextAction | string | yes | – |
| receiptId | string | yes | – |
| verificationQueued | boolean | yes | – |
| verificationReady | boolean | yes | – |
| verificationReason | string|null | – | – |
| verificationRunId | string|null | – | – |
No examples provided.
What is the Foliora Managed AI Search MCP server?
Foliora Managed AI Search is an MCP server listed in the public MCP registry as ai.foliora/search. Foliora MCP for public discovery, account reads, and agent execution of human-approved changes. This page covers its hosted endpoint (https://www.foliora.ai/mcp).
Is the Foliora Managed AI Search MCP server safe to use?
Foliora Managed AI Search scores 38 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Foliora Managed AI Search MCP server expose?
Foliora Managed AI Search exposes 12 tools: get_product, get_snapshot, create_preview_link, list_sites, get_approved_change, and 7 more. Their descriptions and schemas cost roughly 953 tokens of context every time the server is loaded.
Does the Foliora Managed AI Search MCP server require authentication?
Yes. Foliora Managed AI Search asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Foliora Managed AI Search MCP server still maintained?
Foliora Managed AI Search is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.