Atisbo Documentation
REMOTE · APP.ATISBO.DEV
Read-only search and page retrieval from the public Atisbo documentation corpus. No authentication.
Available components
Last scanned (25 minutes ago)
Scores higher than 98% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category Search and Retrieval
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 Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 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.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 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.
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 5 Nov 2026 · Probed https://app.atisbo.dev/api/mcp-docs
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of app.atisbo.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| atisbo.dev. | present | 45139 | 13 | Verified |
| app.atisbo.dev. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.atisbo.dev/api/mcp-docs | Unreachable | ||
| http (plaintext) | http://app.atisbo.dev/api/mcp-docs | HTTPS enforced |
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_doc ~55
Read one full Atisbo documentation page as markdown, by its site-relative URL (for example /docs/api/webhooks).
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Site-relative URL of the page, as returned by search_docs or list_docs. |
No output schema declared.
No examples provided.
list_docs ~81
List Atisbo documentation pages with their URL, title and description. Omit limit for the whole corpus; pass limit to cap the response.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of pages to return (1-50). Omitted, non-integer, or out-of-range values return the WHOLE corpus — this tool never pages, it only trims. |
No output schema declared.
No examples provided.
search_docs ~60
Search Atisbo documentation by keyword or natural-language question. Returns ranked page titles, URLs, descriptions and match scores.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum hits to return (default 5). |
| query | string | yes | Keywords or a natural-language question. |
No output schema declared.
No examples provided.
How do I install the Atisbo Documentation MCP server?
Atisbo Documentation is a hosted endpoint at https://app.atisbo.dev/api/mcp-docs, 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 · app.atisbo.dev
claude mcp add --transport http brian8a1-atisbo-docs 'https://app.atisbo.dev/api/mcp-docs'
What is the Atisbo Documentation MCP server?
Atisbo Documentation is an MCP server listed in the public MCP registry as io.github.brian8a1/atisbo-docs. Read-only search and page retrieval from the public Atisbo documentation corpus. No authentication. This page covers its hosted endpoint (https://app.atisbo.dev/api/mcp-docs).
Is the Atisbo Documentation MCP server safe to use?
Atisbo Documentation scores 91 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 Atisbo Documentation MCP server expose?
Atisbo Documentation exposes 3 tools: get_doc, list_docs, search_docs. Their descriptions and schemas cost roughly 196 tokens of context every time the server is loaded.
Does the Atisbo Documentation MCP server require authentication?
Its publisher declares no required credentials for Atisbo Documentation. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Atisbo Documentation MCP server still maintained?
Atisbo Documentation is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.