Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

TuringTap

REMOTE · MCP.TURINGTAP.AI · SCANNED AUG 24

Live decrypted HTTP(S) traffic visibility for AI agents, plus human handoff for 2FA and captchas.

Available components

23 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → 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.

Install

How do I install the TuringTap MCP server?

TuringTap is a hosted endpoint at https://mcp.turingtap.ai/sse, 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.turingtap.ai

# add to Claude Code
claude mcp add --transport http ai-turingtap-turingtap 'https://mcp.turingtap.ai/sse'
// .cursor/mcp.json
{
  "mcpServers": {
    "ai-turingtap-turingtap": {
      "url": "https://mcp.turingtap.ai/sse"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ai-turingtap-turingtap": {
      "type": "http",
      "url": "https://mcp.turingtap.ai/sse"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ai-turingtap-turingtap]
url = "https://mcp.turingtap.ai/sse"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-turingtap-turingtap": {
      "type": "remote",
      "url": "https://mcp.turingtap.ai/sse",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ai-turingtap-turingtap --url 'https://mcp.turingtap.ai/sse' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ai-turingtap-turingtap:
    url: "https://mcp.turingtap.ai/sse"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ai-turingtap-turingtap": {
      "Transport": "http",
      "Url": "https://mcp.turingtap.ai/sse"
    }
  }
}
# add to Vellum
assistant mcp add ai-turingtap-turingtap -t streamable-http -u 'https://mcp.turingtap.ai/sse'
// mcp.json
{
  "mcpServers": {
    "ai-turingtap-turingtap": {
      "type": "http",
      "url": "https://mcp.turingtap.ai/sse"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 23 Aug 26 23

    First indexed and scored.

Diagnostics

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 24 Aug 2026 · Probed https://mcp.turingtap.ai/sse

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.turingtap.ai CN=WR3,O=Google Trust Services,C=US 16 Jul 2026 14 Oct 2026 RSA 2048 SHA256-RSA c1c2e602d211cb130a62487246c0c8ef
SANs: mcp.turingtap.ai
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d
DNSSEC insecure

Validation of mcp.turingtap.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
turingtap.ai. 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 405
Transports 2 probes
Transport URL Outcome Status Location
sse https://mcp.turingtap.ai/sse Auth required 401
http (plaintext) http://mcp.turingtap.ai/sse HTTPS enforced 302 https://mcp.turingtap.ai/sse
MCP tools

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.

No tool schema has been captured from this endpoint yet.

Common questions

What is the TuringTap MCP server?

TuringTap is an MCP server listed in the public MCP registry as ai.turingtap/turingtap. Live decrypted HTTP(S) traffic visibility for AI agents, plus human handoff for 2FA and captchas. This page covers its hosted endpoint (https://mcp.turingtap.ai/sse).

Is the TuringTap MCP server safe to use?

TuringTap scores 23 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 TuringTap MCP server require authentication?

No. We connected to TuringTap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the TuringTap MCP server still maintained?

TuringTap is still listed as active in the MCP registry. We last reached this channel on 24 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.