Site MCP server
com.texasfoundationrepaircost/site
We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 81 of 100 (grade B), higher than 26.3% of the 33,003 registry servers that responded over HTTPS that day. Ready for Gemini and MCP Registry. Not ready for Claude and ChatGPT.
Measured facts
- Score
- 81B
- Sign-in
- No sign-in
- Tools listed
- 3
- Protocol version
- 2025-11-25
Store readiness
| Store | Status | Reason |
|---|---|---|
| Claude Connectors Directory | Not ready | Blocked by readOnlyHint or destructiveHint on every tool. |
| ChatGPT app directory | Not ready | Blocked by readOnlyHint or destructiveHint on every tool and Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT). |
| Gemini Connected Apps | Ready | No blocking check failed. |
| Official MCP Registry | Ready | No blocking check failed. |
MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.
4 checks to fix
- Fails
readOnlyHint or destructiveHint on every tool
tool_annotationsBlocks Claude and ChatGPT.
Measured
3/3 tools set neither readOnlyHint nor destructiveHint: enquiry_describe, enquiry_fields, submit_enquirySet annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).
- Fails
Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)
tool_open_worldBlocks ChatGPT.
Measured
3/3 tools miss an explicit hint: enquiry_describe, enquiry_fields, submit_enquirySet readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).
- Fails
GET answers SSE or 405
get_streamMeasured
HTTP 200 application/jsonReturn HTTP 405 Method Not Allowed on GET (or a text/event-stream), not a page or 404.
- Warning
initialize latency
latencyMeasured
2317 msBring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.
13 checks passed, 10 did not run
Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, serverInfo name and version, Server instructions, tools capability declared, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, Human-readable title on every tool, Tool descriptions.
Not run. Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. The server asks for no sign-in, so the OAuth checks do not apply.
Run a fresh check
This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.
README badge
The badge shows the latest score for this URL and links to this report.
Markdown
[](https://www.mcpstamp.com/r/com-texasfoundationrepaircost-site/)
HTML
<a href="https://www.mcpstamp.com/r/com-texasfoundationrepaircost-site/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Ftexasfoundationrepaircost.com%2Fmcp" alt="McpStamp score" height="20"></a>
About this server
Texas Foundation Repair Cost: the site's own MCP server - enquiry (enquiry = a human handoff,...
The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.
More grade B servers
All grade B servers · All server reports · State of MCP readiness, November 2026