Skip to main content
Glama
JussCubs

mcp-server-test

by JussCubs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
fetch_leaderboardB

Fetch Vector leaderboard data

Args:
    leaderboard_type: Type of leaderboard (e.g., 'PNL_WIN', 'TRADE_VOLUME')
    
Returns:
    JSON string with leaderboard data
fetch_profileB

Fetch detailed profile data for a Vector trader

Args:
    username: Vector username to fetch
    
Returns:
    JSON string with profile data
fetch_token_dataA

Fetch trending Solana tokens from Vector

Returns:
    JSON string with token data
fetch_token_broadcastsB

Fetch broadcasts for a specific token

Args:
    token_id: Vector token ID
    
Returns:
    JSON string with token broadcasts

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a unique purpose: leaderboard, profile, token broadcasts, and token data. There is no overlap between fetching different data types.

Naming Consistency5/5

All tools follow a consistent 'fetch_' prefix with descriptive nouns (leaderboard, profile, token_broadcasts, token_data) in snake_case.

Tool Count4/5

4 tools is a reasonable number for a focused data retrieval server. It covers key endpoints without being excessive or too sparse.

Completeness4/5

The set covers major data categories for a trading platform (leaderboard, profile, token info, broadcasts). Missing details like token price or history, but sufficient for common queries.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources