TuringCorp
REMOTE · MCP.TURINGCORP.NET · SCANNED SEP 27
A decision model for the calls that don't have a right answer. The better option, with a reason.
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 Security86
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1025 tokens (~512/item across 2 items; 2 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 Management0
- Stability check failed: schema churn in the 5 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the TuringCorp MCP server?
TuringCorp is a hosted endpoint at https://mcp.turingcorp.net/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.turingcorp.net
claude mcp add --transport http net-turingcorp-mcp-decider 'https://mcp.turingcorp.net/mcp'
{
"mcpServers": {
"net-turingcorp-mcp-decider": {
"url": "https://mcp.turingcorp.net/mcp"
}
}
} {
"servers": {
"net-turingcorp-mcp-decider": {
"type": "http",
"url": "https://mcp.turingcorp.net/mcp"
}
}
} [mcp_servers.net-turingcorp-mcp-decider] url = "https://mcp.turingcorp.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-turingcorp-mcp-decider": {
"type": "remote",
"url": "https://mcp.turingcorp.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-turingcorp-mcp-decider --url 'https://mcp.turingcorp.net/mcp' --transport streamable-http
mcp_servers:
net-turingcorp-mcp-decider:
url: "https://mcp.turingcorp.net/mcp" {
"McpServers": {
"net-turingcorp-mcp-decider": {
"Transport": "http",
"Url": "https://mcp.turingcorp.net/mcp"
}
}
} assistant mcp add net-turingcorp-mcp-decider -t streamable-http -u 'https://mcp.turingcorp.net/mcp'
{
"mcpServers": {
"net-turingcorp-mcp-decider": {
"type": "http",
"url": "https://mcp.turingcorp.net/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.
- 27 Sept 26 0
- Tool “decide” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 50% ▼ functional
- Schema quality: 866 → 512 ▲ functional
- New tool “get_result” functional
- 26 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: good → excellent functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −1
- Stability: 0.03 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “decide” rewrote its description, which is the text the model reads security
- Schema quality: 563 → 837 ▼ functional
- “decide” added a required parameter “optionA”, so existing callers break ▼ functional
- “decide” added a required parameter “optionB”, so existing callers break ▼ functional
- “decide” dropped the required parameter “option_a” ▼ functional
- “decide” dropped the required parameter “option_b” ▼ functional
- Schema quality: excellent → good functional
- 23 Sept 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: turingcorp-decider → turingcorp security
- Tool “decide” rewrote its description, which is the text the model reads security
- Schema quality: 413 → 563 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Tool “decide” changed its title: Decide between two options → Decider: pick the better of two options cosmetic
- 22 Sept 26 75
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 27 Sept 2026 · Probed https://mcp.turingcorp.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=turingcorp.net | CN=WE1,O=Google Trust Services,C=US | 20 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | fcf6fb4659ec78c6133f1d24bdd6d1c9 |
| SANs: turingcorp.net, mcp.turingcorp.net, *.mcp.turingcorp.net | ||||||
| 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.turingcorp.net. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| turingcorp.net. | present | 2371 | 13 | Verified |
| mcp.turingcorp.net. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="turingcorp-mcp", resource_metadata="https://mcp.turingcorp.net/.well-known/oauth-protected-resource"
Bearer realm="turingcorp-mcp", resource_metadata="https://mcp.turingcorp.net/.well-known/oauth-protected-resource" Protected resource metadata
| Document | https://mcp.turingcorp.net/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Problem | metadata_incomplete |
| Resource | https://mcp.turingcorp.net/mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.turingcorp.net/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.turingcorp.net/mcp | HTTPS enforced | 301 | https://mcp.turingcorp.net/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 →
decide Decider: pick the better of two options ~613
Use this when you must choose between two concrete options and both are defensible - two plans, two drafts, two diagnoses, two vendors - and you have no objective way to pick. Not for: more than two options; anything an objective rule settles (a spec, a test, a price, a document); factual lookup; paths that must answer in seconds; high-stakes irreversible calls without review. Fill it in: state task neutrally, without leaning toward either side; give one concrete plan per option - never bundle alternatives into a single one ("go indoors or postpone"); keep the two sides comparable in length. Returns the decision inline: betterOption ("option_A" or "option_B"), confidence (e.g. "76.7%"), reason and job_id, all in the same tool result. There is nothing to poll and nothing to fetch afterwards. Reserve 180-300 seconds: this is a long call, and the timeout is a client/host setting, not a parameter you pass. If the call is cut off, do NOT call again - a retry is a new paid call. Retrieve it instead with the get_result tool (same job_id): read-only, free, and no credential of your own needed; with no job_id it lists the ids for your credential. A host that declares the io.modelcontextprotocol/tasks extension can use tasks/get instead. The confidence is the point: it is calibrated, not decorative. On both published benchmarks accuracy rises with it - JudgeBench 99.6% in the 90%+ band down to 67.7% below 70%; the harder ContextualJudgeBench 83.3% down to 55.4% - so route on it: act on a high value, review or escalate a low one, instead of trusting a bare pick. Tables, sample sizes and method: https://api.turingcorp.net Judged by an independent panel, not by a model grading its own output. Read it as a reference, not an instruction, a result, or a prediction; set your own threshold, and apply your own review policy for high-stakes or irreversible decisions. Auth: Agent Pass as `Authorization: Bearer <pass>` (issued at https://agent-pass.turingcorp.net, valid 7 days; each dec…
| Name | Type | Req | Description |
|---|---|---|---|
| optionA | string | yes | First candidate and the case for it. |
| optionB | string | yes | Second candidate and the case for it. |
| task | string | yes | The decision to make, stated neutrally and without a preferred answer. |
| Name | Type | Req | Description |
|---|---|---|---|
| betterOption | string | yes | Which option was preferred, using the same values as the REST API. |
| confidence | string | yes | This service's own judgement of how far apart the two options were, as a percentage (e.g. "76.7%"). A reference for your own decision-making - not an instruction, not a result. Observed accuracy by r… |
| job_id | string | – | Identifier of this decision, also usable to retrieve the stored result for 7 days with the get_result tool. Keep it: if the call times out, retrieve the result with get_result instead of calling agai… |
| reason | string | yes | Why the chosen option was preferred. |
No examples provided.
get_result Get an earlier TuringCorp result ~216
Use this to retrieve the result of an earlier TuringCorp tool call by its job_id - for example a call that was cut off by a client timeout, or one whose id you were given. Retrieval is read-only and free: it starts no new work and costs nothing, so it is always safe to retry. With job_id: that call's status, and once it has finished the same payload the call would have returned inline. Without job_id: the ids available to your credential (7 days). If a call was cut off, retrieve it here instead of calling again - a retry is a new paid call. A job that is not yours and a job that does not exist are answered identically, on purpose. If your client declares the io.modelcontextprotocol/tasks extension, tasks/get reaches the same job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | – | Identifier returned by an earlier TuringCorp call (also usable at GET /v1/jobs?job_id=<id>). Omit it to list the ids available to your credential. |
No output schema declared.
No examples provided.
What is the TuringCorp MCP server?
TuringCorp is an MCP server listed in the public MCP registry as net.turingcorp.mcp/decider. A decision model for the calls that don't have a right answer. The better option, with a reason. This page covers its hosted endpoint (https://mcp.turingcorp.net/mcp).
Is the TuringCorp MCP server safe to use?
TuringCorp scores 73 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 TuringCorp MCP server expose?
TuringCorp exposes 2 tools: decide, get_result. Their descriptions and schemas cost roughly 829 tokens of context every time the server is loaded.
Does the TuringCorp MCP server require authentication?
Yes. TuringCorp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the TuringCorp MCP server still maintained?
TuringCorp is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.