1. Conduid
  2. Developer Tools
  3. Nacos Istio
MCP server · Developer Tools

Nacos Istio

Nacos integrate with Istio as a MCP server

Unclaimed last commit 6 years ago devtools
41Fair

Scored 4 months ago · breakdown

About Nacos Istio

Nacos Istio is an MCP server published by nkorange in the Developer Tools category: nacos integrate with Istio as a MCP server. It has been installed 0 times through Conduid.

The repository has 2 stars and 0 forks, with the last commit 6 years ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues (0) before depending on it in production.

Install

Install
npx nacos-istio

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

Ask AI about Nacos Istio

Powered by Claude · Grounded in docs

I know everything about Nacos Istio. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ·README presentNot checked yet.
  • ·License declaredNot checked yet.
  • ·Tests presentNot checked yet.
  • ·Dependencies pinnedNot checked yet.
  • ·No dynamic code executionNot checked yet.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

nacos-istio

Nacos integrate with Istio as a MCP server

This project has been moved to https://github.com/nacos-group/nacos-istio

README mirrored from the source repository 4 months ago. The original is authoritative.

Questions

About Nacos Istio

How do I install Nacos Istio?

Run npx nacos-istio, then add the server to your MCP client's configuration. Conduid has recorded 0 installs, so the command is known to work with current clients.

Is Nacos Istio safe to use with an AI agent?

Its trust score is 41 out of 100 (fair). It passes 0 of 1 static security checks; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Nacos Istio still maintained?

The last commit was 6 years ago, with 0 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.