Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Nov 27, 2025

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
github.com/stacklok/toolhive v0.6.7v0.6.16 age confidence

Release Notes

stacklok/toolhive (github.com/stacklok/toolhive)

v0.6.16

Compare Source

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.6.15...v0.6.16

v0.6.15

Compare Source

What's Changed

Full Changelog: stacklok/toolhive@v0.6.14...v0.6.15

v0.6.14

Compare Source

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.6.13...v0.6.14

v0.6.13

Compare Source

What's Changed

Full Changelog: stacklok/toolhive@v0.6.12...v0.6.13

v0.6.12

Compare Source

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.6.11...v0.6.12

v0.6.11

Compare Source

Headline changes:

  • Include ping checks for remote workloads.
  • Allow build envs to include secrets from the secrets manager and environment variables on the host.

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.6.10...v0.6.11

v0.6.10

Compare Source

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.6.9...v0.6.10

v0.6.9

Compare Source

🚀 Toolhive v0.6.9 is live!

This release brings enhancements to MCP workflows, better registry customization, and improved developer experience across the board.

MCP & Workflows
• Smart transport auto-detection makes thv mcp commands easier to use
• Standard JSON Schema format now used for composite tool parameters
• Added RetryDelay to error handling in WorkflowStep CRD for more resilient workflows
• Extracted MCP client setup into reusable CreateInitializedMCPClient helper
• E2E tests now use mcp.LATEST_PROTOCOL_VERSION for better compatibility
• Removed token cache from vMCP for cleaner authentication flow

Registry & Deployment
• Registry server can now be configured with custom database connection details
• New podTemplateSpec field in MCPRegistry CRD lets you fully customize registry API deployments
MergePodTemplateSpecs utility added for cleaner pod template composition
• Updated registry from toolhive-registry release v2025.11.28

Tool Filtering & Configuration
• New ExcludeAll option provides more flexible tool filtering controls
• Better error handling throughout vMCP code (replaced utilruntime.Must with proper error checks)
• Minor fixes for retryDelay handling improve reliability

Testing & Quality
• Added vMCP E2E tests using yardstick MCP server
• Proposal naming validation now only checks new files, reducing false positives

Infrastructure
• Updated docker/metadata-action to v5.10.0

👋 Welcome to our newest contributors @​ignorant05 and @​4t8dd! 🥳

🔗 Full changelog: stacklok/toolhive@v0.6.8...v0.6.9

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.6.8...v0.6.9

v0.6.8

Compare Source

What's Changed


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Nov 27, 2025

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 2 additional dependencies were updated

Details:

Package Change
github.com/cedar-policy/cedar-go v1.3.0 -> v1.3.1
golang.org/x/exp/jsonrpc2 v0.0.0-20251113190631-e25ba8c21ef6 -> v0.0.0-20251125195548-87e1e737ad39

@github-actions
Copy link

github-actions bot commented Nov 27, 2025

🔒 MCP Security Scan Results

✅ adb-mysql-mcp-server

  • Status: Passed
  • Tools scanned: 3
  • Result: No security issues detected

✅ agentql-mcp

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ arxiv-mcp-server

  • Status: Passed
  • Tools scanned: 4
  • Result: No security issues detected

✅ astra-db-mcp

  • Status: Passed
  • Tools scanned: 16
  • Result: No security issues detected

✅ aws-diagram

  • Status: Passed
  • Tools scanned: 3
  • Result: No security issues detected

✅ aws-documentation

  • Status: Passed
  • Tools scanned: 3
  • Result: No security issues detected

✅ blender-mcp

  • Status: Passed
  • Tools scanned: 21
  • Result: No security issues detected

✅ brightdata-mcp

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ browserbase-mcp-server

  • Status: Passed
  • Tools scanned: 9
  • Result: No security issues detected

❌ chroma-mcp

  • Status: Failed
  • Tools scanned: 13
  • Vulnerabilities found: 1

Security issues detected:

Allowed issues (not blocking):

  • [TF002] Destructive toxic flow detected. The same agent has access to at least one tool that produces untrusted content and one tool that can behave destructively. For more information, see https://explorer.invariantlabs.ai/docs/mcp-scan/issue-code-reference/#TF002 (Allowed: ChromaDB is a vector database that requires both read and write operations for managing embeddings and collections)
  • [W004] The MCP server is not in our registry. (Allowed: Server not in Invariant Labs registry - we verify provenance independently via our own checks.)

✅ chrome-devtools-mcp

  • Status: Passed
  • Tools scanned: 26
  • Result: No security issues detected

✅ context7

  • Status: Passed
  • Tools scanned: 2
  • Result: No security issues detected

