Free Live Data MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RAPIDAPI_KEY | Yes | Your RapidAPI application key. Create a RapidAPI account, join each API's free plan and copy your application key. The same key can serve your subscribed APIs. Required for live calls; catalog exploration works without a 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
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 |
|---|---|
| search_apisA | Find supported live-data APIs by source, country, category or task. Returns free-plan enrollment links. Discovery does not require an API key. |
| search_endpointsA | Find operations within an API or across the catalog. Search for the task or for lookup/autocomplete operations when an entity ID is required. Discovery uses local metadata and no API quota. |
| describe_endpointA | Inspect one operation, its required parameters, allowed values and defaults before calling it. Parameter identifiers must come from the user or source lookup results. |
| call_endpointB | Fetch source data using a documented GET operation. Requires RAPIDAPI_KEY and enrollment in this API plan. One call consumes upstream quota. maxItems limits returned array previews, not the upstream request. Use schema parameter names exactly. |
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 4 tools
The tools map to a clean discovery→inspect→execute pipeline, with search_apis (sources) and search_endpoints (operations) targeting different resource levels. The only mild overlap is that an agent might start with search_endpoints when it should first enumerate sources, but the descriptions clarify the workflow.
All four names follow a verb_noun snake_case pattern (search_apis, search_endpoints, describe_endpoint, call_endpoint). The verb choice also encodes the workflow stage (search → describe → call), which is predictable.
Four tools is lean but proportionate to a read-only live-data catalog: discovery, inspection, and execution each earn their place. It sits just below the ideal mid-range breadth but nothing feels redundant.
The surface covers the full read lifecycle: find an API, find an operation, learn its parameters, then call it. Gaps are minor — there is no tool to verify enrollment/API-key status or check remaining quota before consuming it, though errors from call_endpoint likely surface these.