Skip to content

TuringCorp MCP server

net.turingcorp.mcp/decidermcp.turingcorp.netstreamable-httpv1.0.3Scanned

A decision model for the calls that don't have a right answer. The better option, with a reason.

2 tools: 1 do something that can't be undone and 1 only read.

Tools: 0 delete, 1 irreversible, 0 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 5 findings

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the TuringCorp MCP server can do

The TuringCorp MCP server is published by mcp.turingcorp.net, a domain the MCP Registry verified. It has 2 tools. It can do things that cannot be undone, such as sending, paying or publishing (decide), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 5 findings (credentials-mention, long-description and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 18, 2026, version 1.0.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Can't be undone 1Claude Code: ask
  • decideUse 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.3 findings

    Why it is in this group

    • The description says "irreversible".
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...(same job_id): read-only, free, and no credential of your own needed; with no job_id it l..."

      What this check looks for
    • Info

      The description is 2,400 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ge}, where http_status is the upstream status (the tool call itself is HTTP 200)."

      What this check looks for
    • Warn

      The server marks "decide" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":false}; The description says "irreversible".

      What this check looks for
    Description, as the server wrote it
    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 decision is a paid call). On invalid_credential, sign in there and re-roll. Errors: a credential problem is rejected before the call - HTTP 401 with WWW-Authenticate; a business failure (e.g. insufficient balance) comes back as a tool result with isError true plus a second JSON block {error, http_status, action_url, message}, where http_status is the upstream status (the tool call itself is HTTP 200).

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: false
Only reads 1Show 1 read-only tool
  • get_resultUse 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.2 findings

    Why it is in this group

    • The name "get_result" says "get": a word for reading.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "...thout job_id: the ids available to your credential (7 days). If a call was cut off, retrie..."

      What this check looks for
    • Info

      The input schema at properties.job_id.description mentions "credential".

      Matched text

      inputSchema.properties.job_id.description: "...it it to list the ids available to your credential."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.turingcorp.net/.well-known/oauth-protected-resource/mcp
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.turingcorp.net/mcp: tools/list returned 2 tools to an anonymous client, including decide (irreversible)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn4 info
  • Warndecide

    The server marks "decide" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":false}; The description says "irreversible".

    What this check looks for
  • Infodecide

    The description mentions "credential".

    Matched text

    description: "...(same job_id): read-only, free, and no credential of your own needed; with no job_id it l..."

    What this check looks for
  • Infodecide

    The description is 2,400 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ge}, where http_status is the upstream status (the tool call itself is HTTP 200)."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "...thout job_id: the ids available to your credential (7 days). If a call was cut off, retrie..."

    What this check looks for
  • The input schema at properties.job_id.description mentions "credential".

    Matched text

    inputSchema.properties.job_id.description: "...it it to list the ids available to your credential."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http decider https://mcp.turingcorp.net/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http decider https://mcp.turingcorp.net/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__decider__get_result"
    ],
    "ask": [
      "mcp__decider__decide"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as decider. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/net.turingcorp.mcp/decider/verify?hash=2d51ec483d76679bea1a2d11c1ee4514da9e9fb74554a5e338d8cd4fff3026f1" | jq -e '.changed == false'

Pinned hash 2d51ec483d76, from Nov 18, 2026, 01:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/net.turingcorp.mcp/decider/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for net.turingcorp.mcp/decider
[![Anlyon Radar](https://radar.anlyon.com/badge/net.turingcorp.mcp/decider.svg)](https://radar.anlyon.com/servers/net.turingcorp.mcp/decider)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:53 UTC.

TuringCorp MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TuringCorp MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the TuringCorp MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the TuringCorp MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: decide.

What tools does the TuringCorp MCP server have?

2 tools: 1 irreversible, 1 read. decide and get_result.

Does the TuringCorp MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TuringCorp MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the TuringCorp MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.