Atisbo Documentation
REMOTE · APP.ATISBO.DEV · SCANNED SEP 20
Read-only search and page retrieval from the public Atisbo documentation corpus. No authentication.
Available components
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 Security86
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
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'
{
"mcpServers": {
"brian8a1-atisbo-docs": {
"url": "https://app.atisbo.dev/api/mcp-docs"
}
}
} {
"servers": {
"brian8a1-atisbo-docs": {
"type": "http",
"url": "https://app.atisbo.dev/api/mcp-docs"
}
}
} [mcp_servers.brian8a1-atisbo-docs] url = "https://app.atisbo.dev/api/mcp-docs"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"brian8a1-atisbo-docs": {
"type": "remote",
"url": "https://app.atisbo.dev/api/mcp-docs",
"enabled": true
}
}
} openclaw mcp add brian8a1-atisbo-docs --url 'https://app.atisbo.dev/api/mcp-docs' --transport streamable-http
mcp_servers:
brian8a1-atisbo-docs:
url: "https://app.atisbo.dev/api/mcp-docs" {
"McpServers": {
"brian8a1-atisbo-docs": {
"Transport": "http",
"Url": "https://app.atisbo.dev/api/mcp-docs"
}
}
} assistant mcp add brian8a1-atisbo-docs -t streamable-http -u 'https://app.atisbo.dev/api/mcp-docs'
{
"mcpServers": {
"brian8a1-atisbo-docs": {
"type": "http",
"url": "https://app.atisbo.dev/api/mcp-docs"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Sept 26 −49
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.43 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Sept 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.
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 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.
- 27 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 +2
- 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: unverified → 0.03 ▲ 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 20 Sept 2026 · Probed https://app.atisbo.dev/api/mcp-docs
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.atisbo.dev | CN=YR1,O=Let's Encrypt,C=US | 27 Jul 2026 | 25 Oct 2026 | RSA 2048 | SHA256-RSA | 6ceda2081ea0f66aa07416ae41492c7a801 |
| SANs: app.atisbo.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
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 Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 403 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
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 | Auth required | 403 | |
| http (plaintext) | http://app.atisbo.dev/api/mcp-docs | HTTPS enforced | 308 | https://app.atisbo.dev/api/mcp-docs |
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.
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 34 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?
Yes. Atisbo Documentation asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Atisbo Documentation MCP server still maintained?
Atisbo Documentation is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.