Skip to main content
Glama
Seitrace

Seitrace Insights MCP Server

Official
by Seitrace

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
API_BASE_URLNoBase URL for the Seitrace Insights APIhttps://seitrace.com/insights
SECRET_APIKEYYesSeitrace API key; used to set header `x-api-key`

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
list_resourcesB

List available resources (e.g., insights_erc20, insights_erc721, insights_native).

list_resource_actionsC

List actions for a given resource.

get_resource_action_schemaC

Get the JSON Schema for a specific resource action.

invoke_resource_actionC

Invoke a resource action with a payload matching its schema.

get_resource_action_snippetC

Generate a code snippet to perform a resource action in the specified language. For example, a JavaScript snippet to call the action with the required parameters.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: list_resources enumerates available resources, list_resource_actions enumerates actions for a resource, get_resource_action_schema retrieves schema details, get_resource_action_snippet generates code, and invoke_resource_action executes the action. The descriptions clearly differentiate their functions, eliminating any ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case, with verbs like 'get', 'list', and 'invoke' paired with descriptive nouns (e.g., 'resource_action_schema', 'resource_action_snippet'). This uniformity makes the set predictable and easy to understand.

Tool Count5/5

With 5 tools, the set is well-scoped for a server focused on resource action management. Each tool serves a specific role in the workflow (listing, schema retrieval, snippet generation, invocation), and none feel redundant or missing, making the count appropriate for the domain.

Completeness5/5

The tool surface provides complete coverage for interacting with resource actions: listing resources and their actions, retrieving schemas and code snippets, and invoking actions. This covers the full lifecycle from discovery to execution, with no apparent gaps for the server's purpose.

Maintenance

ActivityInactive
ResponsivenessNo issues