Verfy

MCP servers / @pulumi/mcp-server

MCP tool changes

@pulumi/mcp-server

2 of its last 5 updates changed what the agent reads: 1 tool description rewritten, up to 0.2.0.

npm package · last recorded on 13 November 2026 on a clean machine with placeholder settings; only tools/list was sent. A changed description is not a vulnerability. npm page · Method and limits · this data as JSON.

Release by release

0.1.12 → 0.2.0

minor release, 26 September 2025

No tool definition changed.

0.1.11 → 0.1.12

patch release, 25 September 2025

No tool definition changed.

0.1.10 → 0.1.11

patch release, 25 September 2025

No tool definition changed.

0.1.9 → 0.1.10

patch release, 22 September 2025
pulumi-resource-search: description and input schema changed; arguments removed: size
Before (0.1.9)
Search and analyze Pulumi-managed cloud resources using Lucene-style queries. This tool can discover, count, and analyze your deployed infrastructure across all cloud providers. Query Syntax Examples: - All S3 buckets: type:aws:s3:Bucket - Untagged resources: -properties.tags:* - Untagged S3 buckets: type:aws:s3:Bucket AND -properties.tags:* - Resources in production stack: stack:production - AWS Lambda functions: package:aws type:lambda:Function - Resources by project: project:my-app Supports field filters, boolean operators (AND, OR, NOT), exact matches with quotes, and property searches. The top parameter controls the maximum number of results to return (defaults to 20).
After (0.1.10)
Search and analyze Pulumi-managed cloud resources using a strict subset of Lucene query syntax. QUERY SYNTAX RULES: - The search query syntax is a strict subset of Lucene query syntax - The documents being searched are Pulumi resources - The implicit operator is AND - Parentheses and OR are supported between fields but not within fields - All resources are returned by default (use empty query "" to get all) - Wildcard queries are NOT supported (no * allowed) - Fuzzy queries are NOT supported - Boosting is NOT supported - Field grouping is NOT supported - Whitespace is NOT supported - field:value produces a match_phrase query - field:"value" produces a term query - -field:value produces a bool must_not match_phrase query - -field:"value" produces a bool must_not term query - field: produces an existence query - Resource properties can be queried with leading dot: .property.path:value or .property.path: (existence) - You absolutely must not produce queries that use fields other than: type, name, id, stack, project, package, modified, provider, provider_urn, team and protected, unless the field is the name of a property. - You absolutely must not produce queries that use wildcards (e.g., *). - You absolutely must not produce queries that use field grouping (e.g., type:(a OR b)) AVAILABLE FIELDS: - type: Pulumi types used for pulumi import operations (e.g., aws:s3/bucket:Bucket) - name: logical Pulumi resource names - id: physical Pulumi resource names - stack: name of the stack the resource belongs to - project: name of the project the resource belongs to - created: when the resource was first created (absolute dates only) - modified: when the resource was last modified (absolute dates only) - package: package of the resource (e.g., aws, gcp) - provider: alias for the "package" field - provider_urn: full URN of the resource's provider - protected: boolean representing whether a resource is protected - team: name of a team with access to the resource IMPORTANT QUERY PATTERNS: For AWS resources, do not use specific provider prefixes (aws: or aws-native:) in type filters. Instead: WRONG: type:aws:s3/bucket:Bucket WRONG: type:aws-native:s3:Bucket CORRECT: type:"Bucket" (searches across both aws and aws-native providers) For package filtering, use the generic package name: CORRECT: package:aws (matches both aws and aws-native packages) For finding resources by service, prefer the module field when possible: PREFERRED: module:s3 (finds all S3 resources regardless of provider) For property existence queries, always use the dot notation: CORRECT: .tags: (checks if tags property exists) For property negation queries (finding resources WITHOUT a property): CORRECT: -.tags: or NOT .tags: (finds resources without tags) COMMON TRANSLATIONS: - "untagged resources" → -.tags: or NOT .tags: - "resources without tags" → -.tags: or NOT .tags: Supports field filters, boolean operators (AND, OR, NOT), exact matches with quotes, and property searches. The top parameter controls the maximum number of results to return (defaults to 20). Resources may not have a repository url. This means that there is no available information about the repository that the resource is associated with.

0.1.8 → 0.1.9

patch release, 16 September 2025

Added: neo-task-launcher

Releases tried: 0.1.8 (2025-09-16); 0.1.9 (2025-09-16); 0.1.10 (2025-09-22); 0.1.11 (2025-09-25); 0.1.12 (2025-09-25); 0.2.0 (2025-09-26).

Tools in 0.2.0

The pin is the SHA-256 of the tool's name, description and input schema, as verfy.lock records it. The same pin in your lock means your agent reads this exact definition. Verfy 0.16.0 and later also pin a tool's title, annotations and output schema when the server sends them, so such a tool shows a different pin in your lock.

Tools in 0.2.0
ToolDescriptionPin
pulumi-registry-get-typeGet the JSON schema for a specific JSON schema type reference62d809f2d2ef
pulumi-registry-get-resourceReturns information about a Pulumi Registry resource200715c4d2f6
pulumi-registry-get-functionReturns information about a Pulumi Registry functione2e6a6e25be9
pulumi-registry-list-resourcesList all resource types for a given provider and module304fd7ab13e6
pulumi-registry-list-functionsList all function types for a given provider and module43f9ea0ffaf1
pulumi-cli-previewRun pulumi preview for a given project and stack2c882de4fe61
pulumi-cli-upRun pulumi up for a given project and stacke756359ac473
pulumi-cli-stack-outputGet the output value(s) of a given stackeab65a2affe2
pulumi-cli-refreshRun pulumi refresh for a given project and stack738269d0dcc3
deploy-to-awsDeploy application code to AWS by generating Pulumi infrastructure. This tool automatically analyzes your application files and provisions the appropriate AWS resources (S3, Lambda, EC2, etc.) based on what it finds. No prior analysis needed - just invoke directly.651fe5fe4302
pulumi-resource-searchSearch and analyze Pulumi-managed cloud resources using a strict subset of Lucene query syntax. QUERY SYNTAX RULES: - The search query syntax is a strict subset of Lucene query syntax - The documents being searched are Pulumi resources - The implicit operator is AND - Parentheses and OR are supported between fields but not within fields - All resources are returned by default (use empty query "" to get all) - Wildcard queries are NOT supported (no * allowed) - Fuzzy queries are NOT supported - Boosting is NOT supported - Field grouping is NOT supported - Whitespace is NOT supported - field:value produces a match_phrase query - field:"value" produces a term query - -field:value produces a bool must_not match_phrase query - -field:"value" produces a bool must_not term query - field: produces an existence query - Resource properties can be queried with leading dot: .property.path:value or .property.path: (existence) - You absolutely must not produce queries that use fields other than: type, name, id, stack, project, package, modified, provider, provider_urn, team and protected, unless the field is the name of a property. - You absolutely must not produce queries that use wildcards (e.g., *). - You absolutely must not produce queries that use field grouping (e.g., type:(a OR b)) AVAILABLE FIELDS: - type: Pulumi types used for pulumi import operations (e.g., aws:s3/bucket:Bucket) - name: logical Pulumi resource names - id: physical Pulumi resource names - stack: name of the stack the resource belongs to - project: name of the project the resource belongs to - created: when the resource was first created (absolute dates only) - modified: when the resource was last modified (absolute dates only) - package: package of the resource (e.g., aws, gcp) - provider: alias for the "package" field - provider_urn: full URN of the resource's provider - protected: boolean representing whether a resource is protected - team: name of a team with access to the resource IMPORTANT QUERY PATTERNS: For AWS resources, do not use specific provider prefixes (aws: or aws-native:) in type filters. Instead: WRONG: type:aws:s3/bucket:Bucket WRONG: type:aws-native:s3:Bucket CORRECT: type:"Bucket" (searches across both aws and aws-native providers) For package filtering, use the generic package name: CORRECT: package:aws (matches both aws and aws-native packages) For finding resources by service, prefer the module field when possible: PREFERRED: module:s3 (finds all S3 resources regardless of provider) For property existence queries, always use the dot notation: CORRECT: .tags: (checks if tags property exists) For property negation queries (finding resources WITHOUT a property): CORRECT: -.tags: or NOT .tags: (finds resources without tags) COMMON TRANSLATIONS: - "untagged resources" → -.tags: or NOT .tags: - "resources without tags" → -.tags: or NOT .tags: Supports field filters, boolean operators (AND, OR, NOT), exact matches with quotes, and property searches. The top parameter controls the maximum number of results to return (defaults to 20). Resources may not have a repository url. This means that there is no available information about the repository that the resource is associated with.7ea6628425b5
neo-task-launcherLaunch a Neo task when user asks Neo to perform a task. Pulumi Neo is a purpose-built cloud infrastructure automation agent.19a982084355
prompt:deploy-to-awsDeploy application code to AWS by generating Pulumi infrastructure38cf333f59b2
prompt:convert-terraform-to-typescriptConverts a Terraform file to TypeScript11518445a0ee

Lock these tools

Pin what @pulumi/mcp-server serves you today, commit the lock, and a pull request fails when a tool changes, with the text before and after. Pin the package version in your MCP config as well.

$ pip install verfy
$ verfy lock check --update   # shows each tool, then writes verfy.lock
$ git add verfy.lock
# .github/workflows/verfy.yml, after actions/checkout
- uses: verfy-dev/verfy-action@v1

Maintain this server? Run the same check on your releases and add the Locked by Verfy badge to your README.