Skip to main content
Glama

Server Details

Web research across search, Reddit, YouTube, local businesses, reviews, ad libraries and more. Every answer carries line-numbered citations; up to 1,000 rows per call without loading them into context.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.5/5.0

Scored across 8 tools

Disambiguation5/5

Each tool targets a distinct stage of the research workflow: search, fetch, store/read, query, poll, SEO analysis, and bug reporting. The collected-record tools are clearly separated by intent: ask for synthesis, grep for exact matching/counting, and read for full or ranged reading. Search, fetch, and SEO metrics are also explicitly differentiated in their descriptions.

Naming Consistency4/5

All names use snake_case and are readable, with most following a verb_noun pattern such as ask_collected_records, grep_collected_records, get_task_results, and report_bug. The main deviations are advanced_web_fetch/advanced_web_search, which use an adjective-prefixed pattern, and seo_metrics, which is noun-only.

Tool Count5/5

Eight tools is well-scoped for a research server. Each tool has a clear role in the workflow, and there are no redundant or obviously filler tools.

Completeness4/5

The surface covers the core research lifecycle: discovery, full-page retrieval, persistent collected records, exact search, synthesis, async polling, SEO analysis, and bug reporting. Minor gaps exist around explicitly listing or managing collected records, but the main workflows are covered.

Publisher details

Operator
BRONTIR OÜ · Publisher source
Operator website
https://brontir.com/
Vendor relationship
Independent
Privacy policy
Not provided
Trust center
Not available
Restrictions
Free tier on signup, usage-based pricing above that. OAuth sign-in required. · Publisher source

Available Tools

8 tools
advanced_web_fetchAdvanced web fetchA
Read-only
Inspect

Fetch a webpage or any URL and get everything on it.

Content is saved for re-reading. It also reaches what a plain fetch cannot: the rendered page including JavaScript-generated text, the whole reply tree under a post, what was spoken in a video, the text of a PDF, what an image shows.

Best for: reading any known URL in full, including what a plain fetch misses.

Examples:

  • a news article → the article text, not the surrounding page

  • a thread with 300 replies → the whole tree, not the opening post

  • a 40-minute review video → transcript plus what commenters said about it

  • a long PDF report → text plus a line index to read only the relevant part

  • a site's sitemap or an RSS feed → the pages or entries it lists, with their dates

Use after advanced_web_search to open a result it found. Every relevant result carries mdOrHtmlDownloadUrl — a ready-to-use link that downloads that record as Markdown, no key attached, so it can be passed on as-is. Swap its ?type=md for ?type=html and the same link hands back the page's original HTML exactly as the site served it, markup and all — what an SEO reader needs and what Markdown drops; web-page fetches only.

If status: "running" is returned, poll get_task_results({ taskIds }).

Inputs: requests (required), isResearch, maxWaitSec.

ask_collected_recordsAsk over collected recordsA
Read-only
Inspect

Answer from collected records, with quotes tied to exact lines.

Extracts and synthesises across material too large to fit in context, and returns every claim traceable to a line range in the original. Use instead of summarising from memory whenever the evidence has to hold up — quotes come back with their locations, so they can be checked against the source.

Not for: exact wording or counting occurrences — grep_collected_records does that without an LLM call; or material small enough to read directly — use read_collected_records.

In quotes and both modes the output is quotes: [{ id: '{<uuid>}', index }] — one block per record, with index formatted like the index field of advanced_web_search / advanced_web_fetch results. Empty array when no quotable evidence is found. When part of the material could not be read or worked into the result, notes says what is missing. If status: "running" is returned, poll get_task_results({ taskIds }).

Inputs: mode (required), query (required), dataIds (required), maxWaitSec.

get_task_resultsGet task resultsA
Read-only
Inspect

Required after any call that returned status: running.

The task keeps working, but its results are not delivered until polled. The call waits for the next event — a new streaming chunk on any listed task, or a task settling — then returns the state of all listed tasks. Tasks settle one at a time: keep calling with the still-running ids to collect the rest (settledInThisCall lists the ones that just finished).

