Skip to main content
Glama
Sign In
0xarchive-mcp

0xarchive-mcp

by 0xArchiveIO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

web3_signup

Create a free 0xArchive account and obtain an API key by providing a signed SIWE message and its EIP-191 signature.

Instructions

Create a free-tier 0xArchive account and get an API key using a signed SIWE message. Requires a challenge from web3_challenge signed with personal_sign (EIP-191). Returns an API key that can be used with all other tools.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "message": "<message>",
      "signature": "<signature>"
    },
    "name": "web3_signup"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesThe SIWE message from web3_challenge
signatureYesHex-encoded signature from personal_sign (0x-prefixed, 65 bytes)

Output Schema

NameRequiredDescriptionDefault
dataYesResult data object

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.9.0

TDQS

A3.7/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already convey non-read-only, non-destructive, and non-idempotent behavior. The description adds detail about requiring a generated challenge and signature format, but does not discuss error cases, idempotency effects, or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences effectively convey the action, prerequisites, and output with no unnecessary words. Very concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Provides sufficient context for a simple two-parameter tool with an output schema. Covers the purpose, prerequisites, and result. Could mention that the API key should be stored securely, but current content is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already covers both parameters with descriptions. The description adds context by linking the message to web3_challenge and the signature to personal_sign, clarifying the workflow beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it creates a free-tier account and returns an API key, specifying the required inputs. However, it does not explicitly distinguish from sibling tools like web3_list_keys or web3_revoke_key, leaving some room for ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Specifies the prerequisite of a challenge from web3_challenge signed with personal_sign, but does not provide exclusions or mention when to use alternatives (e.g., if the user already has an account).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools