1. Conduid
  2. Developer Tools
  3. Mon Magma MCP
MCP server · Developer Tools

Mon Magma MCP

mcp tools to stake and unstake on magmastaking.xyz on monad network

Unclaimed last commit a year ago devtools
41Fair

Scored 5 months ago · breakdown

About Mon Magma MCP

Mon Magma MCP is an MCP server published by intellygentle in the Developer Tools category: mcp tools to stake and unstake on magmastaking.xyz on monad network.

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/intellygentle/mon-magma-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 Mon Magma MCP

Powered by Claude · Grounded in docs

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

Security checks

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

  • ✓README presentThe repository ships documentation.
  • !License declaredNo license file. Legally you have no right to use it in a product.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • ✓No dynamic code executionSource scan found no eval, dynamic Function, or shell execution.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

Summary of Commands

Here’s a recap of the prerequisite commands to set up your MCP project:

git clone https://github.com/intellygentle/mon-magma-mcp.git
cd mon-magma-mcp

Install dependencies

npm i --save-dev @types/node
npm isntall
npm install @modelcontextprotocol/sdk zod viem
npm install dotenv

Run configure dotenv

go to dist folder

cd dist
  • create an env file in your dist folder

    code .env # fill it with PRIVATE_KEY=0xYourPrivateKey
    
  • get the env directory

    pwd # add /env to the output to make your env path
    
  • edit the monad-magma-Tools.ts in the src folder with the path to your env. this is so that claude can load it

go back to the root directory

cd ..

Build Again

npm run build

run the script

node dist/monad-magma-Tools.js

Output will look like this

configure claude json file

  • copy the output of which node
which node  # it should look like this /home/yourUsername/.nvm/versions/node/v23.11.0/bin/node
  • copy the path to your js file
  • combine the two to make your claude json setup
  • { "mcpServers": {
      "monad-mcp": {
        "command": "wsl",
        "args": [
           "/home/yourUsername/.nvm/versions/node/v23.11.0/bin/node",
          "/home/yourUsername/monadMpcTask/dist/monad-magma-Tools.js"
        ]
      }
    

Install MCP inspector

npm install @modelcontextprotocol/inspector@0.10.2

Test with MCP Inspector

be sure to edit "username" use your directory

npx @modelcontextprotocol/inspector /home/username/.nvm/versions/node/v23.11.0/bin/node /home/username/monadMpcTask/dist/monad-magma-Tools.js
  • output will look like this

MCP Inspector will look like this

Claude will look like this

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

Questions

About Mon Magma MCP

How do I install Mon Magma MCP?

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

Is Mon Magma MCP safe to use with an AI agent?

Its trust score is 41 out of 100 (fair). It passes 3 of the 6 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 Mon Magma MCP 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.