chore: list the MCP Registry entry (com.vericto/sql-firewall); code o…

.github/CODEOWNERS

@@ -1,2 +1,3 @@
-# Default owner for everything in this repository.
-* @vericto
+# Code owners: GitHub requests a review from these accounts on every pull request.
+# Informational only: branch protection does not require code-owner approval.
+* @vericto @donkan168

mcp-registry/README.md

@@ -0,0 +1,17 @@
+# MCP Registry entry
+
+`server.json` is the entry published to the official MCP Registry
+(<https://registry.modelcontextprotocol.io>) as `com.vericto/sql-firewall`: the
+remote Vericto MCP server at `https://mcp.vericto.com/mcp` (streamable HTTP,
+`X-API-Key` header). It is kept here so anyone can see exactly what is listed.
+
+Publishing uses DNS namespace verification for `vericto.com` (a `v=MCPv1` TXT
+record at the apex) and `mcp-publisher`:
+
+```bash
+mcp-publisher login dns --domain vericto.com --private-key "<hex private key>"
+mcp-publisher validate && mcp-publisher publish
+```
+
+Bump `version` for every change, because the registry rejects a version that is
+already published.

mcp-registry/server.json

@@ -0,0 +1,22 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
+  "name": "com.vericto/sql-firewall",
+  "title": "Vericto SQL Firewall",
+  "description": "Check SQL against your Vericto rules before it runs: blocks destructive or risky statements.",
+  "version": "1.0.0",
+  "websiteUrl": "https://vericto.com/docs/mcp",
+  "remotes": [
+    {
+      "type": "streamable-http",
+      "url": "https://mcp.vericto.com/mcp",
+      "headers": [
+        {
+          "name": "X-API-Key",
+          "description": "Vericto API key (dashboard > Settings > API keys)",
+          "isRequired": true,
+          "isSecret": true
+        }
+      ]
+    }
+  ]
+}