SiteGPT Docs
REMOTE · SITEGPT.AI · SCANNED SEP 21
Search the SiteGPT documentation: setup, features, API reference, troubleshooting.
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 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1383 tokens (~345/item across 4 items; 3 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the SiteGPT Docs MCP server?
SiteGPT Docs is a hosted endpoint at https://sitegpt.ai/docs/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 · sitegpt.ai
claude mcp add --transport http sitegpt-sitegpt-docs 'https://sitegpt.ai/docs/mcp'
{
"mcpServers": {
"sitegpt-sitegpt-docs": {
"url": "https://sitegpt.ai/docs/mcp"
}
}
} {
"servers": {
"sitegpt-sitegpt-docs": {
"type": "http",
"url": "https://sitegpt.ai/docs/mcp"
}
}
} [mcp_servers.sitegpt-sitegpt-docs] url = "https://sitegpt.ai/docs/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sitegpt-sitegpt-docs": {
"type": "remote",
"url": "https://sitegpt.ai/docs/mcp",
"enabled": true
}
}
} openclaw mcp add sitegpt-sitegpt-docs --url 'https://sitegpt.ai/docs/mcp' --transport streamable-http
mcp_servers:
sitegpt-sitegpt-docs:
url: "https://sitegpt.ai/docs/mcp" {
"McpServers": {
"sitegpt-sitegpt-docs": {
"Transport": "http",
"Url": "https://sitegpt.ai/docs/mcp"
}
}
} assistant mcp add sitegpt-sitegpt-docs -t streamable-http -u 'https://sitegpt.ai/docs/mcp'
{
"mcpServers": {
"sitegpt-sitegpt-docs": {
"type": "http",
"url": "https://sitegpt.ai/docs/mcp"
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 0
- Tool “query_docs_filesystem_site_gpt_docs” rewrote its description, which is the text the model reads security
- Tool “search_site_gpt_docs” rewrote its description, which is the text the model reads security
- Schema quality: 307 → 345 ▼ functional
- “submit_feedback” reworded the description of “path” cosmetic
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 21 Sept 2026 · Probed https://sitegpt.ai/docs/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sitegpt.ai | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 7c4782bca91cafd113fba5065114cc59 |
| SANs: sitegpt.ai, app.sitegpt.ai | ||||||
| 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 sitegpt.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| sitegpt.ai. | present | 2371 | 13 | Verified |
| sitegpt.ai. | 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=0; includeSubDomains; preload |
| content-security-policy | worker-src * blob: data:; object-src data:; base-uri 'self'; upgrade-insecure-requests; frame-ancestors 'self' https://dashboard.mintlify.com https://app.mintlify.com; form-action 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sitegpt.ai/docs/mcp | Verified | 200 | |
| http (plaintext) | http://sitegpt.ai/docs/mcp | HTTPS enforced | 301 | https://sitegpt.ai/docs/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 →
query_docs_filesystem_site_gpt_docs ~862
Run a read-only shell-like query against a virtualized, in-memory filesystem rooted at `/` that contains ONLY the SiteGPT Docs documentation pages and OpenAPI specs. This is NOT a shell on any real machine — nothing runs on the user's computer, the server host, or any network. The filesystem is a sandbox backed by documentation chunks. This is how you read documentation pages: there is no separate "get page" tool. To read a page, pass its `.mdx` path to `head` or `cat` — a page at the URL path `/some/page` lives at `/some/page.mdx`. To search the docs with exact keyword or regex matches, use `rg`. To understand the docs structure, use `tree` or `ls`. **Paths are specific to this site — never guess them.** Discover real paths with `tree / -L 2`, `ls /`, or the search tool before reading. If a path does not exist, that only means the guess was wrong; it does NOT mean the topic is undocumented — use `rg -il "keyword" /` to find where it is covered. **Workflow:** Start with the search tool for broad or conceptual queries like "how to authenticate" or "rate limiting". Use this tool when you need exact keyword/regex matching, structural exploration, or to read the full content of a specific page by path. Supported commands: rg (ripgrep), grep, find, tree, ls, cat, head, tail, stat, wc, sort, uniq, cut, sed, awk, jq, plus basic text utilities. No writes, no network, no process control. Run `--help` on any command for usage. Each call is STATELESS: the working directory always resets to `/` and no shell variables, aliases, or history carry over between calls. If you need to operate in a subdirectory, chain commands in one call with `&&` or pass absolute paths (e.g., `cd /some-directory && ls` or `ls /some-directory`). Do NOT assume that `cd` in one call affects the next call. Examples (replace the placeholder paths with real ones from `tree` or search): - `tree / -L 2` — see the top-level directory layout - `rg -il "rate limit" /` — find all files mentioning "rate li…
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | A shell command to run against the virtualized documentation filesystem (e.g., `rg -il "keyword" /`, `tree / -L 2`, `head -80 /path/file.mdx`). |
No output schema declared.
No examples provided.
search_site_gpt_docs Search documentation ~171
Search across the SiteGPT Docs knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about SiteGPT Docs, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query |
| version | string | – | Filter to specific version (e.g., 'v0.7') |
No output schema declared.
No examples provided.
submit_feedback Submit documentation feedback ~125
Report a problem with this documentation site so the docs team can fix it. Use when a documentation page is incorrect, outdated, confusing, incomplete, or has a broken example. This is for feedback about the documentation content itself — not for product support requests or feedback about this tool or assistant.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | string | yes | A clear description of the documentation issue or suggestion — what is incorrect, outdated, missing, or confusing. |
| path | string | yes | The URL path of the documentation page the feedback is about (the page you were reading, without the `.mdx` extension). |
No output schema declared.
No examples provided.
What is the SiteGPT Docs MCP server?
SiteGPT Docs is an MCP server listed in the public MCP registry as io.github.sitegpt/sitegpt-docs. Search the SiteGPT documentation: setup, features, API reference, troubleshooting. This page covers its hosted endpoint (https://sitegpt.ai/docs/mcp).
Is the SiteGPT Docs MCP server safe to use?
SiteGPT Docs scores 88 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 SiteGPT Docs MCP server expose?
SiteGPT Docs exposes 3 tools: search_site_gpt_docs, query_docs_filesystem_site_gpt_docs, submit_feedback. Their descriptions and schemas cost roughly 1,158 tokens of context every time the server is loaded.
Does the SiteGPT Docs MCP server require authentication?
No. We connected to SiteGPT Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SiteGPT Docs MCP server still maintained?
SiteGPT Docs is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.