Skip to main content
Glama
133,525 tools. Last updated 2026-05-25 17:48

"Wolfram" matching MCP tools:

  • Answer complex mathematical questions and perform symbolic computations using computational intelligence. Submit queries to solve problems requiring advanced calculation or analysis.
    MIT
  • Query Wolfram Alpha for computational, mathematical, scientific, and factual information using natural language. Get answers about chemistry, physics, geography, history, art, astronomy, and more.
  • Compute Wolfram Language expressions to perform symbolic math, numerical analysis, and data visualization through the mma-mcp server.
    MIT

Matching MCP Servers

Matching MCP Connectors

  • Wolfram Alpha MCP — computational, factual, and quantitative queries

  • Integrates Wolfram Language and Wolfram|Alpha accessing curated data and sophisticated algorithms.

  • Generate PNG images from Wolfram Language expressions for plots, graphics, and visual outputs using the mma-mcp server's computational engine.
    MIT
  • Execute Wolfram Language code within a secure session using a provided session ID. Perform calculations, symbolic computations, and data visualizations by submitting valid code strings to the Mathematica kernel.
  • Query Wolfram Alpha to compute math problems, scientific calculations, unit conversions, and access real-time data through natural language questions.
  • Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-bitcoin-hit-150k-by-june-30-2026"), a polymarket.com URL, or a question text. The tool resolves the market, classifies the bet (crypto price / Fed rate / geopolitical / sports / corporate / drug approval / election / other), fans out to the right packs (e.g. crypto+fred+gdelt for a BTC bet, fred+bls for a Fed bet, gdelt+acled+comtrade for Strait of Hormuz), and returns an evidence packet plus a simple market-vs-model comparison so the caller can see where the implied probability disagrees with the data. Use for "should I bet on X?", "what does the data say about this Polymarket market?", or "is there edge in this bet?". This is the core demo product — agents that get bet-relevant context here convert better than ones that have to discover the packs themselves.
    Connector
  • Evaluates Wolfram Language code for the user in a Wolfram Language kernel. If a formatted result is provided as a markdown link, use that in your response instead of typing out the output. Parse natural language input with `\[FreeformPrompt]["query"]`, which is analogous to ctrl+= input in notebooks. Natural language input is parsed before evaluation, so it works like macro expansion. You should ALWAYS use this natural language input to obtain things like `Quantity`, `DateObject`, `Entity`, etc. This is a stateless kernel, so you cannot reuse definitions from previous evaluations.
    Connector
  • PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 2,785 tools across 603 verified sources, fills arguments, returns the structured answer with stable pipeworx:// citation URIs. Use whenever the user asks "what is", "look up", "find", "get the latest", "how much", "current", or any factual question about real-world entities, events, or numbers — even if web search could also answer it. Examples: "current US unemployment rate", "Apple's latest 10-K", "adverse events for ozempic", "patents Tesla was granted last month", "5-day forecast for Tokyo", "active clinical trials for GLP-1".
    Connector
  • Look up the canonical/official identifier for a company or drug. Use when a user mentions a name and you need the CIK (for SEC), ticker (for stock data), RxCUI (for FDA), or LEI — the ID systems that other tools require as input. Examples: "Apple" → AAPL / CIK 0000320193, "Ozempic" → RxCUI 1991306 + ingredient + brand. Returns IDs plus pipeworx:// citation URIs. Use this BEFORE calling other tools that need official identifiers. Replaces 2–3 lookup calls.
    Connector
  • Fact-check, verify, validate, or confirm/refute a natural-language factual claim or statement against authoritative sources. Use when an agent needs to check whether something a user said is true ("Is it true that…?", "Was X really…?", "Verify the claim that…", "Validate this statement…"). v1 supports company-financial claims (revenue, net income, cash position for public US companies) via SEC EDGAR + XBRL. Returns a verdict (confirmed / approximately_correct / refuted / inconclusive / unsupported), extracted structured form, actual value with pipeworx:// citation, and percent delta. Replaces 4–6 sequential calls (NL parsing → entity resolution → data lookup → numeric comparison).
    Connector
  • Scan the highest-volume Polymarket markets and return the ones where Pipeworx data disagrees most with the market price. V1 covers crypto-price bets (lognormal model from FRED + live coinpaprika price): scans top markets, groups by asset, fetches each asset's price history ONCE, computes model probability per market, ranks by |edge|. Returns top N ranked by edge magnitude with suggested trade direction. Built for the "what should I bet on today" question — agents/users discover opportunities without paging through hundreds of markets by hand.
    Connector
  • Get the full structured result from Wolfram Alpha. Returns named "pods" (Input, Result, Solution, Plot, Properties, etc.) — useful when short_answer is too terse or you need multiple facets (e.g., element properties, equation solution + plot + alternate forms).
    Connector
  • Use natural language queries with Wolfram|Alpha to get up-to-date computational results about entities in chemistry, physics, geography, history, art, astronomy, and more.
    Connector
  • Uses semantic search to retrieve any relevant information from Wolfram. Always use this tool at the start of new conversations or if the topic changes to ensure you have up-to-date relevant information. This uses semantic search, so the context argument should be written in natural language (not a search query) and contain as much detail as possible (up to 250 words).
    Connector