1. Conduid
  2. AI
  3. Model Context Protocol Server 53493
MCP server · AI

Model Context Protocol Server 53493

MCP server: Model Context Protocol Server 53493

Unclaimed last commit 8 months ago ai
44Fair

Scored 5 months ago · breakdown

About Model Context Protocol Server 53493

Model Context Protocol Server 53493 is an MCP server published by Kishore6753 in the AI category: mCP server: Model Context Protocol Server 53493.

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/Kishore6753/model-context-protocol-server-53493

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 Model Context Protocol Server 53493

Powered by Claude · Grounded in docs

I know everything about Model Context Protocol Server 53493. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

  • ✓README presentThe repository ships documentation.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

4 checks have not been run yet.

README

Project Repository

This is the initial README file for the project.

README copy captured when this server was indexed; it may lag the repository. The original is authoritative.

Questions

About Model Context Protocol Server 53493

How do I install Model Context Protocol Server 53493?

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

Is Model Context Protocol Server 53493 safe to use with an AI agent?

Its trust score is 44 out of 100 (fair). It passes 1 of the 2 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Model Context Protocol Server 53493 still maintained?

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