1. Conduid
  2. Blockchain
  3. Smart Intent Router
MCP server · Blockchain

Smart Intent Router

by · github.com/vika4433/smart-intent-router

Smart intent router solution built on the Model Context Protocol (MCP). Features intent classification, multilingual support, dynamic LLM selection, and LM Studio integration, with both a web client and a modular server.

Unclaimed last commit a year ago blockchain
InstallView source
34Low

Scored a month ago · breakdown

About Smart Intent Router

Smart Intent Router is an MCP server published by vika4433 in the Blockchain category: smart intent router solution built on the Model Context Protocol (MCP). Features intent classification, multilingual support, dynamic LLM selection, and LM Studio integration, with both a web client and a modular server.

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

Install

From source
git clone https://github.com/vika4433/smart-intent-router

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 Smart Intent Router

Powered by Claude · Grounded in docs

I know everything about Smart Intent Router. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Questions

About Smart Intent Router

How do I install Smart Intent Router?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Smart Intent Router safe to use with an AI agent?

Its trust score is 34 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Smart Intent Router still maintained?

The last commit was a year ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.