1. Conduid
  2. Developer Tools
  3. Desktop Pressets MCP
MCP server · Developer Tools

Desktop Pressets MCP

An experimental MCP Server written in GO. This follows current MCP sepcs version 2025-03-26. No SDL used.

Unclaimed last commit a year ago devtools
41Fair

Scored 6 months ago · breakdown

About Desktop Pressets MCP

Desktop Pressets MCP is an MCP server published by souravray in the Developer Tools category: an experimental MCP Server written in GO. This follows current MCP sepcs version 2025-03-26. No SDL used. It has been installed 0 times through Conduid.

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 (0) before depending on it in production.

Install

Install
npx desktop-pressets-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 Desktop Pressets MCP

Powered by Claude · Grounded in docs

I know everything about Desktop Pressets MCP. 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.
Questions

About Desktop Pressets MCP

How do I install Desktop Pressets MCP?

Run npx desktop-pressets-mcp, 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 Desktop Pressets MCP 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 Desktop Pressets MCP still maintained?

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