3TG Test Generation
REMOTE · MCP.3TG.DEV · SCANNED OCT 4
3rd Generation Testing (3TG) — generate deterministic test suites from Markdown spec tables via MCP.
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 Security63
- 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 connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the 3TG Test Generation MCP server?
3TG Test Generation is a hosted endpoint at https://mcp.3tg.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.3tg.dev
claude mcp add --transport http dev-3tg-mcp 'https://mcp.3tg.dev/mcp'
{
"mcpServers": {
"dev-3tg-mcp": {
"url": "https://mcp.3tg.dev/mcp"
}
}
} {
"servers": {
"dev-3tg-mcp": {
"type": "http",
"url": "https://mcp.3tg.dev/mcp"
}
}
} [mcp_servers.dev-3tg-mcp] url = "https://mcp.3tg.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-3tg-mcp": {
"type": "remote",
"url": "https://mcp.3tg.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-3tg-mcp --url 'https://mcp.3tg.dev/mcp' --transport streamable-http
mcp_servers:
dev-3tg-mcp:
url: "https://mcp.3tg.dev/mcp" {
"McpServers": {
"dev-3tg-mcp": {
"Transport": "http",
"Url": "https://mcp.3tg.dev/mcp"
}
}
} assistant mcp add dev-3tg-mcp -t streamable-http -u 'https://mcp.3tg.dev/mcp'
{
"mcpServers": {
"dev-3tg-mcp": {
"type": "http",
"url": "https://mcp.3tg.dev/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.
- 4 Oct 26 −40
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.83 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 3 Oct 26 −3
- Stability: pass → 0.83 functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 2 Oct 26 +43
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: 860 → 1138 ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 1 Oct 26 −4
- Endpoint reachability: reachable → not serving MCP ▼ security
- Capabilities: pass → unverified ▼ functional
- 30 Sept 26 −41
- Tool safety: pass → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 29 Sept 26 +3
- Schema quality: 1138 → 860 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 28 Sept 26 +38
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +4
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day 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 6 Oct 2026 · Probed https://mcp.3tg.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.3tg.dev | CN=YR1,O=Let's Encrypt,C=US | 24 Sept 2026 | 23 Dec 2026 | RSA 2048 | SHA256-RSA | 59da94691a840a408c9c574ab795bc6efd3 |
| SANs: mcp.3tg.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.3tg.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| 3tg.dev. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.3tg.dev/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.3tg.dev/mcp | HTTPS enforced | 308 | https://mcp.3tg.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 →
No tool schema has been captured from this endpoint yet.
What is the 3TG Test Generation MCP server?
3TG Test Generation is an MCP server listed in the public MCP registry as dev.3tg/mcp. 3rd Generation Testing (3TG), generate deterministic test suites from Markdown spec tables via MCP. This page covers its hosted endpoint (https://mcp.3tg.dev/mcp).
Is the 3TG Test Generation MCP server safe to use?
3TG Test Generation scores 35 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.
Does the 3TG Test Generation MCP server require authentication?
No. We connected to 3TG Test Generation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the 3TG Test Generation MCP server still maintained?
3TG Test Generation is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.