Skip to directory

About Seitrace MCP

Local Seitrace MCP for Sei blockchain insights with a schema-first flow: discover resources, list their actions, fetch an action schema, invoke it, and optionally generate a client snippet.

What you can use it for

  • Discover and invoke Sei Insights actions with explicit schema retrieval and input validation.
Connection and setup
Hosting
Local MCP server
Transport
stdio
Endpoint
Local process; no hosted endpoint documented
Authentication
Node stdio server; SECRET_APIKEY is used as x-api-key for most live actions. Discovery can be performed without the key.

Requirements

  • Node.js 20 or newer
  • MCP client supporting local stdio
  • Seitrace Insights API key for most live calls

Setup steps

  1. Create an API key from Seitrace Insights.
  2. Add a local stdio server using npx -y @seitrace/mcp and set SECRET_APIKEY in the client environment. The package README shows API_BASE_URL as optional, defaulting to https://seitrace.com/insights.
  3. Reload the MCP connection.
  4. Discover resources, list a resource's actions, and retrieve that action's JSON schema before invoking it; the README marks schema retrieval as required.
Tools 5

Five MCP meta-tools are documented. They discover Sei resources/actions and schemas, then invoke them; the underlying action set is dynamic and requires the publisher API key.

  • list_resouces

    List available Seitrace resources. The upstream README spells “resources” as “resouces” in this identifier.

    01
  • list_resouce_actions

    List actions for a resource. The upstream README spells “resource” as “resouce” in this identifier.

    02
  • get_resource_action_schema

    Retrieve the JSON Schema for a resource action.

    03
  • invoke_resource_action

    Invoke a resource action with a schema-validated payload.

    04
  • get_resource_action_snippet

    Generate a code snippet for invoking a resource action.

    05
Limitations and notes
  • Most live API actions require a Seitrace API key. The upstream identifiers contain the spelling “resouce(s)” for two discovery tools; names are preserved exactly as documented.
Original sources
  • official tool reference

    Maintainer README documents five discovery/schema/invocation/snippet meta-tools. Names `list_resouces` and `list_resouce_actions` preserve the publisher’s literal spelling. The actual Sei API action catalog is discovered dynamically and requires API key.

  • official documentation or source

    Maintainer README documents five discovery/schema/invocation/snippet meta-tools. Names `list_resouces` and `list_resouce_actions` preserve the publisher’s literal spelling. The actual Sei API action catalog is discovered dynamically and requires API key.

Documentation checked 2026-10-28T13:00:03.000Z. Connection has not been runtime tested.

Similar tools