@jigyasudham/veto 2.1.1 → 2.5.0

package/.mcp-tools/LICENSE

@@ -0,0 +1,216 @@
+The MCP project is undergoing a licensing transition from the MIT License to the Apache License, Version 2.0 ("Apache-2.0"). All new code and specification contributions to the project are licensed under Apache-2.0. Documentation contributions (excluding specifications) are licensed under CC-BY-4.0.
+
+Contributions for which relicensing consent has been obtained are licensed under Apache-2.0. Contributions made by authors who originally licensed their work under the MIT License and who have not yet granted explicit permission to relicense remain licensed under the MIT License.
+
+No rights beyond those granted by the applicable original license are conveyed for such contributions.
+
+---
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to the Licensor for inclusion in the Work by the copyright
+      owner or by an individual or Legal Entity authorized to submit on behalf
+      of the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+---
+
+MIT License
+
+Copyright (c) 2024-2025 Model Context Protocol a Series of LF Projects, LLC.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+---
+
+Creative Commons Attribution 4.0 International (CC-BY-4.0)
+
+Documentation in this project (excluding specifications) is licensed under
+CC-BY-4.0. See https://creativecommons.org/licenses/by/4.0/legalcode for
+the full license text.

package/.mcp-tools/README.md

@@ -0,0 +1,153 @@
+# MCP Registry
+
+The MCP registry provides MCP clients with a list of MCP servers, like an app store for MCP servers.
+
+[**📤 Publish my MCP server**](docs/modelcontextprotocol-io/quickstart.mdx) | [**⚡️ Live API docs**](https://registry.modelcontextprotocol.io/docs) | [**👀 Ecosystem vision**](docs/design/ecosystem-vision.md) | 📖 **[Full documentation](./docs)**
+
+## Development Status
+
+**2025-10-24 update**: The Registry API has entered an **API freeze (v0.1)** 🎉. For the next month or more, the API will remain stable with no breaking changes, allowing integrators to confidently implement support. This freeze applies to v0.1 while development continues on v0. We'll use this period to validate the API in real-world integrations and gather feedback to shape v1 for general availability. Thank you to everyone for your contributions and patience—your involvement has been key to getting us here!
+
+**2025-09-08 update**: The registry has launched in preview 🎉 ([announcement blog post](https://blog.modelcontextprotocol.io/posts/2025-09-08-mcp-registry-preview/)). While the system is now more stable, this is still a preview release and breaking changes or data resets may occur. A general availability (GA) release will follow later. We'd love your feedback in [GitHub discussions](https://github.com/modelcontextprotocol/registry/discussions/new?category=ideas) or in the [#registry-dev Discord](https://discord.com/channels/1358869848138059966/1369487942862504016) ([joining details here](https://modelcontextprotocol.io/community/communication)).
+
+Current key maintainers:
+- **Adam Jones** (Anthropic) [@domdomegg](https://github.com/domdomegg)  
+- **Tadas Antanavicius** (PulseMCP) [@tadasant](https://github.com/tadasant)
+- **Toby Padilla** (GitHub) [@toby](https://github.com/toby)
+- **Radoslav (Rado) Dimitrov** (Stacklok) [@rdimitrov](https://github.com/rdimitrov)
+
+## Contributing
+
+We use multiple channels for collaboration - see [modelcontextprotocol.io/community/communication](https://modelcontextprotocol.io/community/communication).
+
+Often (but not always) ideas flow through this pipeline:
+
+- **[Discord](https://modelcontextprotocol.io/community/communication)** - Real-time community discussions
+- **[Discussions](https://github.com/modelcontextprotocol/registry/discussions)** - Propose and discuss product/technical requirements
+- **[Issues](https://github.com/modelcontextprotocol/registry/issues)** - Track well-scoped technical work  
+- **[Pull Requests](https://github.com/modelcontextprotocol/registry/pulls)** - Contribute work towards issues
+
+### Quick start:
+
+#### Pre-requisites
+
+- **Docker**
+- **Go 1.24.x**
+- **ko** - Container image builder for Go ([installation instructions](https://ko.build/install/))
+- **golangci-lint v2.4.0**
+
+#### Running the server
+
+```bash
+# Start full development environment
+make dev-compose
+```
+
+This starts the registry at [`localhost:8080`](http://localhost:8080) with PostgreSQL. The database uses ephemeral storage and is reset each time you restart the containers, ensuring a clean state for development and testing.
+
+**Note:** The registry uses [ko](https://ko.build) to build container images. The `make dev-compose` command automatically builds the registry image with ko and loads it into your local Docker daemon before starting the services.
+
+By default, the registry seeds from the production API with a filtered subset of servers (to keep startup fast). This ensures your local environment mirrors production behavior and all seed data passes validation. For offline development you can seed from a file without validation with `MCP_REGISTRY_SEED_FROM=data/seed.json MCP_REGISTRY_ENABLE_REGISTRY_VALIDATION=false make dev-compose`.
+
+The setup can be configured with environment variables in [docker-compose.yml](./docker-compose.yml) - see [.env.example](./.env.example) for a reference.
+
+<details>
+<summary>Alternative: Running a pre-built Docker image</summary>
+
+Pre-built Docker images are automatically published to GitHub Container Registry. Note that the image does not bundle PostgreSQL, so you need to run your own and point the registry at it via `MCP_REGISTRY_DATABASE_URL` (see [docker-compose.yml](./docker-compose.yml) for a working example):
+
+```bash
+# Run latest stable release
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:latest
+
+# Run latest from main branch (continuous deployment)
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main
+
+# Run specific release version
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:v1.0.0
+
+# Run development build from main branch
+docker run -p 8080:8080 ghcr.io/modelcontextprotocol/registry:main-20250906-abc123d
+```
+
+**Available tags:** 
+- **Releases**: `latest`, `v1.0.0`, `v1.1.0`, etc.
+- **Continuous**: `main` (latest main branch build)
+- **Development**: `main-<date>-<sha>` (specific commit builds)
+
+</details>
+
+#### Publishing a server
+
+To publish a server, we've built a simple CLI. You can use it with:
+
+```bash
+# Build the latest CLI
+make publisher
+
+# Use it!
+./bin/mcp-publisher --help
+```
+
+See [the publisher guide](./docs/modelcontextprotocol-io/quickstart.mdx) for more details.
+
+#### Other commands
+
+```bash
+# Run lint, unit tests and integration tests
+make check
+```
+
+There are also a few more helpful commands for development. Run `make help` to learn more, or look in [Makefile](./Makefile).
+
+<!--
+For Claude and other AI tools: Always prefer make targets over custom commands where possible.
+-->
+
+## Architecture
+
+### Project Structure
+
+```
+├── cmd/                     # Application entry points
+│   └── publisher/           # Server publishing tool
+├── data/                    # Seed data
+├── deploy/                  # Deployment configuration (Pulumi)
+├── docs/                    # Documentation
+├── internal/                # Private application code
+│   ├── api/                 # HTTP handlers and routing
+│   ├── auth/                # Authentication (GitHub OAuth, JWT, namespace blocking)
+│   ├── config/              # Configuration management
+│   ├── database/            # Data persistence (PostgreSQL)
+│   ├── service/             # Business logic
+│   ├── telemetry/           # Metrics and monitoring
+│   └── validators/          # Input validation
+├── pkg/                     # Public packages
+│   ├── api/                 # API types and structures
+│   │   └── v0/              # Version 0 API types
+│   └── model/               # Data models for server.json
+├── scripts/                 # Development and testing scripts
+├── tests/                   # Integration tests
+└── tools/                   # CLI tools and utilities
+    └── validate-*.sh        # Schema validation tools
+```
+
+### Authentication
+
+Publishing supports multiple authentication methods:
+- **GitHub OAuth** - For publishing by logging into GitHub
+- **GitHub OIDC** - For publishing from GitHub Actions
+- **DNS verification** - For proving ownership of a domain and its subdomains
+- **HTTP verification** - For proving ownership of a domain
+
+The registry validates namespace ownership when publishing. E.g. to publish...:
+- `io.github.domdomegg/my-cool-mcp` you must login to GitHub as `domdomegg`, or be in a GitHub Action on domdomegg's repos
+- `me.adamjones/my-cool-mcp` you must prove ownership of `adamjones.me` via DNS or HTTP challenge
+
+## Community Projects
+
+Check out [community projects](docs/community-projects.md) to explore notable registry-related work created by the community.
+
+## More documentation
+
+See the [documentation](./docs) for more details if your question has not been answered here!

package/LAUNCH-KIT.md

@@ -0,0 +1,211 @@
+# Veto Launch Kit
+
+Ready-to-paste copy for distribution. Facts current as of v2.1.2 (npm latest + official MCP Registry).
+Core hook: **89 agentic tools + a 49-specialist agent council for every major AI CLI, at zero extra
+token cost on subscription plans.**
+
+Canonical links:
+- npm: https://www.npmjs.com/package/@jigyasudham/veto
+- GitHub: https://github.com/jigyasudham/veto
+- MCP Registry: `io.github.jigyasudham/veto`
+- Quickstart: `npx @jigyasudham/veto init`  (or `npm i -g @jigyasudham/veto && veto init`)
+
+> Honesty guardrail used throughout: "zero cost" = subscription plans (Claude Max, Gemini Advanced…).
+> On API/pay-per-token billing, MCP Sampling calls count toward usage. Keep that caveat in every post.
+
+---
+
+## 1. awesome-mcp-servers PR
+
+**Repo:** https://github.com/punkpeye/awesome-mcp-servers
+**Section:** `## 🤖 Coding Agents` (alt: `## 🛠️ Developer Tools`)
+**Legend used:** 📇 TypeScript · 🏠 local service · 🍎 macOS · 🪟 Windows · 🐧 Linux
+
+**Entry line (alphabetical by `owner/name` within the section):**
+
+```
+- [jigyasudham/veto](https://github.com/jigyasudham/veto) 📇 🏠 🍎 🪟 🐧 - 89 agentic tools and a 49-specialist agent council (Lead Dev, Architect, Security…) for every major AI CLI — Claude Code, Codex, Gemini, Cursor, Windsurf. Self-learning router, cross-platform memory, deterministic agents that optionally upgrade to LLM. Zero extra token cost on subscriptions.
+```
+
+**Submit steps:**
+```bash
+gh repo fork punkpeye/awesome-mcp-servers --clone
+# add the line under the Coding Agents section, keeping alphabetical order
+git checkout -b add-veto
+git commit -am "Add Veto — 89 MCP tools + 49-agent council for every AI CLI"
+git push -u origin add-veto
+gh pr create --repo punkpeye/awesome-mcp-servers --title "Add Veto" --body "Adds Veto: an MCP server giving every major AI CLI a 49-specialist agent council + 89 tools, using existing subscriptions (no API keys). MIT, on the official MCP registry as io.github.jigyasudham/veto."
+```
+
+---
+
+## 2. Show HN
+
+**Title (submit the GitHub URL as the link):**
+```
+Show HN: Veto – 89 MCP tools and a 49-agent council for every AI CLI
+```
+
+**First comment (post immediately after submitting):**
+```
+Hi HN — I built Veto, a single MCP server that plugs into whatever AI CLI you already
+use (Claude Code, Codex, Gemini, Cursor, Windsurf, Zed, JetBrains) and gives it 89 tools
+and a council of 49 specialist agents — code review, security/secrets scanning, a 7-agent
+"should we build this" debate, CI gates, SDD agents, and persistent memory that follows you
+across CLIs.
+
+The design decision I'd most like feedback on: the 42 worker agents are *deterministic
+expert modules by default* (regex/AST secret detection, OWASP/CWE rules, complexity metrics)
+— they run offline and cost zero tokens. When your client supports MCP Sampling they
+optionally upgrade to real LLM reasoning on your existing subscription. So "49 agents" isn't
+49 LLM calls; it's mostly real code with an LLM layer you opt into. The 7-agent Council is
+the LLM-first part (it debates trade-offs before you build) and falls back to a deterministic
+verdict when Sampling isn't available.
+
+Cost: on a subscription (Claude Max, Gemini Advanced) the LLM calls ride your existing plan,
+so there's no extra bill. On API/pay-per-token billing those Sampling calls do count — `veto
+init` detects API keys and warns you.
+
+It's MIT, on npm and the official MCP registry. Try it: `npx @jigyasudham/veto init`
+
+Repo: https://github.com/jigyasudham/veto
+
+Happy to go deep on the router (it re-tunes its tier thresholds every 20 recorded outcomes)
+or the cross-CLI memory/handoff. What would you want a tool like this to NOT do?
+```
+
+> HN tips: post Tue–Thu ~8–10am ET. Don't ask for upvotes. Reply fast and non-defensively;
+> the skeptical "isn't 89 tools bloat?" question is your best moment — answer it with the
+> deterministic-vs-LLM architecture above.
+
+---
+
+## 3. Reddit posts (tailored — do NOT cross-post identical text)
+
+### r/ClaudeAI  (and r/ClaudeCode)
+**Title:** I gave Claude Code a 49-agent council + persistent memory across CLIs — open source, no API keys
+**Body:**
+```
+Veto is an MCP server I've been building that adds 89 tools + 49 specialist agents to Claude
+Code using your existing Claude subscription (no separate API key, no extra token bill on
+Max/Pro).
+
+What it actually does day to day:
+- /code-review and security/secrets scans as MCP tools
+- a 7-agent Council (Lead Dev, Architect, Security, Devil's Advocate, Legal, PM, UX) that
+  debates a plan before you build it
+- memory that saves your session and restores it in Gemini CLI or Codex if you switch — the
+  handoff carries full context
+- a self-learning router that re-tunes which model tier handles which task
+
+Most worker agents are deterministic (real OWASP/CWE/secret-detection code), and upgrade to
+LLM reasoning via MCP Sampling only when you ask — so it works offline and costs nothing extra
+on a subscription. (API billing: Sampling calls do count; it warns you.)
+
+MIT, on npm + the official MCP registry. `npx @jigyasudham/veto init` sets it up for every CLI
+it detects. Repo + GIF: https://github.com/jigyasudham/veto
+
+Would love feedback on what's missing.
+```
+
+### r/LocalLLaMA
+**Title:** MCP server with 49 agents that run deterministically offline + optional local LLM — MIT
+**Body:**
+```
+Sharing Veto in case it's useful here: it's an MCP server whose 42 worker agents are
+hand-written deterministic modules (AST/regex secret detection, OWASP/CWE rules, complexity
+metrics) — they run offline at zero token cost. There's a local-LLM tool and MCP Sampling
+support, so you can route the reasoning layer to a local model instead of a hosted one.
+
+It also does cross-CLI session memory, a multi-agent council debate, CI gates, and secrets
+scanning, and works with Claude Code / Codex / Gemini / Cursor / Windsurf / Zed / JetBrains.
+
+MIT, npm + official MCP registry. `npx @jigyasudham/veto init`.
+Repo: https://github.com/jigyasudham/veto — keen on feedback re: wiring it to local backends.
+```
+
+### r/ChatGPTCoding
+**Title:** Open-source MCP server: 89 tools + 49-agent council that works across Codex, Claude, Gemini & Cursor
+**Body:**
+```
+Veto is an MCP server that gives whatever AI coding CLI you use (Codex, Claude Code, Gemini,
+Cursor, Windsurf) a shared layer: 89 tools, a 49-specialist agent council, code review +
+security scanning, CI gates, and memory that follows you when you switch tools.
+
+The agents are deterministic by default and upgrade to LLM reasoning only when your client
+supports it — so on a subscription there's no extra token cost (API billing does count; it
+warns you). MIT, on npm + the official MCP registry.
+
+Setup is one command: `npx @jigyasudham/veto init`
+https://github.com/jigyasudham/veto
+```
+
+> Reddit tips: post the GIF natively if the sub allows it (huge engagement boost). Lead with
+> utility, not metrics. Reply to every comment in the first 2 hours. Read each sub's
+> self-promo rules first — some require a flair or a ratio of non-promo participation.
+
+---
+
+## 4. X/Twitter thread
+
+```
+1/ I shipped Veto — one MCP server that gives every major AI CLI a council of 49 specialist
+agents + 89 tools, using your existing subscription. No API keys. No extra token bill.
+
+Claude Code, Codex, Gemini, Cursor, Windsurf, Zed, JetBrains — same superpowers everywhere.
+[attach veto.gif]
+
+2/ The trick: the 42 worker agents are deterministic expert modules by default — real
+OWASP/CWE rules, AST secret detection, complexity metrics. They run offline at zero cost,
+and *optionally* upgrade to LLM reasoning via MCP Sampling on your existing plan.
+
+3/ The other 7 are a Council — Lead Dev, Architect, Security, Devil's Advocate, PM, UX, Legal
+— that debates a plan before you build it and hands you a GREEN/YELLOW/RED verdict with the
+actual trade-offs. It's saved me from a few bad calls already.
+
+4/ And it remembers. Save a session in Claude Code, restore it in Gemini CLI mid-task — the
+handoff carries full context. Plus a router that re-tunes itself every 20 outcomes.
+
+5/ MIT. On npm and the official MCP registry.
+
+One command: npx @jigyasudham/veto init
+
+⭐ https://github.com/jigyasudham/veto
+```
+
+> Tag the GIF on tweet 1 (video/gif tweets get far more reach). Quote-tweet it when you hit
+> milestones. Reply to "best MCP servers" threads with tweet 1.
+
+---
+
+## 5. Directory submission kit (paste into glama.ai / smithery.ai / mcp.so / pulsemcp / mcpservers.org)
+
+**Name:** Veto
+**Package:** `@jigyasudham/veto`  ·  **Registry name:** `io.github.jigyasudham/veto`
+**Repo:** https://github.com/jigyasudham/veto  ·  **License:** MIT  ·  **Transport:** stdio
+**Install:** `npx @jigyasudham/veto init`
+**Categories/tags:** mcp, agents, code-review, security, memory, council, router, ci-cd,
+self-learning, multi-agent, developer-tools
+
+**Short description (<=100 chars — matches server.json):**
+```
+89 agentic MCP tools, 49 specialist agents for every major AI CLI. Self-learning, zero API cost.
+```
+
+**One-liner:**
+```
+A council of 49 specialist agents + 89 tools for every AI CLI, using your existing subscription.
+```
+
+**Long description:**
+```
+Veto is a local MCP server that gives every major AI CLI — Claude Code, Codex, Gemini,
+Antigravity, Cursor, Windsurf, Zed, JetBrains — a shared layer of 89 agentic tools and 49
+specialist agents. 42 worker agents (across dev, security, memory, research, quality, and
+workflow domains) run as deterministic expert modules by default and optionally upgrade to LLM
+reasoning via MCP Sampling; a 7-agent Council debates trade-offs before you build. It adds code
+review, security and secrets scanning, CI gates, SDD agents, Playwright automation, a
+self-learning router that re-tunes its thresholds every 20 outcomes, and persistent memory that
+hands off your session across CLIs. On a subscription it costs nothing extra; on API billing,
+Sampling calls count and it warns you. MIT licensed.
+```

package/MCP-REGISTRY.md

@@ -0,0 +1,94 @@
+# Publishing Veto to the official MCP Registry
+
+This document is the runbook for listing Veto on the [official Model Context
+Protocol registry](https://registry.modelcontextprotocol.io) so it appears on
+official sources and in registry-backed directories. The registry entry is
+defined by [`server.json`](../server.json) at the repo root.
+
+## How the registry verifies ownership
+
+The registry does **not** host the package — it points at the npm package
+`@jigyasudham/veto`. To prove we own that package, the registry fetches
+`https://registry.npmjs.org/@jigyasudham/veto/<version>` and reads the
+top-level **`mcpName`** field from the published `package.json`. It must equal
+the `name` in `server.json`:
+
+```
+io.github.jigyasudham/veto
+```
+
+The `io.github.jigyasudham/*` namespace is owned by proving control of the
+GitHub account `jigyasudham` (interactive OAuth at publish time).
+
+> **Critical ordering:** the npm version referenced in `server.json` must
+> already be published **with** the `mcpName` field. The previously published
+> `2.1.1` did **not** have `mcpName`, which is why this listing ships as
+> `2.1.2` — the first npm release that carries it. Always `npm publish` first,
+> then `mcp-publisher publish`.
+
+## Files involved
+
+| File | Role |
+|---|---|
+| `server.json` | The registry entry (schema `2025-12-11`). Name, description (≤100 chars), repository, and the npm package + stdio transport. |
+| `package.json` | Carries `"mcpName": "io.github.jigyasudham/veto"` — the ownership proof read off npm. Keep its `version` equal to `server.json` `version` and `packages[0].version`. |
+
+Keep all three version fields in lockstep on every release:
+`package.json.version` == `server.json.version` == `server.json.packages[0].version`.
+
+## Publish steps
+
+Run from the repo root, on a clean `main` at the tagged release commit.
+
+1. **Publish the npm release that carries `mcpName`** (the user does this — it
+   needs npm credentials):
+
+   ```bash
+   npm run build
+   npm publish --access public        # publishes @jigyasudham/veto@2.1.2
+   ```
+
+   Verify the field landed on npm:
+
+   ```bash
+   curl -s https://registry.npmjs.org/@jigyasudham/veto/2.1.2 | grep -o '"mcpName":"[^"]*"'
+   # -> "mcpName":"io.github.jigyasudham/veto"
+   ```
+
+2. **Install the registry publisher CLI** (`mcp-publisher`). Either download a
+   release binary from
+   [`modelcontextprotocol/registry`](https://github.com/modelcontextprotocol/registry/releases)
+   or build from source (`make publisher` -> `./bin/mcp-publisher`).
+
+3. **Authenticate the namespace** with the GitHub account `jigyasudham`
+   (interactive — opens a browser):
+
+   ```bash
+   mcp-publisher login github
+   ```
+
+4. **Validate and publish** the entry (reads `server.json` from the cwd):
+
+   ```bash
+   mcp-publisher publish
+   ```
+
+   The registry re-runs npm ownership validation server-side; if step 1 was
+   skipped it fails with *"NPM package is missing required 'mcpName' field"*.
+
+5. **Confirm the listing:**
+
+   ```bash
+   curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=veto" | grep -o '"name":"io.github.jigyasudham/veto"'
+   ```
+
+## Updating the listing on future releases
+
+For each new release: bump `version` in `package.json` **and** both version
+fields in `server.json`, `npm publish`, then re-run `mcp-publisher publish`.
+The `mcpName` field never changes.
+
+## Lifecycle
+
+Use `mcp-publisher status` to move the server between `active`, `deprecated`,
+and `deleted` states if needed.