Streaming chunks from advanced_web_fetch, advanced_web_search and seo_metrics arrive in streaming.chunks; chunks already delivered are never redelivered. Act on partial chunks: fire follow-up calls in parallel and pass their new ids to the next get_task_results. A response carries a bounded amount of chunk data: when streaming.pendingChunks is set, that many more chunks of the task are waiting — call again with the same id to receive them, even if the task has finished. A record's index too long for one chunk continues in item.index chunks for the same id (indexPart of indexParts); its parts follow one another line by line.

credits.spent is what was charged since the previous response for the same tasks — a running task keeps charging after the call that started it answers — so spent summed over that first response and every poll is the full cost.

Inputs: taskIds (required), maxWaitSec.

grep_collected_recordsSearch inside collected recordsA
Read-only
Inspect

Find and count matches across everything collected, without loading it.

Returns only matching lines with their line numbers — the records themselves never enter context. Use to count how often a theme recurs across many sources, or to locate the exact line ranges worth loading in full via read_collected_records. Matching is literal: use grep_collected_records for exact wording and counts, ask_collected_records when the question needs interpretation across records.

Inputs: regex (required), dataIds (required), maxMatches, regexFlags, +1 more.

read_collected_recordsRead collected recordsA
Read-only
Inspect

Read collected records in full, or just the line ranges you need.

Records persist across turns, so nothing is fetched twice. Pass line ranges to bring only the relevant parts into context instead of an entire thread or transcript.

Inputs: dataIds (required).

report_bugReport a bugAInspect

Report a bug in this server's tools so the team that runs it can fix it.

Use it when one of this server's tools misbehaves: it returns an error that does not look like a problem with your request, its result is clearly wrong or incomplete for what was asked, it hangs or never finishes, or it does something other than its description says. File a problem once you have actually seen it, and once per problem.

Not for: a search that simply found nothing, a page that does not exist, an error whose hint tells you how to change the request, or a question the user should answer.

Describe what you called, what you expected and what happened instead. Name the tool in tool, paste the arguments you passed into toolInput and the error text or the wrong part of the result into observed. Put the task ids or record ids the problem involves into relatedIds, so the exact runs can be looked at.

Leave out personal data, credentials and anything the user has not agreed to share: the report is read by the people who run this server.

Filing a report is free and changes no result. You get a report number back; no reply comes through this tool, so carry on with the task.

Inputs: title (required), description (required), tool, observed, +3 more.

seo_metricsSEO metricsA
Read-only
Inspect

Answer questions about search visibility and search demand — keywords, rankings, links, domains, and how interest in a subject moves over time and across a country.

Use when the question is about how a site or a market performs in search rather than about what a page says: which keywords a domain ranks for, which pages earn its traffic, who competes with it, which terms it buys ads on, which sites rank or buy ads for a set of keywords, what links to it, how a keyword's demand and difficulty compare, whether interest in a subject is rising or falling, and which of a country's regions search for it most.

Examples:

  • "keywords ahrefs.com ranks in the top 3 for, with real volume"

  • "which pages of this site bring the most organic traffic"

  • "who competes with this domain and how big are they"

  • "keyword ideas around link building that are not brutally competitive"

  • "which sites are running Google ads on these keywords right now"

Ask in plain language. Do not write field names, operators or query syntax — the request is composed from your question, and what came back is described in the answer so you can check it matched what you meant.

Not for: what a specific page says (use advanced_web_fetch), or what people are posting right now (use advanced_web_search).

Results are stored as citable Data records — a large report comes back as a summary plus a line index, so read the parts you need with read_collected_records or search across them with grep_collected_records. Every relevant result carries mdOrHtmlDownloadUrl — a ready-to-use link that downloads that record as Markdown, no key attached, so it can be passed on as-is. Swap its ?type=md for ?type=html and the same link hands back the page's original HTML exactly as the site served it, markup and all — what an SEO reader needs and what Markdown drops; web-page fetches only.

If status: "running" is returned, poll get_task_results({ taskIds }).

Inputs: requests (required), isResearch, maxWaitSec.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources