1. Conduid
  2. AI
  3. MCP
MCP server · AI

MCP

An IoC-based universal application framework.

47Fair

Scored 3 days ago · breakdown

About MCP

MCP is an MCP server published by lakutata in the AI category: an IoC-based universal application framework.

The repository has 77 stars and 13 forks, with the last commit 3 days ago. Recent commit activity is the strongest signal that reported issues will get attention.

Install

Claude Code
claude mcp add mcp-413b -- npx -y @lakutata/mcp
npx
npx -y @lakutata/mcp

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 MCP

Powered by Claude · Grounded in docs

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

Security checks

Static checks derived from the repository 3 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • ✓Tests presentA test suite exists in the repository.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.

1 check has not been run yet.

Releases

2.0.1212.0.121
2.0.1192.0.119
2.0.1182.0.118
2.0.1172.0.117
2.0.1152.0.115

README

Lakutata

An IoC application framework for Node.js and TypeScript

Website · Getting started · Examples · API reference · 中文

npm node license

Lakutata gives web services, command line tools, desktop (Electron) applications and embedded devices one programming model. An application is a tree of objects (components, providers, controllers) that a container creates; DTOs validate the options of the objects and the input of the actions; and transports expose the controllers over HTTP (Express, Fastify), the command line (Commander), service calls (HTTP, Socket.IO, JSON-RPC 2.0, gRPC, NATS, Electron IPC), MCP, D-Bus, schedules and message queues. One controller method can serve several of them at once.

Quick start

npx @lakutata/cli create --name my-app
cd my-app
npm run dev
# in another terminal
curl 'http://localhost:8080/example?name=you'     # {"message":"Hello, you!"}

Lakutata needs Node.js ^22.13.0 || >=24.11.0. The templates of lakutata create give you a web service, a command line tool, an HTTP API with a React, Vue, Next.js or Nuxt interface, or an Electron application. An application written by hand looks like this:

import {Application, DTO} from 'lakutata'
import {buildEntrypoints, Controller} from 'lakutata/com/entrypoint'
import {GET, ServiceAction} from 'lakutata/decorator/ctrl'
import {Expect} from 'lakutata/decorator/dto'
import {expressHTTPEntrypoint} from 'lakutata/adapter/express'

class GreetDTO extends DTO {
    @Expect(DTO.String().optional().default('world'))
    public name: string
}

class GreetController extends Controller {
    //GET /greet?name=you, and the service action {cmd: 'greet', name: 'you'}
    @GET('/greet', GreetDTO)
    @ServiceAction({cmd: 'greet'}, GreetDTO)
    public async greet(input: GreetDTO): Promise<{ message: string }> {
        return {message: `Hello, ${input.name}!`}
    }
}

Application.run(() => ({
    id: 'com.example.greeter',
    name: 'Greeter',
    components: {
        entrypoint: buildEntrypoints({
            controllers: [GreetController],
            http: expressHTTPEntrypoint({port: 8080})
        })
    },
    bootstrap: ['entrypoint']
}))

Packages

lakutata is the framework: it re-exports most of the packages below under its subpaths (lakutata/com/database, lakutata/adapter/express…), so an application usually installs it alone, plus the drivers and adapters it uses.

Package What it provides In lakutata
lakutata The framework, with the log and entrypoint components preset
@lakutata/core Applications, objects, dependency injection, DTO validation yes
@lakutata/entrypoint Controllers and their transports: HTTP, command line, service calls, schedules yes
@lakutata/logger The logger (JSON lines compatible with pino) yes
@lakutata/utils Time and helper functions yes
@lakutata/orm Databases on TypeORM, an embedded MongoDB, migrations yes
@lakutata/cache A cache over memory, files, Redis, Memcache, MongoDB, SQLite, PostgreSQL or MySQL yes
@lakutata/mutex Locks shared between processes and instances yes
@lakutata/queue Message queues over memory, Redis, NATS, RabbitMQ or Kafka yes
@lakutata/i18n Messages in several languages (ICU MessageFormat) yes
@lakutata/security Password hashing, signatures, encryption yes
@lakutata/monitor CPU, memory, event loop and HTTP request monitors yes
@lakutata/docker Docker images, containers and networks yes
@lakutata/containerd containerd without Docker, for embedded Linux devices yes
@lakutata/nats NATS messaging and service calls over NATS no
@lakutata/grpc A gRPC client and server, and service calls over gRPC no
@lakutata/dbus D-Bus services and clients no
@lakutata/mcp The tools, resources and prompts of the Model Context Protocol no
@lakutata/cli The lakutata command: projects, workspaces, migrations, packaging no
@lakutata/builder Bundles, executables and installers, used by lakutata package no

The templates of lakutata create are the @lakutata/template-* packages, listed by @lakutata/templates.

Documentation

  • lakutata.com: the guides and the examples, in English and Chinese, and the API reference. Their sources are packages/lakutata/doc (en, zh, and their examples) and the type declarations of the packages.
  • Each package has a README with its options, API and errors.
  • plugins/lakutata: the Agent Skill of the framework, for AI coding assistants. Any assistant: npx skills add lakutata/lakutata; Claude Code: /plugin install lakutata --marketplace lakutata/lakutata; the others, and how the skill works: its page.

Development

npm install
npm run build        # compiles every package, in the order of their dependencies
npm run test:unit    # the unit tests of the packages
npm run lint         # ESLint, and the check of the documentation of the public API

cd website && npm ci && npm run dev    # the website, once the packages are built

The repository holds the packages and the templates (packages/), the website (website/) and the build and documentation-check scripts (scripts/). CONTRIBUTING.md gives the naming rules and how the public API is documented.

Lakutata 2.x

Lakutata 3 brought the framework and its packages into this repository. The 2.x releases of lakutata are tagged here (2.0.x). The 2.x versions of @lakutata/cli, @lakutata/dbus and @lakutata/nats come from lakutata-packages, and the 2.x templates from the lakutata-template-* repositories. To bring a 2.x project to 3.x, see Upgrading from Lakutata 2.x; a project on Lakutata 1.x (@lakutata/core 1.x and the @lakutata-module/* and @lakutata-component/* packages) follows Upgrading from Lakutata 1.x instead.

License

MIT

README fetched from the repository 3 days ago. The original is authoritative.

Questions

About MCP

How do I install MCP?

Run claude mcp add mcp-413b -- npx -y @lakutata/mcp, then add the server to your MCP client's configuration.

Is MCP safe to use with an AI agent?

Its trust score is 47 out of 100 (fair). It passes 5 of the 5 static security checks run so far. It has no ConduID identity yet, so agent calls to it are not receipted.

Is MCP still maintained?

Yes — the last commit was 3 days ago. The repository has 77 stars and 13 forks.