realia-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REALIA_API_URL | No | Base URL of the Realia API. Defaults to https://realiahq.xyz | https://realiahq.xyz |
| REALIA_API_TOKEN | No | Your Realia API token. Required for write operations (whoami, upload_dataset, launch_coin). Without it, read tools work on public data. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_datasetsA | Search the real-world datasets published on Realia by title, description, or column name. Returns each dataset's id, size, and field names. Leave the query empty for the newest ones. Use get_dataset for the full schema and a sample row. |
| get_datasetA | Read one dataset in full: every column with type and description, one sample row, and the coin launched on it if there is one. The file itself is not public — this returns the schema and sample only. |
| list_launchpadA | List the coins launched on Realia datasets, newest first, with mint address, pump.fun link, status, and the dataset each one is backed by. |
| get_coinA | Look up one coin by mint address or coin id, and get the dataset behind it — including that dataset's schema. Answers 'what data is this coin actually backed by?'. |
| whoamiA | Show which Realia account this server's API token belongs to, and the Solana wallets on it. Use this first when an upload or launch fails with an authentication error. |
| upload_datasetA | Publish a CSV, TSV, or JSON dataset to Realia under the account this token belongs to. Pass the file's text directly as |
| launch_coinA | Stage a pump.fun launch for a dataset this account uploaded, and return a link the user opens to sign with their wallet. This tool cannot spend anything on its own: no transaction is built or signed here, and the link expires. Give the user the returned confirmUrl. |
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
The tools are mostly distinct: search/get for datasets, list/get for coins, upload/launch for publishing, and whoami for auth. There is slight overlap between get_dataset and get_coin (both return dataset schema), but the context differs. The naming is clear enough to avoid major misselection.
The naming follows a consistent verb_noun pattern (search_datasets, get_dataset, list_launchpad, get_coin, upload_dataset, launch_coin). The exception is 'whoami', which is a conventional but different style. Overall, the pattern is predictable and readable.
The server provides 7 tools, which is well within the ideal range. Each tool addresses a distinct core function (searching, retrieving, listing, uploading, launching, and authentication). No tool feels redundant or out of place, and the count is neither too thin nor too heavy.
The tools cover the main lifecycle: search/get datasets, upload datasets, list/get coins, launch a coin, and check auth. However, there is an obvious gap: no tool to update or delete a dataset, or to manage a coin after launch. These missing operations could hinder workflows that require dataset maintenance.