Dysnomia Ecosystem Navigator — MCP Server
Dysnomia Ecosystem Navigator — MCP Server
An MCP (Model Context Protocol) server that gives AI assistants direct access to the Dysnomia/Atropa blockchain ecosystem on PulseChain. Ask Claude about contract state, debug transactions, trace minters, and map the entire ecosystem graph — all from natural language.
Tools
Tool | Description |
| List all registered contracts with categories and descriptions |
| Read on-chain state — balances, supply, ownership, minting status |
| Trace a minter address across all ecosystem contracts |
| Look up QING territory data — ownership, metadata |
| Simulate contract calls to surface reverts before spending gas |
| Map ownership and dependency graph between contracts |
| Query on-chain event logs filtered by contract, event, block range |
Related MCP server: SEI MCP Server V2
Setup
# Install dependencies
npm install
# Build
npm run buildConfiguration
1. Add Contract Addresses
Edit src/config.ts and fill in the deployed addresses:
META: { address: "0x...", category: "core", description: "Root coordination contract" },
RING: { address: "0x...", category: "core", description: "Ring structure / orbital mechanics" },
// etc.Rebuild after changes: npm run build
2. Custom RPC
Set the PULSECHAIN_RPC environment variable to override the default RPC:
export PULSECHAIN_RPC="https://your-rpc-endpoint.com"3. Extend ABIs
Each tool file in src/tools/ has its own ABI definitions. Add function signatures as contracts evolve — the pattern is human-readable ABI strings:
const MY_ABI = [
"function MyNewFunction(uint256) view returns (address)",
];Connect to Claude Desktop
Add this to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on Mac):
{
"mcpServers": {
"dysnomia": {
"command": "node",
"args": ["/absolute/path/to/dysnomia-navigator/build/index.js"],
"env": {
"PULSECHAIN_RPC": "https://rpc.pulsechain.com"
}
}
}
}Connect to Claude Code
claude mcp add dysnomia node /absolute/path/to/dysnomia-navigator/build/index.jsTest with MCP Inspector
npm run inspectorArchitecture
src/
├── index.ts # Entry point — creates server, registers tools
├── config.ts # RPC config, contract registry, ABIs, helpers
└── tools/
├── listEcosystem.ts # list_ecosystem
├── getContractState.ts # get_contract_state
├── traceMinter.ts # trace_minter
├── queryQing.ts # query_qing
├── debugCall.ts # debug_call
├── mapRelationships.ts # map_relationships
└── searchEvents.ts # search_eventsExtending
To add a new tool:
Create
src/tools/myNewTool.tsExport a
registerMyNewTool(server: McpServer)functionImport and call it in
src/index.tsRebuild:
npm run build
The server uses stdio transport so it works with any MCP-compatible client.
Phases (for context)
Terra: Forming data on minters — physics actions per-QING build minter token data
Firma: Personal GWATs establishing territory
Life: IoT hardware + YUE extensions creating real-world activity sandboxes
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tehironclad/Dysnomia-Ecosystem-Navigator-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server