Trustlayer

io.tooloraclePublished by tooloracle.ioOfficial publisherv1.0.0Updated Oct 24, 2026

FeedOracle Trust Layer - 10-tool cross-server trust: signing, anchoring, verification.

The publisher's own server: Accessoracle

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Server details

Identifier: io.tooloracle/trustlayer
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to tooloracle.io, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.tooloracle%2Ftrustlayer.svg)](https://sourceweft.com/mcp/io.tooloracle%2Ftrustlayer?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A remote MCP server offering ten cross-server trust tools for signing, anchoring and verifying data.

What you can do: Sign data across servers with the trust layer's signing tools. Anchor signed records so they can be referenced later. Verify signatures and anchored records to check integrity. The tools are described as cross-server, so they are meant to work alongside other MCP servers.
When to use it: Relevant when an assistant needs to sign, anchor or verify data produced across several MCP servers and you want a shared trust layer for those operations.
Requirements: A remote endpoint at tooloracle.io reached over streamable HTTP. The manifest declares no authentication, environment variables or headers, and no local package is needed.

Before you install

The manifest declares no authentication, so consider what data you send to a third-party endpoint. Signing and anchoring write records; confirm what is stored and where before relying on it. No tool list or documentation is provided, so the exact behavior is unverified.

Installation

In SourceWeft

Open Trustlayer in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.tooloracle%2Ftrustlayer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "trustlayer": {
      "type": "http",
      "url": "https://tooloracle.io/trust/mcp/"
    }
  }
}

README

This repository has no README.

Tools

SourceWeft has not read this server's tools yet.

Version history

v1.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.