# Emercoin Agent (remote · ai.emercoin.com)

On-chain identity and durable memory for AI agents on the Emercoin blockchain (NVS).

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `ai.emercoin.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/emercoin-emercoin-agent/ai.md), [page](https://verifymcp.io/servers/emercoin-emercoin-agent/ai)
- oci · `docker.io/emercoin/mcp:0.1.0`: 6/100, [markdown](https://verifymcp.io/servers/emercoin-emercoin-agent/docker-io-emercoin-mcp-0-1-0.md), [page](https://verifymcp.io/servers/emercoin-emercoin-agent/docker-io-emercoin-mcp-0-1-0)

## Channel facts

- Endpoint: `https://ai.emercoin.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-08-03.

- **Endpoint Security**: 57/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 3 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 is enforced; there's no plaintext access path.
  - 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**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 963 tokens (~192/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http emercoin-emercoin-agent https://ai.emercoin.com/mcp
```

### Codex

```toml
[mcp_servers.emercoin-emercoin-agent]
url = "https://ai.emercoin.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "emercoin-emercoin-agent": {
      "type": "remote",
      "url": "https://ai.emercoin.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add emercoin-emercoin-agent --url https://ai.emercoin.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  emercoin-emercoin-agent:
    url: "https://ai.emercoin.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "emercoin-emercoin-agent": {
      "type": "http",
      "url": "https://ai.emercoin.com/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-08-03 (score 66, +1)

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

### 2026-08-01 (score 65, +1)

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

### 2026-07-31 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

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

### 2026-07-28 (score 63, +1)

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

### 2026-07-27 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (5)

### `node_status` (~89 tokens)

Node status

Report the Emercoin node's version, block height, header height, peer
    connections and sync state (`synced` true once block == header height).
    Read-only, no sign-in required, no parameters. Call it first in a session to
    confirm the node is healthy and fully synced before trusting `read_record` or
    writing with `register_identity` / `store_memory`.

Output parameters:

- `blocks`
- `connections`
- `headers`
- `synced`
- `verificationprogress`
- `version`

### `read_record` (~204 tokens)

Read NVS record

Read one Emercoin NVS (Name-Value Storage) record by its full name — an
    agent's identity (`ai:gh:<github_id>`) or a memory
    (`ai:gh:<github_id>:mem:<hash>`) written by `register_identity` / `store_memory`.
    Returns the confirmed on-chain record, or a `pending` one still in the mempool —
    the `status` field ('confirmed' | 'pending') distinguishes them. Read-only, no
    sign-in required; use `whoami` to find your own github_id. Returns null fields
    for a name that does not exist.

Input parameters:

- `name` (string, required): Full NVS record name to read. Identity records are 'ai:gh:<github_id>' (e.g. 'ai:gh:3772563'); memory records are 'ai:gh:<github_id>:mem:<sha256-hex>'. Any existing NVS name works.

Output parameters:

- `address`
- `address_is_mine`
- `days_added`
- `name`
- `operation`
- `pending`
- `pending_update`
- `status`
- `time`
- `txid`
- `value`

### `whoami` (~98 tokens)

Who am I

Report the current session's identity. Read-only, no sign-in required: an
    anonymous session gets `{authenticated: false}` with a hint (not an error),
    a signed-in one gets `{authenticated: true}` plus the GitHub-rooted id, login
    and tariff. Call it to confirm who you are before `register_identity` /
    `store_memory`; an anonymous caller must sign in (GitHub OAuth) first.

Output parameters:

- `authenticated` (boolean)
- `github_id`
- `github_login`
- `hint`
- `tariff`

### `register_identity` (~245 tokens)

Register identity

Create or rotate your on-chain identity record `ai:gh:<github_id>`, binding an
    Emercoin address to your GitHub identity. Requires a signed-in session (OAuth)
    and counts against the FREE-tier per-minute write limit. Run `whoami` first to
    confirm you are signed in; anchor memories under this identity afterwards with
    `store_memory`. Writes one NVS transaction paid by the gateway (you need no EMC);
    the record reads back as `pending` at once and `confirmed` after the next block
    (~10 min on average). Idempotent — calling again rebinds the address. Returns the
    record name and the transaction id.

Input parameters:

- `address` (string, required): Emercoin address to bind to your GitHub identity, e.g. 'EVfAn...'. It is the anchor for later signature login — you must control its key (control is proven when you sign a challenge at login, not her…
- `metadata`: Optional JSON object stored verbatim in the identity record, e.g. {"agent": "my-bot", "url": "https://..."}. Omit if unused.

Output parameters:

- `name` (string)
- `txid` (string)

### `store_memory` (~212 tokens)

Store memory

Anchor a memory/artifact on-chain as the NVS record
    `ai:gh:<github_id>:mem:<content_hash>` — a tamper-evident fingerprint others can
    verify later. Requires a signed-in session (OAuth) and counts against the
    FREE-tier per-minute write limit. Writes one NVS transaction paid by the gateway;
    reads back `pending` at once, `confirmed` after the next block (~10 min). Not
    idempotent — each distinct hash is a new record. Register your identity first.
    Returns the record name and the transaction id.

Input parameters:

- `content_hash` (string, required): Hash of the artifact/memory, e.g. a SHA-256 hex digest. It becomes the record's ':mem:<hash>' suffix; the content itself stays off-chain (e.g. IPFS) — only this fingerprint is anchored.
- `metadata`: Optional JSON object stored with the record (note, source, tags, …). Omit if unused.

Output parameters:

- `name` (string)
- `txid` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/emercoin-emercoin-agent/ai#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 64
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 62

## Links

- Remote endpoint: https://ai.emercoin.com/mcp
- Repository: https://github.com/emercoin/emer-ai-tools
- Website: https://ai.emercoin.com/
- Changelog RSS feed: https://verifymcp.io/servers/emercoin-emercoin-agent/ai/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/emercoin-emercoin-agent/ai/changelog.json
- HTML version of this page: https://verifymcp.io/servers/emercoin-emercoin-agent/ai