1. Conduid
  2. Developer Tools
  3. Pelican MCP
MCP server · Developer Tools

Pelican MCP

A MCP server for https://pelican.dev/ built with https://bun.com/

Unclaimed last commit 7 months ago devtools
34Low

Scored a month ago · breakdown

About Pelican MCP

Pelican MCP is an MCP server published by AJXD2 in the Developer Tools category: a MCP server for https://pelican.dev/ built with https://bun.com/.

The repository has 2 stars and 2 forks, with the last commit 7 months 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/AJXD2/pelican-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.

Tools (7)

get_resource_usageCPU, memory, disk, network stats

Parameters not published.

get_serverGet server details

Parameters not published.

kill_serverForce-kill a server

Parameters not published.

list_serversList all accessible servers

Parameters not published.

restart_serverRestart a server

Parameters not published.

start_serverStart a server

Parameters not published.

stop_serverGracefully stop a server

Parameters not published.

Ask AI

✦

Ask AI about Pelican MCP

Powered by Claude · Grounded in docs

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

Security checks

6 checks have not been run yet.

Questions

About Pelican MCP

How do I install Pelican MCP?

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

Is Pelican MCP 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 Pelican MCP still maintained?

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