@joinmassive/mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MASSIVE_TOKEN | Yes | Your Massive API token. Get it from https://dashboard.joinmassive.com → Developer → API Keys |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| web_fetchA | Fetch any URL through Massive. Returns Markdown by default (best for LLM consumption); also supports rendered HTML and raw HTML. Handles JS rendering, captcha solving, and 195+ country geo-targeting. Cost: 1 credit base. Multipliers stack:
Use expiration=0 for always-live data (prices, scores). Default expiration=1 (day) reuses cached results. Live pricing: https://joinmassive.com/pricing |
| web_searchA | Google search results parsed into structured JSON. Returns organic results, AI overview (if present), and 'people also ask' questions. Cost: 1 credit base. No multipliers. Use expiration=0 for always-live results; default expiration=1 (day) reuses cached SERPs. Localize with country, subdivision, city, language, display. |
| ai_chat_completionA | Get a chatbot answer (ChatGPT, Gemini, Perplexity, or Copilot) with structured sources. Cost: 1 credit base. No multipliers. Use expiration=0 for fresh answers; default expiration=1 (day) reuses cached responses. Localize with country, subdivision, city, language, display, device. |
| account_statusA | Returns the user's remaining credit balance. Free; does not consume credits. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| web_search_full | Google search: top 10 organic results, AI overview, and people-also-asked. |
| web_fetch_markdown | Fetch a URL as Markdown. |
| ai_chat_full | Ask a chatbot (ChatGPT/Gemini/Perplexity/Copilot) and show answer + sources. |
| account_check | Show my Massive credit balance. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| pricing | Credit cost per endpoint and difficulty/speed multipliers. |
| geotargeting | Country / subdivision / city formats and examples for routing requests. |
| changelog | What's new in each release. |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: account_status for credit balance, ai_chat_completion for chatbot responses, web_fetch for fetching URLs, and web_search for search results. No overlap.
All tools use snake_case and follow a verb_noun pattern: account_status, ai_chat_completion, web_fetch, web_search. Naming is uniform and predictable.
With 4 tools, the server is well-scoped for its purpose of providing access to various Massive services. Not too few, not too many.
The tool set covers the core functionalities: account info, AI chat, web fetch, and search. A minor gap is the lack of a tool for user profile or usage history beyond credits, but the current set is sufficient for typical use.