Chainweb API runs on your own machine — the client starts it, so there is no endpoint to ping. 75 installs a week from npm. Last commit 4 Oct 2026.
Chainweb HTTP API: local sim, pre-signed send, poll, table reads, SPV proofs, module deploys.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
: path.join(workspaceRoot, candidate);
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add chainweb -e 'PACT_COMMUNITY_WORKSPACE_ROOT=<PACT_COMMUNITY_WORKSPACE_ROOT>' -e 'PACT_COMMUNITY_CHAINWEB_MODE=<PACT_COMMUNITY_CHAINWEB_MODE>' -- npx -y @pact-community/mcp-chainweb
{
"mcpServers": {
"chainweb": {
"command": "npx",
"args": [
"-y",
"@pact-community/mcp-chainweb"
],
"env": {
"PACT_COMMUNITY_CHAINWEB_MODE": "<PACT_COMMUNITY_CHAINWEB_MODE>",
"PACT_COMMUNITY_WORKSPACE_ROOT": "<PACT_COMMUNITY_WORKSPACE_ROOT>"
}
}
}
}
[mcp_servers.chainweb]
command = "npx"
args = ["-y", "@pact-community/mcp-chainweb"]
env = { PACT_COMMUNITY_WORKSPACE_ROOT = "<PACT_COMMUNITY_WORKSPACE_ROOT>", PACT_COMMUNITY_CHAINWEB_MODE = "<PACT_COMMUNITY_CHAINWEB_MODE>" }
{
"mcpServers": {
"chainweb": {
"command": "npx",
"args": [
"-y",
"@pact-community/mcp-chainweb"
],
"env": {
"PACT_COMMUNITY_CHAINWEB_MODE": "<PACT_COMMUNITY_CHAINWEB_MODE>",
"PACT_COMMUNITY_WORKSPACE_ROOT": "<PACT_COMMUNITY_WORKSPACE_ROOT>"
}
}
}
}
{
"servers": {
"chainweb": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pact-community/mcp-chainweb"
],
"env": {
"PACT_COMMUNITY_CHAINWEB_MODE": "<PACT_COMMUNITY_CHAINWEB_MODE>",
"PACT_COMMUNITY_WORKSPACE_ROOT": "<PACT_COMMUNITY_WORKSPACE_ROOT>"
}
}
}
}
Put your own values in place of
<PACT_COMMUNITY_WORKSPACE_ROOT> (Workspace root directory; all file access is confined inside it), <PACT_COMMUNITY_CHAINWEB_MODE> (Network mode; must be set and match PACT_COMMUNITY_CHAINWEB_PROFILE (devnet, testnet06, or mainnet)).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
PACT_COMMUNITY_CHAINWEB_PROFILE (Network profile: devnet (default, read/write), testnet06, or mainnet (both read-only)), PACT_COMMUNITY_CHAINWEB_BASE_URL (Chainweb node base URL (default per profile)), PACT_COMMUNITY_CHAINWEB_NETWORK_ID (Network id, e.g. development, testnet06, mainnet01 (default per profile)).
Sealed render-proof for deployed websites — signed verdicts bound to the deployed artifact.
Read your Edgible applications, devices, deploy status and logs, signed in as you.
Search 600+ Docker/Portainer app templates and prepare a local deploy plan.
Checks TypeORM migrations for data loss, table locks, and deploy problems before they run.
Deploy your project to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
Local MCP tools for secret status and guarded deployment. Values never reach the agent.
Complete Vercel MCP: deploys, logs, projects, env, domains, DNS, certs via the full REST API
Deploy a local folder, git repo, or Docker image to a live HTTPS URL from your AI chat.
Answers built from our own checks of this server.