Emercoin Agent
REMOTE · AI.EMERCOIN.COM · 2 COMPONENTS · SCANNED AUG 3
On-chain identity and durable memory for AI agents on the Emercoin blockchain (NVS).
Available components
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. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · ai.emercoin.com
claude mcp add --transport http emercoin-emercoin-agent https://ai.emercoin.com/mcp
[mcp_servers.emercoin-emercoin-agent] url = "https://ai.emercoin.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"emercoin-emercoin-agent": {
"type": "remote",
"url": "https://ai.emercoin.com/mcp",
"enabled": true
}
}
} openclaw mcp add emercoin-emercoin-agent --url https://ai.emercoin.com/mcp --transport streamable-http
mcp_servers:
emercoin-emercoin-agent:
url: "https://ai.emercoin.com/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://ai.emercoin.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=emercoin.com | CN=WE1,O=Google Trust Services,C=US | 27 Jul 2026 | 25 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | c9e224924e86b348130bbb02b24c3e2b |
| SANs: emercoin.com, *.emercoin.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of ai.emercoin.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| emercoin.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai.emercoin.com/mcp | Verified | 200 | |
| http (plaintext) | http://ai.emercoin.com/mcp | HTTPS enforced | 301 | https://ai.emercoin.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
node_status Node status ~89
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`.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | — | — | — |
| connections | — | — | — |
| headers | — | — | — |
| synced | — | — | — |
| verificationprogress | — | — | — |
| version | — | — | — |
No examples provided.
read_record Read NVS record ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | — | — | — |
| address_is_mine | — | — | — |
| days_added | — | — | — |
| name | — | — | — |
| operation | — | — | — |
| pending | — | — | — |
| pending_update | — | — | — |
| status | — | — | — |
| time | — | — | — |
| txid | — | — | — |
| value | — | — | — |
No examples provided.
register_identity Register identity ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | — |
| txid | string | yes | — |
No examples provided.
store_memory Store memory ~212
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content_hash | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | — |
| txid | string | yes | — |
No examples provided.
whoami Who am I ~98
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| authenticated | boolean | — | — |
| github_id | — | — | — |
| github_login | — | — | — |
| hint | — | — | — |
| tariff | — | — | — |
No examples provided.