_ registry / mcp http-sse · checked 1h ago

applivery-docs

https://docs.applivery.com

Registry code: 63b38d6927a58bc1

api record

Read-only access to the public Applivery documentation (https://docs.applivery.com).

Typical workflow: call list_doc_sections once for orientation, search_docs to find pages, then get_doc_page to read one.

endpoint
https://docs.applivery.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is applivery-docs live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is applivery-docs free to use?
Yes — the hub reached it with no key and no payment.
What tools does applivery-docs have?
4 tools: get_api_endpoint, get_doc_page, search_docs, list_doc_sections.
Is applivery-docs safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 98.4%· all time 98.4%

latency
356ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 369 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search product documentation
  • read a documentation page
  • get an api endpoint definition
  • list documentation sections
takes → gives
text → text, data
tools
4 reads
note
documentation mirror
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_doc_sections reads open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "section": {
          "type": "string",
          "description": "Optional filter on section name or title."
        }
      }
    }
    arguments 10 lines
  • get_api_endpoint reads unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "url": {
          "type": "string",
          "description": "A docs.applivery.com API reference page URL, e.g. from a search_docs result with docType 'api'."
        },
        "slug": {
          "type": "string",
          "description": "Path after the locale, e.g. 'api/android/web-apps/delete-web-app'. Used with locale when url is not given."
        },
        "locale": {
          "type": "string",
          "description": "Locale for the slug, e.g. 'en' (default en)."
        }
      }
    }
    arguments 18 lines
  • get_doc_page reads unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "url": {
          "type": "string",
          "description": "A docs.applivery.com page URL, typically copied from a search_docs result."
        },
        "slug": {
          "type": "string",
          "description": "Path after the locale, e.g. 'device-management/getting-started'. Used with locale when url is not given."
        },
        "locale": {
          "type": "string",
          "description": "Locale for the slug, e.g. 'en' (default en)."
        },
        "maxChars": {
          "type": "integer",
          "maximum": 200000,
          "minimum": 1000,
          "description": "Truncate the page after this many characters (default 80000). Raise it if a page arrives truncated."
        }
      }
    }
    arguments 24 lines
  • search_docs reads unknown 18h ago

    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'.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 12,
          "minimum": 1,
          "description": "Maximum number of results, 1 to 12 (default 8)."
        },
        "query": {
          "type": "string",
          "maxLength": 512,
          "minLength": 1,
          "description": "Search keywords or phrase."
        },
        "locale": {
          "type": "string",
          "description": "Language filter, e.g. 'en' or 'es'. Omit to search all languages."
        },
        "docType": {
          "enum": [
            "guides",
            "api"
          ],
          "type": "string",
          "description": "Filter by corpus: 'guides' (product documentation, for admins and end users) or 'api' (REST API reference, for developers). Omit to search both."
        },
        "section": {
          "type": "string",
          "description": "Restrict results to a documentation section."
        },
        "platform": {
          "type": "string",
          "description": "Filter by platform, e.g. 'Apple', 'Android', 'Windows', 'Cross-platform'."
        },
        "excludeSection": {
          "type": "string",
          "description": "Exclude a documentation section from results."
        }
      }
    }
    arguments 45 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 63b38d6927a58bc1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/63b38d6927a58bc1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/63b38d6927a58bc1/badge.svg)](https://brick.blue/agent/63b38d6927a58bc1?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.