ToGO
REMOTE · MCP.TO-GO.DEV
ToGO docs and plugins for agents: a full-stack Go + React framework, plus plugin submission.
Available components
Last scanned (15 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Developer Tools
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 297 tokens (~49/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 63
First indexed and scored.
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 17 Oct 2026 · Probed https://mcp.to-go.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=to-go.dev | CN=WE1,O=Google Trust Services,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 5691f10ed63184940e179a7f2b07a46e |
| SANs: to-go.dev, *.to-go.dev | ||||||
| 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 mcp.to-go.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| to-go.dev. | present | 2371 | 13 | Verified |
| mcp.to-go.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.to-go.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.to-go.dev/mcp | HTTPS enforced | 301 | https://mcp.to-go.dev/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 →
framework_overview ~24
What togo is, its stack, and how to start a project.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_doc ~41
Fetch a repo's full README/documentation as Markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| repo | string | yes | repo slug, e.g. 'cli', 'togo', 'ui' |
No output schema declared.
No examples provided.
get_plugin ~38
Get a plugin's details and full README.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | plugin slug, e.g. 'auth' or 'cache-redis' |
No output schema declared.
No examples provided.
list_plugins ~32
List the togo plugin marketplace (installable capabilities, fetched live).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | optional category filter |
No output schema declared.
No examples provided.
search_docs ~36
Search togo repos and docs by keyword (live).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | keyword(s) to match against repo names + descriptions |
No output schema declared.
No examples provided.
submit_plugin ~69
Submit a new plugin to the togo marketplace. Returns a prefilled GitHub issue URL (the plugin-submission form).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| description | string | yes | – |
| name | string | yes | – |
| repo_url | string | yes | GitHub URL of the plugin repo |
No output schema declared.
No examples provided.
How do I install the ToGO MCP server?
ToGO is a hosted endpoint at https://mcp.to-go.dev/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 · mcp.to-go.dev
claude mcp add --transport http togo-framework-togo 'https://mcp.to-go.dev/mcp'
What is the ToGO MCP server?
ToGO is an MCP server listed in the public MCP registry as io.github.togo-framework/togo. ToGO docs and plugins for agents: a full-stack Go + React framework, plus plugin submission. This page covers its hosted endpoint (https://mcp.to-go.dev/mcp).
Is the ToGO MCP server safe to use?
ToGO scores 65 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 ToGO MCP server expose?
ToGO exposes 6 tools: framework_overview, list_plugins, get_plugin, search_docs, get_doc, submit_plugin. Their descriptions and schemas cost roughly 240 tokens of context every time the server is loaded.
Does the ToGO MCP server require authentication?
No. We connected to ToGO without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ToGO MCP server still maintained?
ToGO is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.