Griddo AX Docs
REMOTE · AX.MCP.GRIDDO.IO
Official Griddo backoffice docs for content authors: search, read and list pages in ES and EN.
Available components
Last scanned (12 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Productivity and Notes
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 472 tokens (~157/item across 3 items; 3 tools + 0 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 Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
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 4 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
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 +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.
- 2 Nov 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.
- 31 Oct 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.
- 29 Oct 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.
- 26 Oct 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.
- 24 Oct 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.
- 23 Oct 26 0
- Server version: 0.1.0 → 0.1.2 functional
- 22 Oct 26 +1
- 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 5 Nov 2026 · Probed https://ax.mcp.griddo.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ax.mcp.griddo.io | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 8 Sept 2026 | 24 Mar 2027 | RSA 2048 | SHA256-RSA | ad3239c0bb56be4fa185dbeba1e45ca |
| SANs: ax.mcp.griddo.io | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ax.mcp.griddo.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| griddo.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ax.mcp.griddo.io/mcp | Verified | 200 | |
| http (plaintext) | http://ax.mcp.griddo.io/mcp | HTTPS enforced | 301 | https://ax.mcp.griddo.io/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 →
get_griddo_editor_doc Get a Griddo editor docs page ~101
Fetch the full Markdown of one Griddo backoffice (Author Experience) documentation page by its path, as returned by search_griddo_editor_docs or list_griddo_editor_docs. Use it when the search excerpt is not enough to answer accurately.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Page path, e.g. '/editor/anadir-imagen'. The '.md' suffix, a leading slash and a full https://docs.griddo.io URL are all accepted. |
No output schema declared.
No examples provided.
list_griddo_editor_docs List Griddo editor docs pages ~60
List every page of the Griddo backoffice (Author Experience) documentation, grouped by section, with title and URL. Use it to get oriented before searching, or when the user asks what the documentation covers.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
No output schema declared.
No examples provided.
search_griddo_editor_docs Search Griddo editor docs ~186
Search the official Griddo documentation for content authors and site administrators (the Griddo backoffice, Author Experience: pages, modules, templates, content types, forms, media gallery, roles, publishing). Returns ranked excerpts with the canonical URL of each page. Use this before answering any question about how to do something in the Griddo backoffice, and cite the URLs you get back. Do NOT use it for developer questions about @griddo/core hooks and components, schema or module code, the Griddo API or the SDK: that is Developer Experience documentation, covered by the separate Griddo DX Docs MCP server.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Documentation language. Spanish is the primary, most complete version; pass 'en' when the user writes in English. |
| limit | integer | – | – |
| query | string | yes | Natural-language query or keywords. Spanish or English. |
No output schema declared.
No examples provided.
How do I install the Griddo AX Docs MCP server?
Griddo AX Docs is a hosted endpoint at https://ax.mcp.griddo.io/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 · ax.mcp.griddo.io
claude mcp add --transport http io-griddo-ax-docs 'https://ax.mcp.griddo.io/mcp'
What is the Griddo AX Docs MCP server?
Griddo AX Docs is an MCP server listed in the public MCP registry as io.griddo/ax-docs. Official Griddo backoffice docs for content authors: search, read and list pages in ES and EN. This page covers its hosted endpoint (https://ax.mcp.griddo.io/mcp).
Is the Griddo AX Docs MCP server safe to use?
Griddo AX Docs scores 76 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 Griddo AX Docs MCP server expose?
Griddo AX Docs exposes 3 tools: search_griddo_editor_docs, get_griddo_editor_doc, list_griddo_editor_docs. Their descriptions and schemas cost roughly 347 tokens of context every time the server is loaded.
Does the Griddo AX Docs MCP server require authentication?
No. We connected to Griddo AX Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Griddo AX Docs MCP server still maintained?
Griddo AX Docs is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.