MCP.so
Sign In

Trustloop MCP Server

@SMJAI

Basic information

Category

Developer Tools

Transports

stdio

Auth

oauth

Author

SMJAI

Submitted by

Soji Joseph

About Trustloop MCP Server

Governance and audit layer for MCP tool calls. TrustLoop intercepts every AI agent action, logs it to a tamper-evident audit trail, blocks unsafe tools via kill-switch, and anchors proof to the blockchain. Drop it into any MCP setup in minutes, no code changes required.

Trustloop MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "trustloop": {
      "url": "https://trustloop-production.up.railway.app/sse?api_key=<YOUR_TRUSTLOOP_API_KEY>"
    }
  }
}

Trustloop MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

What is Trustloop?

Trustloop is an MCP governance proxy that intercepts tool calls from AI agents, checking them against policy rules before execution. It logs every call and either allows or blocks it, providing oversight and compliance for teams using AI agents.

How to use Trustloop?

Add the server to your claude_desktop_config.json with the provided URL and your API key, then configure policy rules to govern agent tool usage. Get your API key at trustloop.live.

Key features of Trustloop

  • Kill-switch to block specific tools by name
  • Audit log capturing timestamp, tool, arguments, and status
  • Blockchain anchoring of audit log hashes for tamper-evident compliance
  • Multi‑tenant isolation of logs and governance rules
  • Built for EU AI Act and similar global mandates

Use cases of Trustloop

  • Prevent AI agents from executing destructive tool calls
  • Demonstrate regulatory compliance with auditable agent actions
  • Enforce governance policies across multiple agent customers
  • Maintain tamper‑evident records for external audits

Frequently asked questions

1

How does the kill-switch work?

You can block specific tools by name before they can cause harm. For example, `delete_all_files` is blocked by default.

2

What is the audit log?

Every tool call is captured with its timestamp, tool name, arguments, and status (allowed or blocked).

3

How does blockchain anchoring work?

A SHA-256 hash of the audit logs is recorded on‑chain, making logs tamper‑evident for compliance.

4

Is Trustloop multi‑tenant?

Yes, each customer gets isolated logs and governance rules.

5

What do I need to run Trustloop?

You need an API key from trustloop.live and to configure an MCP client (e.g., Claude Desktop) with the server URL.

Comments

More Developer Tools MCP servers