Rootpublish AI facts check
REMOTE · ROOTPUBLISH.COM
Check what an AI assistant tells buyers about a company against the company's own pricing pages.
Available components
Last scanned (20 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Marketing and SEO
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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 331 tokens (~110/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +35
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.27 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Oct 26 −33
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 17. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 62
First indexed and scored.
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 16 Oct 2026 · Probed https://rootpublish.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rootpublish.com | CN=WE1,O=Google Trust Services,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 779472b3c30f01490e7f80fca050a015 |
| SANs: rootpublish.com, studio-staging.rootpublish.com, *.studio-staging.rootpublish.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rootpublish.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rootpublish.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; connect-src 'self'; frame-src 'none'; object-src 'none'; base-uri 'none'; frame-ancestors 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rootpublish.com/mcp | Verified | 200 | |
| http (plaintext) | http://rootpublish.com/mcp | Inconclusive | 405 |
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 →
buyer_questions ~102
Start an AI facts check: returns the questions a buyer asks about a company. Answer them yourself, with web search, before reading anything from the company.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | The company or product name buyers use |
| depth | string | – | full asks three questions (default); quick asks one |
| offer | string | – | The product or service to ask about |
| site | string | yes | The company's site, e.g. https://example.com |
No output schema declared.
No examples provided.
company_statements ~72
After you have answered the buyer questions: reads the company's pricing and service pages and returns its statements with instructions for comparing your answers.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| pages | array | – | Paths of the pages that state prices and terms, e.g. ["/pricing"] |
| site | string | yes | – |
No output schema declared.
No examples provided.
verify_findings ~99
Keeps only the differences whose quotes are really in your answer and on the company's page, and finds the pages your answer cited that carry a wrong figure. Call once per answer.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | One of your full answers, exactly as you wrote it |
| judgement | string | yes | Your findings for that answer as a JSON object |
| pages | array | – | The pages returned by company_statements |
| site | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Rootpublish AI facts check MCP server?
Rootpublish AI facts check is a hosted endpoint at https://rootpublish.com/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 · rootpublish.com
claude mcp add --transport http com-rootpublish-ai-facts 'https://rootpublish.com/mcp'
What is the Rootpublish AI facts check MCP server?
Rootpublish AI facts check is an MCP server listed in the public MCP registry as com.rootpublish/ai-facts. Check what an AI assistant tells buyers about a company against the company's own pricing pages. This page covers its hosted endpoint (https://rootpublish.com/mcp).
Is the Rootpublish AI facts check MCP server safe to use?
Rootpublish AI facts check scores 66 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 Rootpublish AI facts check MCP server expose?
Rootpublish AI facts check exposes 3 tools: buyer_questions, company_statements, verify_findings. Their descriptions and schemas cost roughly 273 tokens of context every time the server is loaded.
Does the Rootpublish AI facts check MCP server require authentication?
No. We connected to Rootpublish AI facts check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Rootpublish AI facts check MCP server still maintained?
Rootpublish AI facts check is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.