Emercoin Agent
Server Details
On-chain identity and durable memory for AI agents on the Emercoin blockchain (NVS).
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- emercoin/emer-ai-tools
- GitHub Stars
- 7
- Server Listing
- Emercoin Agent
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.7/5 across 5 of 5 tools scored.
Each tool targets a distinct function: node status, session identity, record reading, identity registration, and memory storage. There is no overlap or ambiguity.
All tool names follow a consistent lowercase_with_underscores pattern (node_status, read_record, register_identity, store_memory, whoami). whoami is a standard exception but fits the pattern.
Five tools is appropriate for a focused MCP server handling node health, identity management, and on-chain storage. Each tool earns its place without excess or deficiency.
The set covers the core workflow: check node health, manage identity, read/write records. A minor gap is the lack of a delete or update operation for records, but these are less critical for the intended use case.
Available Tools
5 toolsnode_statusNode statusRead-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| blocks | No | |
| synced | No | |
| headers | No | |
| version | No | |
| connections | No | |
| verificationprogress | No |
read_recordRead NVS recordRead-onlyIdempotentInspect
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 | Required | Description | Default |
|---|---|---|---|
| name | 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. |
Output Schema
| Name | Required | Description |
|---|---|---|
| name | No | |
| time | No | |
| txid | No | |
| value | No | |
| status | No | |
| address | No | |
| pending | No | |
| operation | No | |
| days_added | No | |
| pending_update | No | |
| address_is_mine | No |
register_identityRegister identityIdempotentInspect
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 | Required | Description | Default |
|---|---|---|---|
| address | 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 here). | |
| metadata | No | Optional JSON object stored verbatim in the identity record, e.g. {"agent": "my-bot", "url": "https://..."}. Omit if unused. |
Output Schema
| Name | Required | Description |
|---|---|---|
| name | Yes | |
| txid | Yes |
store_memoryStore memoryInspect
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 | Required | Description | Default |
|---|---|---|---|
| metadata | No | Optional JSON object stored with the record (note, source, tags, …). Omit if unused. | |
| content_hash | 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. |
Output Schema
| Name | Required | Description |
|---|---|---|
| name | Yes | |
| txid | Yes |
whoamiWho am IRead-onlyIdempotentInspect
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.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
| hint | No | |
| tariff | No | |
| github_id | No | |
| github_login | No | |
| authenticated | No |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Your Connectors
Sign in to create a connector for this server.