Seitrace Insights MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_BASE_URL | No | Base URL for the Seitrace Insights API | https://seitrace.com/insights |
| SECRET_APIKEY | Yes | Seitrace 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
| Name | Description |
|---|---|
| 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
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
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.
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.
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.
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.