# chainward [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/saltxd/chainward  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/chainward

## Description
Check a Base or BNB Chain address before you pay it: on-chain risk reports, EAS attestations.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "chainward": {
    "command": "npx",
    "args": ["-y","chainward-mcp-server"]
  }
}
```

## Documentation

## What the chainward MCP server does

The chainward MCP server connects MCP-compatible agents to ChainWard's address investigation service. It is intended for checking an address before sending payment, especially on Base or BNB Chain. Results are reports containing risk flags tied to the transactions behind them, not a binary statement that an address is safe or unsafe.

The service also provides an OFAC sanctions screen. That screen checks an address against the U.S. Treasury SDN list and reports whether the address is listed. A result indicating that an address is not listed is not a clearance and should not be treated as proof that the address is safe.

Reports can be attested with Ethereum Attestation Service on Base. This gives an agent or contract a way to inspect an on-chain attestation without depending only on the ChainWard API.

## How it works

The chainward MCP server is available in two forms. A local MCP process can be started with the `chainward-mcp-server` npm package through `npx`. Alternatively, an MCP client can connect to `https://api.chainward.ai/mcp` using Streamable HTTP. The hosted endpoint does not require a key according to the project documentation.

Behind the service, ChainWard reads chain data from a self-hosted Base node rather than depending on a third-party RPC provider for its Base ground truth. Its broader investigation system researches targets, produces reports, and checks factual and numeric claims against chain data before publication. That automated verification pipeline is part of the project context, while the MCP interface is the agent-facing route for address checks and related report data.

Risk checks are available for Base and BNB Chain. The sanctions endpoint supports any EVM chain. Paid HTTP variants use x402 payments, including a 0.05 USDC counterparty check and a 0.01 USDC sanctions check, but the README does not state that MCP clients must handle those payment flows.

## Setup and configuration

For a local process, run:

```bash
npx -y chainward-mcp-server
```

Configure the command in an MCP-compatible client such as Claude or Cursor. The repository also publishes the package through the MCP Registry under `io.github.saltxd/chainward`.

For a hosted connection, use this MCP URL:

```text
https://api.chainward.ai/mcp
```

No required environment variables or API key are documented for the hosted MCP endpoint. The project README does not provide client-specific configuration beyond the npm command and hosted URL.

## Tools and capabilities

The chainward MCP server supports these documented use cases:

- Check a Base address before paying it.
- Check a BNB Chain address before paying it.
- Retrieve risk flags linked to underlying transactions.
- Screen an address against the OFAC SDN list.
- Read report attestations recorded through EAS on Base.

The public API also documents direct HTTP routes for risk checks, counterparty checks, and sanctions checks. The README does not list individual MCP tool names, input schemas, or response schemas, so those details should be obtained from the server or its OpenAPI documentation rather than assumed from the package name.

## Limitations and notes

Risk output is evidence for review, not a safety verdict. An address can have no reported flag without being proven safe. Likewise, an OFAC result of “Not listed” only means that the address was not found on the referenced list; it is not a general sanctions clearance.

The README specifically identifies Base and BNB Chain for address risk checks. It identifies any EVM chain for the sanctions screen. The hosted MCP endpoint is described as keyless, but the project also exposes paid x402 HTTP routes, so payment behavior may differ when using those direct API endpoints.

The available documentation does not enumerate MCP tool names or guarantee support for every response field. Developers needing exact schemas should consult `https://api.chainward.ai/openapi.json` and the live MCP server.

_Full upstream README: https://allmcps.com/mcp/chainward/readme_