omnistream-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OMNI_KEY | No | Your Omni API key (required for call_api) | |
| OMNI_GATEWAY | No | Gateway base URL (override for self-hosted) | https://grid.skinvaults.online |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_apisA | List all published APIs on the OmniStream marketplace. Returns slug, title, category, endpoint count, rating, and uptime for each API. Use this to browse what is available before calling search_apis or get_api. |
| search_apisA | Search the OmniStream marketplace by keyword using BM25 ranking. Searches across API titles, descriptions, tags, and endpoint names. Returns ranked results with relevance scores. |
| get_apiA | Get full details for a specific API: description, base URL, authentication method, all endpoints with their HTTP method, path, parameters, and summary. Use this before calling call_api to understand what parameters an endpoint needs. |
| list_endpointsA | List all endpoints for a specific API with their operation IDs, HTTP methods, paths, and required parameters. Lighter than get_api when you only need the endpoint list. |
| call_apiA | Call any published API on the OmniStream marketplace using the proxy. Your Omni key (OMNI_KEY env var) authenticates the request - you never need the upstream API key. Use get_api first to learn the available endpoints and their parameters. |
| list_streamsA | List all available real-time data streams on the OmniStream Grid. Returns stream ID, title, category, update interval, and current subscriber count. |
| get_streamA | Get details for a specific real-time stream including description, update interval, and the last 5 data samples to understand the payload shape. |
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 7 tools
Each tool has a distinct purpose: call, get details, list, search, and stream-specific operations. No two tools overlap in functionality.
All tools follow a consistent verb_noun pattern using snake_case (e.g., list_apis, call_api), making them predictable and easy to understand.
With 7 tools, the set is well-scoped for an API and stream marketplace, covering browsing, inspection, and invocation without excess.
The tool set covers key operations for APIs (list, search, get details, list endpoints, call) and streams (list, get details). Minor gaps like lacking filtering or pagination options prevent a perfect score.