Skip to content

trust-oracle MCP server

io.github.New1Direction/trust-oracleNew1Directionstreamable-httpv1.0.0Scanned

Independent A-F trust grade for any MCP server, watched for drift. Free, never for sale.

3 tools: 3 change things.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the trust-oracle MCP server can do

The trust-oracle MCP server is published by the GitHub account New1Direction. It has 3 tools. It can create or change data (3 tools: grade_mcp_server, check_mcp_drift and verify_before_execute), but cannot delete data. None of its tools only reads.

3 tools can send data out of your system (grade_mcp_server, check_mcp_drift and verify_before_execute).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.0.

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.

3 tools

Changes things 3Claude Code: ask
  • check_mcp_driftCheck whether an MCP server's tool definitions have changed since it was last trusted (rug-pull / schema-drift detection, the CVE-2025-54136 class).Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Check whether an MCP server's tool definitions have changed since it was last trusted (rug-pull / schema-drift detection, the CVE-2025-54136 class). Returns how long the tool surface has been stable, how many times it has changed, and the last change. Use after approval to detect post-trust mutation.
  • grade_mcp_serverIndependently grade an MCP server (A–F) BEFORE connecting an agent to it.Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Independently grade an MCP server (A–F) BEFORE connecting an agent to it. Returns spec-conformance, security (OWASP MCP Top 10), reliability, tool-hygiene and transparency sub-scores plus a connect/caution/avoid recommendation. Audited by wmcp.sh; the grade is free and never for sale.
  • verify_before_executeVerify an MCP server immediately BEFORE you execute any of its tools.Can send data outNo findings

    Why it is in this group

    • The name "verify_before_execute" says "execute": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Verify an MCP server immediately BEFORE you execute any of its tools. Combines the continuously-watched trust grade and live drift status into a single connect/caution/avoid verdict (ok | caution | drifted | failing | ungraded), so you can gate the call in one step. Free, read-tier. The grade is independent and never for sale.

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.

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 out3
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, 18:59 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
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

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

    Matched text

    https://wmcp.sh/mcp/trust: tools/list returned 3 tools to an anonymous client, including grade_mcp_server (write), check_mcp_drift (write), verify_before_execute (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http trust-oracle https://wmcp.sh/mcp/trust
claude mcp add --transport http trust-oracle https://wmcp.sh/mcp/trust

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": [],
    "ask": [
      "mcp__trust-oracle__grade_mcp_server",
      "mcp__trust-oracle__check_mcp_drift",
      "mcp__trust-oracle__verify_before_execute"
    ],
    "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 trust-oracle. Review it before you use it.

Capability tags behind 3 rules
  • mcp__trust-oracle__grade_mcp_server outbound
  • mcp__trust-oracle__check_mcp_drift outbound
  • mcp__trust-oracle__verify_before_execute outbound

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/io.github.New1Direction/trust-oracle/verify?hash=b0a68a0a42ad41e5b38c8967bed47dc2a21a9eeaca43d903cb8eb1131d157224" | jq -e '.changed == false'

Pinned hash b0a68a0a42ad, from Nov 16, 2026, 02:17 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.New1Direction/trust-oracle/changes.xml

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

Badge

Anlyon Radar badge for io.github.New1Direction/trust-oracle
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.New1Direction/trust-oracle.svg)](https://radar.anlyon.com/servers/io.github.New1Direction/trust-oracle)

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

trust-oracle MCP server: questions and answers

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

Is the trust-oracle MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 0 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 trust-oracle MCP server delete data?

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

Can the trust-oracle MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the trust-oracle MCP server have?

3 tools: 3 write. grade_mcp_server, check_mcp_drift and verify_before_execute.

Does the trust-oracle MCP server need sign-in or OAuth?

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

Does the trust-oracle MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): grade_mcp_server, check_mcp_drift and verify_before_execute.

Has the trust-oracle MCP server changed its tools?

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