com.applivery.docs/mcp
REMOTE · DOCS.APPLIVERY.COM
Search and read the public Applivery docs (MDM & app distribution). Read-only, no auth.
Available components
Last scanned (7 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Developer Tools
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 863 tokens (~172/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 6 Nov 2026 · Probed https://docs.applivery.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=docs.applivery.com | CN=WE1,O=Google Trust Services,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a0d77156fa82169e137412935126bc9f |
| SANs: docs.applivery.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 secure
Validation of docs.applivery.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| applivery.com. | DS published | 2371 | 13 | Verified |
| docs.applivery.com. | Verified address RRset verified with the apex keys |
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=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://docs.applivery.com/mcp | Verified | 200 | |
| http (plaintext) | http://docs.applivery.com/mcp | HTTPS enforced | 301 | https://docs.applivery.com/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 →
get_api_endpoint Get an Applivery API endpoint definition ~179
Get the machine-readable OpenAPI definition of one Applivery REST API endpoint: method, path, baseUrl, security, parameters, requestBody and responses — fully dereferenced, no $refs. Pass the `url` or `slug` of an API reference page; find those with search_docs using docType 'api'. Use this instead of get_doc_page when you need to construct or validate an actual API request.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Locale for the slug, e.g. 'en' (default en). |
| slug | string | – | Path after the locale, e.g. 'api/android/web-apps/delete-web-app'. Used with locale when url is not given. |
| url | string | – | A docs.applivery.com API reference page URL, e.g. from a search_docs result with docType 'api'. |
| Name | Type | Req | Description |
|---|---|---|---|
| baseUrl | string | – | – |
| method | string | – | HTTP method, uppercase. |
| parameters | – | – | OpenAPI parameter objects (dereferenced). |
| path | string | – | Endpoint path template. |
| requestBody | – | – | OpenAPI requestBody object (dereferenced). |
| responses | – | – | OpenAPI responses object (dereferenced). |
| security | – | – | OpenAPI security requirements. |
| url | string | yes | Canonical .md URL the definition was read from. |
No examples provided.
get_doc_page Read an Applivery documentation page ~163
Fetch the full Markdown content of a documentation page. Pass either `url` (typically a URL returned by search_docs) or `slug` plus `locale`. Returns clean Markdown; very long pages are truncated at `maxChars` with a note.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Locale for the slug, e.g. 'en' (default en). |
| maxChars | integer | – | Truncate the page after this many characters (default 80000). Raise it if a page arrives truncated. |
| slug | string | – | Path after the locale, e.g. 'device-management/getting-started'. Used with locale when url is not given. |
| url | string | – | A docs.applivery.com page URL, typically copied from a search_docs result. |
No output schema declared.
No examples provided.
list_doc_sections List Applivery documentation sections ~57
List the top-level documentation sections and landing pages from the site's curated index (llms.txt). Use for orientation, then drill in with search_docs or get_doc_page.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | – | Optional filter on section name or title. |
| Name | Type | Req | Description |
|---|---|---|---|
| sections | array | yes | – |
| total | number | yes | – |
No examples provided.
search_docs Search Applivery documentation ~233
Search the Applivery documentation by keyword or phrase. Returns matching pages with title, canonical URL, a highlighted snippet, docType ('guides' or 'api'), platform, breadcrumb and in-page headings. Use this first to discover pages, then read one with get_doc_page. For non-developer questions prefer docType 'guides'.
| Name | Type | Req | Description |
|---|---|---|---|
| docType | string | – | Filter by corpus: 'guides' (product documentation, for admins and end users) or 'api' (REST API reference, for developers). Omit to search both. |
| excludeSection | string | – | Exclude a documentation section from results. |
| limit | integer | – | Maximum number of results, 1 to 12 (default 8). |
| locale | string | – | Language filter, e.g. 'en' or 'es'. Omit to search all languages. |
| platform | string | – | Filter by platform, e.g. 'Apple', 'Android', 'Windows', 'Cross-platform'. |
| query | string | yes | Search keywords or phrase. |
| section | string | – | Restrict results to a documentation section. |
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | – | – |
| results | array | yes | – |
| suggestions | array | – | – |
| total | number | yes | – |
No examples provided.
How do I install the com.applivery.docs/mcp server?
com.applivery.docs/mcp is a hosted endpoint at https://docs.applivery.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 · docs.applivery.com
claude mcp add --transport http com-applivery-docs-mcp 'https://docs.applivery.com/mcp'
What is the com.applivery.docs/mcp server?
com.applivery.docs/mcp is listed in the public MCP registry as com.applivery.docs/mcp. Search and read the public Applivery docs (MDM & app distribution). Read-only, no auth. This page covers its hosted endpoint (https://docs.applivery.com/mcp).
Is the com.applivery.docs/mcp server safe to use?
com.applivery.docs/mcp scores 89 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 com.applivery.docs/mcp server expose?
com.applivery.docs/mcp exposes 4 tools: search_docs, get_doc_page, get_api_endpoint, list_doc_sections. Their descriptions and schemas cost roughly 632 tokens of context every time the server is loaded.
Does the com.applivery.docs/mcp server require authentication?
No. We connected to com.applivery.docs/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.applivery.docs/mcp server still maintained?
com.applivery.docs/mcp is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.applivery.docs/mcp server?
VerifyMCP ran 13 checks on com.applivery.docs/mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.