DeXe DAO governance
NPM · DEXE-MCP
DeXe Protocol DAOs for AI agents: create DAOs, proposals, votes, OTC token sales, on-chain reads.
Available components
Last scanned (10 hours ago)
Scores higher than 85% of npm servers
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 110 of 303 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to edward-arinin-web-dev/dexe-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 11171 tokens (~219/item across 51 items; 48 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (46% of tools); any adoption earns full credit.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 2 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "dexe_vote_build_withdraw" implies "withdraw" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 50 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +31
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 50 functional
- First check of Tool coverage: 46 functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 0
- Package version: 0.37.0 → 0.37.1 functional
- 12 Oct 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Analysed npm/dexe-mcp@0.37.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | edward-arinin-web-dev/dexe-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/edward-arinin-web-dev/dexe-mcp/.github/workflows/release.yml@refs/tags/v0.37.1 |
| Rekor log index | 3244642919 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a1ed3126bb7cae215da06342a443a1c1fcdceaa9db9e918887447d7d911afe5c5c40c6a10f377e9dc8382ef219d64ad443abfb6064da5c8babe4b29a0 |
Background: How many MCP packages publish verified provenance →
Dependencies 303 packages
| Packages resolved | 303 |
|---|---|
| Stale | 110 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dexe_vote_user_power User staking + delegation power across VoteTypes ~127
Read-only. Reads `tokenBalance` and `nftBalance` on GovUserKeeper for every VoteType (Personal/Micropool/Delegated/Treasury) in one multicall. tokenBalance includes the un-deposited wallet balance; deposited power = tokenBalance - tokenOwned.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | – | Chain to read from: 56 mainnet, 97 testnet. Needs an RPC for it. Default: the configured chain. |
| govPool | string | yes | GovPool contract address |
| user | string | yes | User wallet address |
| Name | Type | Req | Description |
|---|---|---|---|
| govPool | string | yes | – |
| power | object | yes | – |
| user | string | yes | – |
| userKeeper | string | yes | – |
No examples provided.
dexe_wc_connect Connect a wallet by QR ~95
Writes to a remote service. Starts a WalletConnect session and renders a scannable QR (ASCII + PNG). RECOMMENDED signer — the phone signs and broadcasts, so no private key touches this machine. Poll dexe_wc_status until `connected`. A hot DEXE_PRIVATE_KEY keeps signing precedence.
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | – | Chain to request in the session namespace. Defaults to the MCP's default chain. |
No output schema declared.
No examples provided.
dexe_wc_disconnect Disconnect the wallet ~44
Writes to a remote service. Tears down the active WalletConnect session; safe when not connected.
| Name | Type | Req | Description |
|---|---|---|---|
| _placeholder | boolean | – | Unused; tool takes no input. |
No output schema declared.
No examples provided.
dexe_wc_status WalletConnect session state ~65
Read-only. WalletConnect config plus live session state (connected?, account, chain, topic, peer wallet, last error). It dispatches transactions in DEXE_SIGNER_MODE=walletconnect (the default).
| Name | Type | Req | Description |
|---|---|---|---|
| chainId | integer | – | Unused; reserved. |
No output schema declared.
No examples provided.
dexe_write_context Signer and write posture ~151
Read-only. Write posture for this session — the signer mode + address (WalletConnect, keystore, hot key or none), the agent KEYRING (signerKey, address, gas, 24h broadcasts per persona), Pinata / WalletConnect / Safe readiness, the signer's deposited power in the newest recorded DAO, and a write journey a prior session left unfinished. Chains, env readiness and recorded DAOs are dexe_context.
| Name | Type | Req | Description |
|---|---|---|---|
| includeAgentBalances | boolean | – | Probe each persona's native balance (one eth_getBalance per signer, default chain). |
| includeDepositedPower | boolean | – | Read the signer's deposited power in the newest recorded DAO (one extra RPC call). |
No output schema declared.
No examples provided.
How do I install the DeXe DAO governance MCP server?
DeXe DAO governance runs locally as an npm package, launched with npx -y dexe-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dexe-mcp
claude mcp add edward-arinin-web-dev-dexe-mcp -- npx -y dexe-mcp
What is the DeXe DAO governance MCP server?
DeXe DAO governance is an MCP server listed in the public MCP registry as io.github.edward-arinin-web-dev/dexe-mcp. DeXe Protocol DAOs for AI agents: create DAOs, proposals, votes, OTC token sales, on-chain reads. This page covers its npm package (dexe-mcp).
Is the DeXe DAO governance MCP server safe to use?
DeXe DAO governance scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DeXe DAO governance MCP server expose?
DeXe DAO governance exposes 48 tools: dexe_dao_predict_addresses, dexe_dao_registry_lookup, dexe_dao_info, dexe_proposal_state, dexe_proposal_list, and 43 more. Their descriptions and schemas cost roughly 10,524 tokens of context every time the server is loaded.
Is the DeXe DAO governance MCP server still maintained?
DeXe DAO governance is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the DeXe DAO governance MCP server under?
DeXe DAO governance declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.