# dev.workers.dolerite.base-onchain-tools/base-onchain-tools (remote · base-onchain-tools.dolerite.workers.dev)

Base mainnet analysis: contract audits, transfer simulation, token pricing. Paid via x402.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `base-onchain-tools.dolerite.workers.dev`: 72/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-dolerite-base-onchain-tools-base-onchain-tools/base-onchain-tools.md), [page](https://verifymcp.io/servers/dev-workers-dolerite-base-onchain-tools-base-onchain-tools/base-onchain-tools)

## Channel facts

- Endpoint: `https://base-onchain-tools.dolerite.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 12 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1451 tokens (~120/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "base_simulate_transfer" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the dev.workers.dolerite.base-onchain-tools/base-onchain-tools MCP server?

dev.workers.dolerite.base-onchain-tools/base-onchain-tools is a hosted endpoint at https://base-onchain-tools.dolerite.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-workers-dolerite-base-onchain-tools-base-onc 'https://base-onchain-tools.dolerite.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-dolerite-base-onchain-tools-base-onc": {
      "url": "https://base-onchain-tools.dolerite.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-dolerite-base-onchain-tools-base-onc": {
      "type": "http",
      "url": "https://base-onchain-tools.dolerite.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-dolerite-base-onchain-tools-base-onc]
url = "https://base-onchain-tools.dolerite.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-dolerite-base-onchain-tools-base-onc": {
      "type": "remote",
      "url": "https://base-onchain-tools.dolerite.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-dolerite-base-onchain-tools-base-onc --url 'https://base-onchain-tools.dolerite.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-dolerite-base-onchain-tools-base-onc:
    url: "https://base-onchain-tools.dolerite.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-dolerite-base-onchain-tools-base-onc": {
      "Transport": "http",
      "Url": "https://base-onchain-tools.dolerite.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-dolerite-base-onchain-tools-base-onc -t streamable-http -u 'https://base-onchain-tools.dolerite.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-dolerite-base-onchain-tools-base-onc": {
      "type": "http",
      "url": "https://base-onchain-tools.dolerite.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 72, +1)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (12)

### `base_demo` (~51 tokens)

Free. Returns a complete, live contract audit of Base USDC — the same output shape as the paid audit tool, with the address fixed. Call this first to see what the paid tools return before spending anything.

### `base_address_check` (~102 tokens)

Pre-flight check on a Base mainnet address before you pay it: contract vs EOA, ETH and USDC balances, outbound tx count, and warnings about whether funds sent there can actually be moved. Costs $0.002 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

Input parameters:

- `address` (string, required): Base mainnet address (0x-prefixed, 20 bytes)

### `base_tx_check` (~97 tokens)

Confirm a Base mainnet transaction: success or reverted, block, confirmations and finality, gas used, and every ERC-20 transfer it moved with USDC amounts decoded. Costs $0.002 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

Input parameters:

- `hash` (string, required): Base mainnet transaction hash (0x-prefixed, 32 bytes)

### `base_token` (~81 tokens)

ERC-20 token metadata on Base mainnet: name, symbol, decimals and total supply, read straight from the contract. Costs $0.001 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

Input parameters:

- `address` (string, required): ERC-20 contract address on Base mainnet

### `base_gas` (~79 tokens)

Live Base mainnet gas oracle: current gas price, base fee, recent base fee trend, priority fee percentiles, and the estimated cost of a plain ERC-20 transfer in ETH. Costs $0.001 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

### `base_price` (~80 tokens)

ETH/USD and BTC/USD read live from Chainlink's on-chain price feeds on Base, with the feed's own description, decimals, update timestamp, age in seconds and a staleness flag. Costs $0.001 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

### `base_contract_type` (~106 tokens)

Identify what a Base contract actually is: ERC-20, ERC-721 or ERC-1155 via ERC-165, plus proxy detection across EIP-1967, EIP-1822 and the legacy ZeppelinOS slot with the current implementation address. Costs $0.002 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

Input parameters:

- `address` (string, required): Contract address on Base mainnet

### `base_allowance` (~124 tokens)

ERC-20 allowance on Base: how much a spender may pull from an owner, whether it is an unlimited approval, the owner balance, and how much is actually spendable right now. Defaults to USDC. Costs $0.001 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

Input parameters:

- `owner` (string, required): Token holder address
- `spender` (string, required): Address allowed to spend
- `token` (string): Optional ERC-20 contract, defaults to USDC on Base

### `base_token_price` (~137 tokens)

USD price for ANY token on Base, not just the two assets Chainlink covers. Discovers every Uniswap V3 pool against WETH and USDC across all four fee tiers, reads sqrtPriceX96 and does the Q96 fixed-point maths, prices off the deepest pool, ignores deployed-but-never-traded pools, and cross-checks the remaining ones to flag thin or manipulated liquidity. Costs $0.006 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

Input parameters:

- `address` (string, required): ERC-20 token address on Base mainnet

### `base_simulate_transfer` (~201 tokens)

Will this token payment actually go through, and if not exactly why. Simulates the transfer without spending gas, decodes the real revert reason (Error(string), Panic codes translated to English, or a custom error selector), and separately reports balance and allowance blockers. Understands that a caller with no ETH is fine for gasless EIP-3009 or a sponsored relayer. Costs $0.008 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

Input parameters:

- `amount` (string, required): Amount in atomic units (for USDC, 1000000 = $1)
- `from` (string, required): Address the tokens leave
- `spender` (string): Optional: simulate transferFrom pulled by this spender instead of a direct transfer
- `to` (string, required): Recipient address
- `token` (string): Optional ERC-20 contract, defaults to USDC on Base

### `base_contract_audit` (~247 tokens)

What an UNVERIFIED Base contract can actually do — the case where block explorers show you nothing. Disassembles the deployed bytecode with a PUSH-aware opcode walk (a naive byte scan reports SELFDESTRUCT on contracts that cannot self-destruct), strips the Solidity metadata trailer, recovers the function selectors from the dispatch table and names them against a keccak-derived signature database, then reports admin powers (mint, blacklist, freeze, pause, trading switches, adjustable fees, upgrade hooks), dangerous opcodes (DELEGATECALL, SELFDESTRUCT, CALLCODE, CREATE2), which token standards it really implements, and whether it supports EIP-3009 so it can be paid gaslessly over x402 at all. Proxies are detected and followed, because a forwarder's own bytecode tells you nothing. Costs $0.04 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

Input parameters:

- `address` (string, required): Contract address on Base mainnet
- `follow_proxy` (string): Optional, default true. Set to false to audit the proxy's own bytecode instead of its implementation.

### `base_portfolio` (~91 tokens)

ETH and USDC balances for up to 20 Base addresses in a single call, with per-address funded flags and totals. One request instead of forty RPC round trips. Costs $0.003 per call, paid in USDC over x402 on Base. Calling this tool returns the payment requirements; failed calls are never billed.

Input parameters:

- `addresses` (string, required): Comma-separated Base addresses, max 20

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-dolerite-base-onchain-tools-base-onchain-tools/base-onchain-tools#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 71
- 2026-09-18: 71
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 66
- 2026-09-07: 66
- 2026-09-06: 65
- 2026-09-05: 65
- 2026-09-04: 64
- 2026-09-03: 64
- 2026-09-02: 63
- 2026-09-01: 63
- 2026-08-31: 63
- 2026-08-30: 62
- 2026-08-29: 62
- 2026-08-28: 61
- 2026-08-27: 61
- 2026-08-26: 60
- 2026-08-25: 60
- 2026-08-24: 59
- 2026-08-23: 59
- 2026-08-22: 58

## Common questions

### What is the dev.workers.dolerite.base-onchain-tools/base-onchain-tools MCP server?

dev.workers.dolerite.base-onchain-tools/base-onchain-tools is an MCP server listed in the public MCP registry as dev.workers.dolerite.base-onchain-tools/base-onchain-tools. Base mainnet analysis: contract audits, transfer simulation, token pricing. Paid via x402. This page covers its hosted endpoint (https://base-onchain-tools.dolerite.workers.dev/mcp).

### Is the dev.workers.dolerite.base-onchain-tools/base-onchain-tools MCP server safe to use?

dev.workers.dolerite.base-onchain-tools/base-onchain-tools scores 72 out of 100 on VerifyMCP. 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 dev.workers.dolerite.base-onchain-tools/base-onchain-tools MCP server expose?

dev.workers.dolerite.base-onchain-tools/base-onchain-tools exposes 12 tools: base_demo, base_address_check, base_tx_check, base_token, base_gas, and 7 more. Their descriptions and schemas cost roughly 1,396 tokens of context every time the server is loaded.

### Does the dev.workers.dolerite.base-onchain-tools/base-onchain-tools MCP server require authentication?

No. We connected to dev.workers.dolerite.base-onchain-tools/base-onchain-tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the dev.workers.dolerite.base-onchain-tools/base-onchain-tools MCP server still maintained?

dev.workers.dolerite.base-onchain-tools/base-onchain-tools is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://base-onchain-tools.dolerite.workers.dev/mcp
- Website: https://base-onchain-tools.dolerite.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-dolerite-base-onchain-tools-base-onchain-tools/base-onchain-tools.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-dolerite-base-onchain-tools-base-onchain-tools/base-onchain-tools.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-dolerite-base-onchain-tools-base-onchain-tools/base-onchain-tools