Schemadriftgate Mcp

com.clauxel.schemadriftgatePublished by schemadriftgate.clauxel.comOfficial publisherv1.0.0Updated Oct 24, 2026

Paid remote MCP for schema drift checks, approvals, receipts, and release audit logs.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Paid remote MCP that lets an assistant check MCP tool-schema drift, approve schemas, record compatibility receipts and export release audit logs.

What you can do
Check tool schemas for drift and breaking changes before agents call a changed interface, and get explanations of breaking changes in plain terms. Approve tool schemas and record compatibility receipts for those approvals. Export release audit logs of schema decisions. Access is through a hosted Streamable HTTP endpoint with a bearer token.
When to use it
Useful when you publish or consume MCP tool schemas and want a gate that flags breaking changes before agents call the wrong interface, with approvals and an audit trail for releases.
Requirements
A remote Streamable HTTP endpoint; an MCP client that supports remote Streamable HTTP servers; a paid plan chosen on the product website; a bearer token issued there, sent in the Authorization header. Network access is required.
Before you install
It is a paid hosted service, so using it involves a plan and spending. The bearer token is a credential and must be kept secret. Approvals and receipts write records to the hosted service, and schema data is sent to a third-party server.

Installation

In SourceWeft

  1. Open Schemadriftgate Mcp in the dashboard and add it to a workspace.
  2. 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/com.clauxel.schemadriftgate%2Fschemadriftgate-mcp/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": {
    "schemadriftgate": {
      "type": "http",
      "url": "https://schemadriftgate.clauxel.com/mcp"
    }
  }
}

README

Schema Drift Gate MCP

Block breaking MCP tool-schema changes before agents call the wrong interface.

Paid remote MCP for schema drift checks, tool-schema approvals, compatibility receipts, breaking-change explanations, and release audit logs.

Public Endpoints

Access

This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website.

http
Authorization: Bearer <token>

Unauthenticated browser visits to /mcp return a clear JSON error instead of internal details.

Tools

  • check_schema_drift
  • approve_tool_schema
  • record_tool_receipt
  • explain_breaking_change
  • export_audit_log

Quick Start

  1. Open the website and choose a plan.
  2. Create or request an API token.
  3. Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
  4. Send JSON-RPC requests with the bearer token.

Useful Links

Status

This repository is a public documentation and directory-submission reference for the hosted service. It does not contain the private production source code.

Source: README.md at commit a9b17e7

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.