A
licenseA
qualityC
maintenanceEnables LLMs to compile and verify Tolk smart contract code for the TON blockchain.
2
1
MIT
cellc-mcp
by toastmanAu
Related Servers
Alternatives to cellc-mcp
No user-submitted related servers found.
Related Servers
- -licenseNot gradedqualityBmaintenanceEnables AI agents to safely run Pact 5 REPL tests, scan modules for critical language traps, estimate gas, generate contracts, and invoke formal verification via a standalone prover plugin.-
- AlicenseNot gradedqualityDmaintenanceBridges LLMs to the Ceedling C unit testing framework, enabling test execution, module-specific testing, and scaffolding of source/test file triplets.MIT
- AlicenseAqualityCmaintenanceEnables AI agents to build, check, cost, and deploy HotPocket dApps on Evernode/Xahau by scaffolding deterministic contracts, checking determinism, estimating lease costs, ranking hosts, and generating deploy commands.1247 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to generate, compile, and fix Rust projects from natural language descriptions using LLMs and the Rust compiler.99-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to analyse local source trees, generate starter projects for multiple targets without overwriting files, and verify generated manifests and entry files. It also exposes source and runtime inspection tools so agents can gather evidence about software artifacts within bounded, honest checks.2MIT
TDQS
B3.4/5.0
Scored across 7 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: type-checking (cellc_check), verifier obligations (cellc_constraints), error explanation (cellc_explain), examples (cellc_get_example, cellc_list_examples), language reference (cellc_language_reference), and metadata (cellc_metadata). No overlap in functionality.
Naming Consistency3/5
All tools start with 'cellc_' prefix, but the naming pattern is inconsistent: some use verbs (cellc_check, cellc_explain, cellc_get_example, cellc_list_examples) while others are nouns (cellc_constraints, cellc_language_reference, cellc_metadata). This mixed convention reduces predictability.
Tool Count5/5
With 7 tools covering essential aspects of CellScript contract development (checking, constraints, error help, examples, language reference, metadata), the count is well-scoped and appropriate for the domain.
Completeness4/5
The tool set covers key workflows: type-checking, error resolution, language reference, and example retrieval. Minor gaps exist (e.g., no tool to fetch a specific example by name or compile a contract), but the core development cycle is supported.
Maintenance
ActivityInactive
ResponsivenessNo recent community issues