@modootoday/pmcp 0.13.0 → 0.14.0

package/plugins/yeoman-environment-7/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "yeoman-environment-7",
+  "version": "7.0.0",
+  "description": "Use yeoman-environment's ESM environment API when working against the v7.0.0 source shape. Note that ^7.0.0 is not a published version according to the researched npm metadata; verify the installed version before relying on this skill.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/yeoman-environment-7/skills/yeoman-environment/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: yeoman-environment
+description: Use yeoman-environment's ESM environment API when working against the v7.0.0 source shape. Note that ^7.0.0 is not a published version according to the researched npm metadata; verify the installed version before relying on this skill.
+---
+
+Verified against yeoman-environment@7.0.0 on 2026-09-08. 3 of 3 examples executed.
+
+# yeoman-environment
+
+## Version reality
+
+The requested range is `^7.0.0`, but the researched npm versions list `6.3.0` as the current published version. No v7 release or v7 changelog was found. Do not assume that `^7.0.0` can be installed from npm, and do not describe this as a verified published v7 API. The API notes below follow the v7.0.0 source snapshot supplied for this task.
+
+The source snapshot is an ESM package. Use named imports or the default `Environment` export; do not copy the older CommonJS examples blindly.
+
+## Core environment
+
+Create an environment with `createEnv(options?)`:
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import { createEnv } from 'yeoman-environment';
+
+const env = createEnv({ skipInstall: true });
+
+assert.equal(typeof env.lookup, 'function');
+assert.equal(typeof env.create, 'function');
+assert.equal(typeof env.run, 'function');
+assert.equal(typeof env.runGenerator, 'function');
+assert.equal(typeof env.register, 'function');
+assert.equal(typeof env.registerStub, 'function');
+```
+
+`Environment.run(arguments?, options?)` accepts either a command string or an argument array. The documented workflow first awaits `env.lookup()` to search the current working directory for installed generators, then awaits `env.run(...)`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import { createEnv } from 'yeoman-environment';
+
+const env = createEnv({ skipInstall: true });
+const result = await env.lookup();
+
+// Lookup completes without requiring a generator to be selected.
+assert.ok(result === undefined || typeof result === 'object');
+```
+
+The environment also exposes `create`, `runGenerator`, `register`, and `registerStub` for programmatic generator lifecycle work. The supplied research identifies these methods but does not specify their complete argument and return-value contracts, so do not invent those contracts from older documentation.
+
+## Generator lookup
+
+`lookupGenerator(namespace, options?)` is a named export. By default it returns one string; with `{singleResult: false}` it returns an array of strings. With `{packagePath: true}`, the lookup can return the generator package path rather than a generator namespace match.
+
+Lookup depends on installed generators and the process environment, so a deterministic standalone assertion should only check the documented result shape for a lookup that actually resolves in the target installation:
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import { lookupGenerator } from 'yeoman-environment';
+
+const matches = lookupGenerator('yeoman-environment', { singleResult: false });
+assert.ok(Array.isArray(matches));
+for (const match of matches) assert.equal(typeof match, 'string');
+```
+
+Do not confuse `lookupGenerator` with `env.lookup()`: the former is the exported generator-resolution helper, while the latter performs environment lookup before a run.
+
+## Registering and running
+
+The current README shape uses ESM and async calls:
+
+```ts
+import { createEnv } from 'yeoman-environment';
+
+const env = createEnv({ skipInstall: true });
+await env.lookup();
+await env.run('angular', { skipInstall: true });
+```
+
+An environment can register a generator with a namespace and resolved location, then run an argument array:
+
+```ts
+import { createEnv } from 'yeoman-environment';
+
+const env = createEnv({ skipInstall: true });
+env.register(generator, { namespace: 'example:app', resolved });
+await env.run(['example:app', 'arg'], { help: true });
+```
+
+The names `generator` and `resolved` above must be supplied by the caller. The research does not define a standalone generator implementation or a complete stub-generator contract, so do not turn this snippet into a supposedly runnable generator test without consulting the installed package's types/source.
+
+## Command preparation
+
+`prepareCommand(options)` prepares a Commander command. `prepareGeneratorCommand(options)` registers a generator and runs it through the environment. The documented preparation shape includes `resolved` and `namespace`:
+
+```ts
+import { prepareCommand } from 'yeoman-environment';
+
+const command = await prepareCommand({
+  resolved: '/path/to/generator',
+  namespace: 'example:app',
+});
+await command.parseAsync(process.argv);
+```
+
+These functions are command/CLI integration APIs. They are not appropriate for a direct `bun example.ts` example unless the caller supplies a real generator path and command-line setup.
+
+## Package-manager installation task
+
+`packageManagerInstallTask(options)` returns `Promise<boolean>`. Its options include `memFs`, `packageJsonLocation`, `adapter`, and `skipInstall`; supported package managers are npm, Yarn, pnpm, and Bun.
+
+```ts
+import { packageManagerInstallTask } from 'yeoman-environment';
+
+const installed = await packageManagerInstallTask({
+  memFs,
+  packageJsonLocation: process.cwd(),
+  adapter,
+  skipInstall: false,
+});
+```
+
+This task requires caller-provided `memFs` and adapter objects and can invoke a package manager. It is therefore not a valid isolated example under the execution constraints for this skill; use it from the Yeoman environment that supplies those dependencies.
+
+## Common mistakes
+
+- Do not use `require('yeoman-environment')` for the researched source shape; it is ESM.
+- Do not assume `^7.0.0` is installable: the researched npm metadata reports `6.3.0` as the latest published version.
+- Do not copy the older v2-style `const yeoman = require(...)` example as the current API.
+- Do not call `describe`, `it`, or `expect` in a direct script. Yeoman environment is not a test runner.
+- Do not expect `TerminalAdapter` or `EnvironmentCommand.execute()` to be standalone helpers. They provide CLI interaction and Commander-based command execution.
+- Do not claim that a successful `env.lookup()` means a generator was run; lookup and run are separate operations.
+- Pass `skipInstall: true` when demonstrating lifecycle behavior that should not install dependencies.
+- Await `lookup`, `run`, command parsing, and package-manager tasks.
+
+## Not covered
+
+This skill does not establish a published v7 release, a v7 migration path, complete generator or stub-generator argument contracts, the exact return values of all `Environment` methods, a standalone `TerminalAdapter` setup, or a runnable package-manager installation example. It also does not cover generator implementation APIs, filesystem/mem-fs construction, Commander configuration beyond the preparation surface described above, or behavior that requires a real installed generator or Yeoman CLI environment.

package/plugins/z-schema-12/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "z-schema-12",
+  "version": "12.0.0",
+  "description": "Use z-schema ^12.0.0 for JSON Schema validation with synchronous and asynchronous APIs, safe results, draft-aware schemas, custom formats, and registered remote references.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/z-schema-12/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/plugins/z-schema-12/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/z-schema-12/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "z-schema-12", "version": "12.0.0" }

package/plugins/z-schema-12/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "z-schema-12",
+  "version": "12.0.0",
+  "description": "Use z-schema ^12.0.0 for JSON Schema validation with synchronous and asynchronous APIs, safe results, draft-aware schemas, custom formats, and registered remote references.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/z-schema-12/skills/z-schema/SKILL.md

@@ -0,0 +1,179 @@
+---
+name: z-schema
+description: Use z-schema ^12.0.0 for JSON Schema validation with synchronous and asynchronous APIs, safe results, draft-aware schemas, custom formats, and registered remote references.
+---
+
+Verified against z-schema@12.4.5 on 2026-09-08. 7 of 7 examples executed.
+
+# z-schema ^12.0.0
+
+## Runtime and defaults
+
+- z-schema v12 requires Node.js 22 or later.
+- Use `ZSchema.create()` rather than constructing `ZSchema` directly. Older examples may still show `new ZSchema(...)`.
+- The default JSON Schema dialect is `draft2020-12`. Draft-2019-09, draft-07, draft-06, and draft-04 are also supported.
+- Existing draft-04, draft-06, and draft-07 schemas must either declare `$schema` or use a matching factory option such as `{ version: 'draft-07' }`.
+- In draft-2019-09 and draft-2020-12, `format` is annotation-only by default. `{ formatAssertions: null }` restores legacy assertion behavior; `{ formatAssertions: true }` enables vocabulary-aware assertions.
+
+## Synchronous validation
+
+The default validator throws when validation fails. A successful call returns `true`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import ZSchema from 'z-schema';
+
+const validator = ZSchema.create();
+const schema = {
+  type: 'object',
+  properties: { answer: { type: 'number' } },
+  required: ['answer'],
+  additionalProperties: false,
+};
+
+assert.equal(validator.validate({ answer: 42 }, schema), true);
+
+try {
+  validator.validate({ answer: 'wrong' }, schema);
+  assert.fail('validation should throw');
+} catch (error) {
+  assert.equal((error as Error).name, 'ValidateError');
+  assert.ok(Array.isArray((error as { details: unknown[] }).details));
+}
+```
+
+Do not expect the old boolean-plus-`getLastErrors()` behavior. The removed public methods include `getLastError()`, `getLastErrors()`, `isValid()`, `compileSchema()`, `getMissingReferences()`, `getMissingRemoteReferences()`, and `getResolvedSchema()`.
+
+## Safe validation
+
+Use `{ safe: true }` when failure should be returned rather than thrown. The result is `{ valid: true }` or `{ valid: false, err }`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import ZSchema from 'z-schema';
+
+const validator = ZSchema.create({ safe: true });
+const schema = { type: 'string' };
+
+const good = validator.validate('ok', schema);
+assert.deepEqual(good, { valid: true });
+
+const bad = validator.validate(123, schema);
+assert.equal(bad.valid, false);
+if (bad.valid) throw new Error('expected invalid result');
+assert.ok(Array.isArray(bad.err.details));
+```
+
+`validateSafe()` and `validateSchemaSafe()` are also available. `validateSchema()` and `validateSchemaSafe()` validate schema documents themselves rather than instance data.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import ZSchema from 'z-schema';
+
+const validator = ZSchema.create();
+const schema = { type: 'object', required: ['name'] };
+
+assert.equal(validator.validateSchema(schema), true);
+const result = validator.validateSchemaSafe({ type: 17 });
+assert.equal(result.valid, false);
+```
+
+## Draft-version migration
+
+Version 12 changed the default from draft-07 to draft-2020-12. Select an older draft explicitly when using its schema vocabulary:
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import ZSchema from 'z-schema';
+
+const validator = ZSchema.create({ version: 'draft-07' });
+const schema = {
+  $schema: 'http://json-schema.org/draft-07/schema#',
+  type: 'array',
+  items: [{ type: 'string' }],
+  additionalItems: false,
+};
+
+assert.equal(validator.validate(['value'], schema), true);
+```
+
+When migrating schemas to draft-2020-12, the vocabulary shapes differ:
+
+- `id` becomes `$id`.
+- `definitions` becomes `$defs`.
+- Tuple `items: [...]` becomes `prefixItems`.
+- `additionalItems` becomes `items` alongside `prefixItems`.
+- `dependencies` becomes either `dependentSchemas` or `dependentRequired`.
+
+Version 12 also supports `unevaluatedProperties`, `unevaluatedItems`, `$dynamicRef`, and `$dynamicAnchor`.
+
+## Asynchronous validation
+
+Create the validator with `{ async: true }`. Its validation methods return promises. With `{ async: true, safe: true }`, the promise resolves to a safe result rather than rejecting for validation failure.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import ZSchema from 'z-schema';
+
+const validator = ZSchema.create({ async: true });
+assert.equal(await validator.validate('ok', { type: 'string' }), true);
+
+const safe = ZSchema.create({ async: true, safe: true });
+const result = await safe.validate(123, { type: 'string' });
+assert.equal(result.valid, false);
+```
+
+The explicit methods are `validateAsync()` and `validateAsyncSafe()`. Async format validators require the async factory option; do not call an async validator through a synchronous validator.
+
+## Custom formats
+
+Formats can be registered on a validator. The package also exports format-management helpers, including `registerFormat`, `unregisterFormat`, `getRegisteredFormats`, `getSupportedFormats`, `getFormatValidators`, and `isFormatSupported`.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import ZSchema from 'z-schema';
+
+const validator = ZSchema.create({ formatAssertions: true });
+validator.registerFormat('uppercase', (value: unknown): boolean =>
+  typeof value === 'string' && value === value.toUpperCase(),
+);
+
+const schema = { type: 'string', format: 'uppercase' };
+assert.equal(validator.validate('YES', schema), true);
+```
+
+For draft-2019-09 and draft-2020-12, registering a format does not by itself make `format` an assertion under the default settings. Configure `formatAssertions` when format failures must invalidate data. The format-management functions are also available as package exports.
+
+## Remote references
+
+Register a remote schema before validating a `$ref` that points to it. In v12, `setRemoteReference()` is a static API; older examples that call it on an instance are outdated.
+
+```ts pmcp-example
+import assert from 'node:assert/strict';
+import ZSchema from 'z-schema';
+
+ZSchema.setRemoteReference('https://example.test/person.json', {
+  $id: 'https://example.test/person.json',
+  type: 'object',
+  required: ['name'],
+  properties: { name: { type: 'string' } },
+});
+
+const validator = ZSchema.create();
+const schema = { $ref: 'https://example.test/person.json' };
+assert.equal(validator.validate({ name: 'Ada' }, schema), true);
+```
+
+A schema reader can be installed with `ZSchema.setSchemaReader(...)` and inspected with `ZSchema.getSchemaReader()`. A reader is responsible for resolving the URI; remote references otherwise need registration before validation.
+
+## Recursion
+
+The default recursion limit is 100. Deep recursive validation can produce `MAX_RECURSION_DEPTH_EXCEEDED`; increase it with `{ maxRecursionDepth: 500 }` when the schema and data require a deeper limit.
+
+## What this skill does not cover
+
+- The command-line executable and its file-oriented invocation.
+- Browser use of the published UMD bundle.
+- Detailed error-code and error-parameter catalogs.
+- Building a filesystem-backed `SchemaReader`.
+- The complete TypeScript type surface beyond the public APIs described here.

package/plugins/zod-schema-validation-3/.claude-plugin/plugin.json

@@ -0,0 +1,9 @@
+{
+  "name": "zod-schema-validation-3",
+  "version": "3.0.0",
+  "description": "Parse at the boundary, read the failure, and let the schema be the type.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}

package/plugins/zod-schema-validation-3/LICENSE

@@ -0,0 +1,93 @@
+Elastic License 2.0
+
+URL: https://www.elastic.co/licensing/elastic-license
+
+## Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+## Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide,
+non-sublicensable, non-transferable license to use, copy, distribute, make
+available, and prepare derivative works of the software, in each case subject to
+the limitations and conditions below.
+
+## Limitations
+
+You may not provide the software to third parties as a hosted or managed
+service, where the service provides users with access to any substantial set of
+the features or functionality of the software.
+
+You may not move, change, disable, or circumvent the license key functionality
+in the software, and you may not remove or obscure any functionality in the
+software that is protected by the license key.
+
+You may not alter, remove, or obscure any licensing, copyright, or other notices
+of the licensor in the software. Any use of the licensor’s trademarks is subject
+to applicable law.
+
+## Patents
+
+The licensor grants you a license, under any patent claims the licensor can
+license, or becomes able to license, to make, have made, use, sell, offer for
+sale, import and have imported the software, in each case subject to the
+limitations and conditions in this license. This license does not cover any
+patent claims that you cause to be infringed by modifications or additions to
+the software. If you or your company make any written claim that the software
+infringes or contributes to infringement of any patent, your patent license for
+the software granted under these terms ends immediately. If your company makes
+such a claim, your patent license ends immediately for work on behalf of your
+company.
+
+## Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you
+also gets a copy of these terms.
+
+If you modify the software, you must include in any modified copies of the
+software prominent notices stating that you have modified the software.
+
+## No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in
+these terms.
+
+## Termination
+
+If you use the software in violation of these terms, such use is not licensed,
+and your licenses will automatically terminate. If the licensor provides you
+with a notice of your violation, and you cease all violation of this license no
+later than 30 days after you receive that notice, your licenses will be
+reinstated retroactively. However, if you violate these terms after such
+reinstatement, any additional violation of these terms will cause your licenses
+to terminate automatically and permanently.
+
+## No Liability
+
+*As far as the law allows, the software comes as is, without any warranty or
+condition, and the licensor will not be liable to you for any damages arising
+out of these terms or the use or nature of the software, under any kind of
+legal claim.*
+
+## Definitions
+
+The **licensor** is the entity offering these terms, and the **software** is the
+software the licensor makes available under these terms, including any portion
+of it.
+
+**you** refers to the individual or entity agreeing to these terms.
+
+**your company** is any legal entity, sole proprietorship, or other kind of
+organization that you work for, plus all organizations that have control over,
+are under the control of, or are under common control with that
+organization. **control** means ownership of substantially all the assets of an
+entity, or the power to direct its management and policies by vote, contract, or
+otherwise. Control can be direct or indirect.
+
+**your licenses** are all the licenses granted to you for the software under
+these terms.
+
+**use** means anything you do with the software requiring one of your licenses.
+
+**trademark** means trademarks, service marks, and similar rights.

package/plugins/zod-schema-validation-3/NOTICE

@@ -0,0 +1,51 @@
+pmcp
+
+Copyright (c) 2026 modootoday. All rights reserved.
+
+Licensor: modootoday
+Licensed under the Elastic License 2.0; see LICENSE.
+
+The licensor is modootoday, the company, not any individual contributor. This
+file names the licensor because the Elastic License 2.0 defines that term rather
+than carrying a copyright line of its own; LICENSE is kept unmodified.
+
+What the licence permits, in short, without replacing the terms in LICENSE:
+
+  - Using this software inside your own company, on any scale.
+  - Embedding it in a product you sell, and modifying or forking it.
+  - Redistributing it, with these notices intact.
+  - Running it locally as an MCP server, which is what it is for. A host
+    process spawning it on your own machine is use, not a hosted service.
+
+What it does not permit:
+
+  - Offering this software to third parties as a hosted or managed service.
+    A remotely hosted MCP endpoint serving other people is the case this
+    forbids.
+  - Circumventing licence key functionality.
+  - Removing or obscuring these notices.
+
+The Elastic License 2.0 is source-available, not an OSI-approved open source
+licence. It grants a patent licence and ends that licence if you assert a patent
+claim against the software; see the Patents section of LICENSE.
+
+LICENSE governs. Where this summary and LICENSE differ, LICENSE is what applies.
+
+---
+
+This software depends on the following packages, which are distributed under
+their own terms and are not covered by the licence above.
+
+  @modelcontextprotocol/server   MIT   Copyright (c) Anthropic, PBC
+  @modelcontextprotocol/core     MIT   Copyright (c) Anthropic, PBC
+  zod                            MIT   Copyright (c) Colin McDonnell
+  semver                         ISC   See the dependency's LICENSE file.
+  smol-toml              BSD-3-Clause   Copyright (c) Squirrel Chat et al.
+  yaml                           ISC   Copyright Eemeli Aro
+
+Full licence texts and copyright notices ship with those packages. Their
+respective licence terms govern distribution of those dependencies.
+
+@huggingface/transformers is an optional peer dependency. It is never
+distributed with this package; a user who wants semantic ranking installs it
+themselves, under its own Apache-2.0 terms.

package/plugins/zod-schema-validation-3/gemini-extension.json

@@ -0,0 +1 @@
+{ "name": "zod-schema-validation-3", "version": "3.0.0" }

package/plugins/zod-schema-validation-3/plugin.json

@@ -0,0 +1,10 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "zod-schema-validation-3",
+  "version": "3.0.0",
+  "description": "Parse at the boundary, read the failure, and let the schema be the type.",
+  "author": { "name": "modootoday" },
+  "license": "Elastic-2.0",
+  "repository": "https://github.com/modootoday/pmcp",
+  "homepage": "https://pmcp.build/skills/"
+}