list_events — Agent.chain.tokyo Address Contracts MCP Tool Read-only
list_events
(list events) is one of 9 tools on the
Agent.chain.tokyo Address Contracts
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_events from your client
- Claude Code Agent.chain.tokyo Address Contracts list_events run in your project directory
- Claude Desktop Agent.chain.tokyo Address Contracts list_events ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agent.chain.tokyo Address Contracts list_events ~/.cursor/mcp.json
- VS Code Agent.chain.tokyo Address Contracts list_events .vscode/mcp.json
- Zed Agent.chain.tokyo Address Contracts list_events ~/.config/zed/settings.json
- Windsurf Agent.chain.tokyo Address Contracts list_events ~/.codeium/windsurf/mcp_config.json
- Cline Agent.chain.tokyo Address Contracts list_events ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agent.chain.tokyo Address Contracts list_events ~/.gemini/settings.json
- Grok Agent.chain.tokyo Address Contracts list_events .mcp.json (in your project root)
- ChatGPT Agent.chain.tokyo Address Contracts list_events Settings → Connectors → Advanced → Developer mode
- Claude.ai Agent.chain.tokyo Address Contracts list_events Settings → Connectors → Add custom connector
- LangChain Agent.chain.tokyo Address Contracts list_events pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http address-contracts https://mainnet.agent.chain.tokyo/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.