mcp-registry/io.github.sitegpt/sitegpt · v1.0.0
Verdict. Sitegpt MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 165 ms median handshake and 0 outages in 90 days. Its agent-readiness grade is A (97/100) across 17 tools, costing an agent about 4,254 tokens to load. Checked every few minutes; no tool is ever called.
Data as of .
| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 165 ms | 75% of MCP servers |
| p95 handshake latency | 401 ms | — |
| Checks in 30 days | 205 | — |
| Outages, 90 days | 0 | — |
| Median recovery | — | — |
| Agent-readiness score | 97/100 (A) | 91% of MCP servers |
| Tools | 17 | — |
| Tool-list size for an agent | ~4,254 tokens | 40% of MCP servers |
| Days observed | 27 | — |
As of 2026-10-26 20:30 UTC, the Sitegpt MCP server is up (it requires sign-in) with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Manage SiteGPT chatbots and account resources through the SiteGPT API v2.
Claude Code
claude mcp add --transport http sitegpt-mcp-server https://sitegpt.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"sitegpt-mcp-server": {
"type": "http",
"url": "https://sitegpt.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Runs commands or code supplied by the model. Legitimate for dev tools; clients should require confirmation. Example (execute_read, name): "execute_read(code)"
Declare destructiveHint/readOnlyHint on these tools and say plainly in the description what runs, where, and with what limits. How to fix →
Requires authentication (Bearer); tool definitions could not be read anonymously.
If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.
Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.sitegpt/sitegpt"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.sitegpt/sitegpt"}) over MCP.
update_chatbot_appearance ~484 tokenscreate_knowledge_source ~340 tokenssend_chat_message ~307 tokenslist_conversations ~284 tokenslist_leads ~270 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.sitegpt%2Fsitegpt?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.sitegpt%2Fsitegpt?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.sitegpt%2Fsitegpt.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.sitegpt%2Fsitegpt.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.sitegpt%2Fsitegpt?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:22a6b0a6fa106e3b…, first seen 2026-10-17, included at leaf 8552 of 75,327. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable api servers · most reliable code servers · most reliable analytics servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 20:30 UTC, the Sitegpt MCP server is up (it requires sign-in) with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Sitegpt MCP server advertises 17 tools, including authorize_knowledge_source, create_knowledge_source, execute_read, execute_write, get_chatbot_analytics.
Point your MCP client at this streamable-http endpoint: https://sitegpt.ai/mcp
Glimind scanned all 17 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.