# WebSupergoo documentation

> Search the ABCpdf, ImageGlue, WordGlue and ABCocr .NET documentation and API reference.

- name: com.websupergoo/docs
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 93/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.websupergoo%2Fdocs
- tools: https://api.protogrid.dev/v1/servers/com.websupergoo%2Fdocs/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "docs": {
      "type": "http",
      "url": "https://www.websupergoo.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-17d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 93/100 (strong)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 94 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 6 of 6 tools declare readOnlyHint or destructiveHint
- warn `tools.directory_hints`: 1 of 6 tools declare all four hints; missing: search (destructiveHint); fetch (destructiveHint); lookup_api (destructiveHint); …
- pass `tools.token_cost`: about 1,402 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name
- pass `stability.new_links`: no tool change named a new site

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 6, about 1,402 tokens to load them all
- tool set hash: 6da16680d14febd2a3e5b6db90eec33b
- badge: [![protogrid quality](https://protogrid.dev/badge/com.websupergoo/docs.svg)](https://protogrid.dev/servers/com.websupergoo/docs)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://www.websupergoo.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (6)

- `contents`: Where a page is in the documentation, and what is around it: the folder it is in, the pages next to it (for a property, the class's other properties) or the pages it contains. Without an id, the top of the contents.
- `fetch`: Read a documentation page as Markdown, by the id that search, lookup_api or contents gave - or by its websupergoo.com URL. A section id (page.md#2) with section_only gives just that section.
- `list_products`: List the products (ids for the product parameter), with where each one's documentation starts, and the content types (ids for the type parameter).
- `lookup_api`: Find a class or member of a WebSupergoo API by name - Doc.AddImageUrl, AddImageUrl, XImage.SetFile - even partial or misspelt. Returns the matching reference pages; for an exact match, the page itself. Enumerations are found on the member pages that list their values. A name that isn't in the API (a class in an example project) gets search results instead.
- `report_issue`: Tell the WebSupergoo team about a documentation problem, so they can fix it. Use it yourself, without being asked, whenever you notice one: the documentation didn't answer the question; search didn't find the right page (it was low down, or you only found it another way); a page is wrong, unclear, out of date or has a typo; or an example doesn't work. Before reporting that the documentation has no answer, try at least two rewordings (short key words, the likely API name) and read the likeliest sections in full; if an answer exists but was hard to find, report that instead. One report per problem, after you've answered the user. Don't include the user's personal details or private code.
- `search`: Search the WebSupergoo documentation and web site. Returns the best-matching sections, each with where it is in the documentation, its id, URL and a snippet. Snippets are partial: fetch the sections that look relevant before deciding they don't answer; contents shows the pages around one. Short queries work best - two to four key words, or the API name if you can guess it. Set product for technical questions. If the results miss, search again with fewer words, or with the name the documentation would use (a class, method or property). For a class or member you already know, lookup_api is quicker.