Smart Pacts MCP Servers
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Smart Pacts MCP Serversdeploy my Pact module to devnet"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Smart Pacts MCP Servers
Model Context Protocol servers for Smart Pacts blockchain tooling.
This monorepo provides secure, audited MCP servers for Kadena Community Edition (KDA-CE) blockchain interactions, following ADR-MCP-001 security baseline.
Architecture Overview
Security-first design: All servers implement audit logging, input sanitization, and capability restrictions
Kadena-native: Built specifically for Pact 5 smart contracts on KDA-CE 20-chain architecture
Multi-agent integration: Designed for Smart Pacts 11-agent enterprise workspace
Browser MCP
Two external MCP servers provide visual testing capabilities:
Server | Purpose | Agent Usage |
Playwright | Browser automation, screenshots, accessibility testing | WebDev (UI verification), Tester (visual testing), Security (accessibility audit) |
Chrome DevTools | Live DOM/CSS inspection, network analysis, console logs | All agents for diagnosing visual test failures |
Security
Allowed origins: Restricted to local dev servers (
localhost:3000-4321) and devnet (localhost:8081-8083)Isolated sessions: Clean browser profile per session, no persistent data
Output containment: Screenshots and traces saved to
/coordination/artifacts/playwright-mcp/
Example Usage
# Take accessibility snapshot
"Navigate to http://localhost:3000 and capture an accessibility tree snapshot"
# Visual regression test
"Screenshot the login form at http://localhost:3000/login and highlight interactive elements"
# DevTools inspection
"Connect to Chrome and inspect the network requests when submitting the form"Packages
Package | Purpose | Status |
Common security baseline and utilities | ✅ | |
Pact smart contract interactions | 🚧 Phase 1.2 | |
Chainweb API and transaction monitoring | 🚧 Phase 1.2 | |
Module deployment and devnet management | 🚧 Phase 1.3 | |
Security scanning and audit tooling | 🚧 Phase 1.3 |
Quick Start
# Install dependencies
pnpm install
# Build all packages
pnpm build
# Run tests
pnpm test
# Security audit
pnpm auditSecurity
All servers implement ADR-MCP-001 security baseline
Audit logs at
~/.smartpacts/mcp-audit.log.YYYY-MM-DDInput sanitization prevents prompt injection
Network/filesystem access controlled via allowlists
Tool schema drift detection via
tools.lock.json
See SECURITY.md for threat model and baseline checklist.
Development
Node.js: >=20.11.0
Package manager: pnpm >=9
TypeScript: Strict mode with composite references
Testing: Vitest with ≥90% function coverage requirement
Architecture Documents
ADR-MCP-001 - MCP Architecture & Security Baseline
License
MIT
Related MCP Connectors
Hosted MCP server for live Bittensor chain reads and self-custodial on-chain writes.
Self-hosted MCP server: 26 deterministic dev, security, and EVM tools.
A paid remote MCP for ZeroID, built to return verdicts, receipts, usage logs, and audit-ready JSON.
A paid remote MCP for hosted MCP server, built to return verdicts, receipts, usage logs, and audit-r