✅ graphlit-mcp-server

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ heroku-mcp-server

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ ida-pro-mcp

  • Status: Passed
  • Tools scanned: 48
  • Result: No security issues detected

✅ launchdarkly-mcp-server

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ magic-mcp

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ mcp-clickhouse

  • Status: Passed
  • Tools scanned: 3
  • Result: No security issues detected

✅ mcp-jetbrains

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ mcp-neo4j-aura-manager

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ mcp-neo4j-cypher

  • Status: Passed
  • Tools scanned: 3
  • Result: No security issues detected

✅ mcp-neo4j-memory

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ mcp-server-box

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ mcp-server-circleci

  • Status: Passed
  • Tools scanned: 16
  • Result: No security issues detected

✅ mcp-server-neon

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ netbird

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ notion

  • Status: Passed
  • Tools scanned: 21
  • Result: No security issues detected

✅ onchain-mcp

  • Status: Passed
  • Tools scanned: 10
  • Result: No security issues detected

✅ pagerduty-mcp

  • Status: Passed
  • Tools scanned: 38
  • Result: No security issues detected

✅ phoenix-mcp

  • Status: Passed
  • Tools scanned: 19
  • Result: No security issues detected

❌ playwright-mcp

  • Status: Failed
  • Tools scanned: 22
  • Vulnerabilities found: 2

Security issues detected:

  • [W005] The tool is not in our registry, even though the server is.
  • [W005] The tool is not in our registry, even though the server is.

Allowed issues (not blocking):

  • [TF001] Data leak toxic flow detected. The same agent has access to at least one tool that produces untrusted content, one tool that can access private data, and one tool that can behave as a public sink. For more information, see https://explorer.invariantlabs.ai/docs/mcp-scan/issue-code-reference/#TF001 (Allowed: Data leak risk acceptable - tool designed for browser automation and web testing workflows where external content interaction is essential. Users should be aware of potential data exposure when automating web interactions.)
  • [TF002] Destructive toxic flow detected. The same agent has access to at least one tool that produces untrusted content and one tool that can behave destructively. For more information, see https://explorer.invariantlabs.ai/docs/mcp-scan/issue-code-reference/#TF002 (Allowed: Destructive flow risk acceptable - browser automation tools are core functionality for web testing and automation. Users should only use with trusted prompts and on non-production systems.)

✅ sentry-mcp-server

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ supabase-mcp-server

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

✅ tavily-mcp

  • Status: Passed
  • Tools scanned: 0
  • Result: No security issues detected

Summary: Scanned 34 MCP server(s), found 3 security issue(s).

⚠️ Action Required: Security issues were detected. Please review and address them before merging.

