1. Conduid
  2. Automation
  3. SEVER
MCP server · Automation

SEVER

by · github.com/orlando2019/MCP-SEVER

Desarrollo de un servidor MCP (“Model Context Protocol”) full-stack, capaz de buscar, copiar y pegar archivos en directorios, gestionar peticiones de clientes y exponer su funcionalidad tanto en TypeScript (Node.js) como en Python (FastAPI), para su integración con n8n, AppSheet y npm.

Unclaimed last commit a year ago automation
InstallView source
34Low

Scored yesterday · breakdown

About SEVER

SEVER is an MCP server published by orlando2019 in the Automation category: desarrollo de un servidor MCP (“Model Context Protocol”) full-stack, capaz de buscar, copiar y pegar archivos en directorios, gestionar peticiones de clientes y exponer su funcionalidad tanto en TypeScript (Node.js) como en Python (FastAPI), para su integración con n8n, AppSheet y npm.

The repository has 1 stars and 0 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/orlando2019/MCP-SEVER

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 SEVER

Powered by Claude · Grounded in docs

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

Security checks

6 checks have not been run yet.

Questions

About SEVER

How do I install SEVER?

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

Is SEVER 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 SEVER 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.