@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from 3705bca to b9879bf Compare November 29, 2025 00:47
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.6.8 fix(deps): update module github.com/stacklok/toolhive to v0.6.9 Nov 29, 2025
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from b9879bf to 5804720 Compare December 2, 2025 18:04
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.6.9 fix(deps): update module github.com/stacklok/toolhive to v0.6.10 Dec 2, 2025
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch 2 times, most recently from 1842ce9 to bdf6cb3 Compare December 3, 2025 19:26
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.6.10 fix(deps): update module github.com/stacklok/toolhive to v0.6.11 Dec 3, 2025
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from bdf6cb3 to ab6abd3 Compare December 12, 2025 14:37
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.6.11 fix(deps): update module github.com/stacklok/toolhive to v0.6.12 Dec 12, 2025
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from ab6abd3 to 725e682 Compare December 15, 2025 16:59
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.6.12 fix(deps): update module github.com/stacklok/toolhive to v0.6.13 Dec 15, 2025
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from 725e682 to e70aa37 Compare December 17, 2025 13:25
JAORMX
JAORMX previously approved these changes Dec 17, 2025
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from e70aa37 to 39faf2a Compare December 17, 2025 17:40
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.6.13 fix(deps): update module github.com/stacklok/toolhive to v0.6.14 Dec 17, 2025
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from 39faf2a to b435665 Compare December 17, 2025 21:36
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.6.14 fix(deps): update module github.com/stacklok/toolhive to v0.6.15 Dec 17, 2025
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from b435665 to c84258b Compare January 5, 2026 10:51
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.6.15 fix(deps): update module github.com/stacklok/toolhive to v0.6.16 Jan 5, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Jan 5, 2026

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 64 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.25.3 -> 1.25.5
github.com/sigstore/sigstore-go v1.1.3 -> v1.1.4
github.com/cedar-policy/cedar-go v1.3.0 -> v1.3.1
github.com/go-openapi/analysis v0.23.0 -> v0.24.1
github.com/go-openapi/errors v0.22.2 -> v0.22.4
github.com/go-openapi/jsonpointer v0.21.1 -> v0.22.1
github.com/go-openapi/jsonreference v0.21.0 -> v0.21.3
github.com/go-openapi/loads v0.22.0 -> v0.23.2
github.com/go-openapi/runtime v0.28.0 -> v0.29.2
github.com/go-openapi/spec v0.21.0 -> v0.22.1
github.com/go-openapi/strfmt v0.23.0 -> v0.25.0
github.com/go-openapi/swag v0.24.1 -> v0.25.4
github.com/go-openapi/swag/cmdutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/conv v0.24.0 -> v0.25.4
github.com/go-openapi/swag/fileutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/jsonname v0.24.0 -> v0.25.4
github.com/go-openapi/swag/jsonutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/loading v0.24.0 -> v0.25.4
github.com/go-openapi/swag/mangling v0.24.0 -> v0.25.4
github.com/go-openapi/swag/netutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/stringutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/typeutils v0.24.0 -> v0.25.4
github.com/go-openapi/swag/yamlutils v0.24.0 -> v0.25.4
github.com/go-openapi/validate v0.24.0 -> v0.25.1
github.com/lestrrat-go/httprc/v3 v3.0.1 -> v3.0.3
github.com/mark3labs/mcp-go v0.43.1 -> v0.43.2
github.com/modelcontextprotocol/registry v1.3.10 -> v1.4.0
github.com/prometheus/common v0.66.1 -> v0.67.4
github.com/prometheus/otlptranslator v0.0.2 -> v1.0.0
github.com/prometheus/procfs v0.17.0 -> v0.19.2
github.com/sigstore/rekor v1.4.2 -> v1.4.3
github.com/sigstore/sigstore v1.9.6-0.20250729224751-181c5d3339b3 -> v1.10.0
github.com/theupdateframework/go-tuf/v2 v2.2.0 -> v2.3.0
github.com/transparency-dev/formats v0.0.0-20250825093915-4fde0c3c9ab1 -> v0.0.0-20251017110053-404c0d5b696c
go.mongodb.org/mongo-driver v1.17.4 -> v1.17.6
go.opentelemetry.io/otel v1.38.0 -> v1.39.0
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp v1.38.0 -> v1.39.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.38.0 -> v1.39.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.38.0 -> v1.39.0
go.opentelemetry.io/otel/exporters/prometheus v0.60.0 -> v0.61.0
go.opentelemetry.io/otel/metric v1.38.0 -> v1.39.0
go.opentelemetry.io/otel/sdk v1.38.0 -> v1.39.0
go.opentelemetry.io/otel/sdk/metric v1.38.0 -> v1.39.0
go.opentelemetry.io/otel/trace v1.38.0 -> v1.39.0
go.opentelemetry.io/proto/otlp v1.8.0 -> v1.9.0
go.yaml.in/yaml/v2 v2.4.2 -> v2.4.3
golang.ngrok.com/ngrok/v2 v2.1.0 -> v2.1.1
golang.org/x/crypto v0.45.0 -> v0.46.0
golang.org/x/exp/event v0.0.0-20251023183803-a4bb9ffd2546 -> v0.0.0-20251125195548-87e1e737ad39
golang.org/x/exp/jsonrpc2 v0.0.0-20251113190631-e25ba8c21ef6 -> v0.0.0-20251219203646-944ab1f22d93
golang.org/x/mod v0.30.0 -> v0.31.0
golang.org/x/net v0.47.0 -> v0.48.0
golang.org/x/oauth2 v0.33.0 -> v0.34.0
golang.org/x/sync v0.18.0 -> v0.19.0
golang.org/x/sys v0.38.0 -> v0.39.0
golang.org/x/term v0.37.0 -> v0.38.0
golang.org/x/text v0.31.0 -> v0.32.0
google.golang.org/genproto/googleapis/api v0.0.0-20250929231259-57b25ae835d4 -> v0.0.0-20251202230838-ff82c1b0f217
gopkg.in/evanphx/json-patch.v4 v4.12.0 -> v4.13.0
k8s.io/api v0.34.2 -> v0.35.0
k8s.io/apimachinery v0.34.2 -> v0.35.0
k8s.io/client-go v0.34.2 -> v0.35.0
k8s.io/kube-openapi v0.0.0-20250710124328-f3f2b991d03b -> v0.0.0-20250910181357-589584f1c912
k8s.io/utils v0.0.0-20251002143259-bc988d571ff4 -> v0.0.0-20251222233032-718f0e51e6d2
sigs.k8s.io/json v0.0.0-20241014173422-cfa47c3a1cc8 -> v0.0.0-20250730193827-2d320260d730

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants