Brave Search MCP Server: web results, images, videos, rich results, AI summaries, and more.
Nothing to run from here
glim.sh is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
14
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Give your agent live data from Twitter, Reddit, the web and GitHub. No API keys, no scraping stack.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http glim-sh-mcp https://glim.sh/mcp
# 2 — ask your agent for something these tools do
# glim_twitter_search, glim_twitter_get, glim_reddit_search and 11 more
glim.sh costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GLAll 1 server
glim1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http glim-sh-mcp https://glim.sh/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Search Twitter/X. Returns a compact human-readable list by default; pass format='json' for full structured data. Use glim_twitter_get(ref) for full thread context. Use docs://search-operators for reference.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query with operators (e.g. 'from:elonmusk AI min_faves:100 within_time:7d') |
| sort | string | no | Sort by relevance or recency: "top" (most engaged tweets matching the query - best for "what's the conversation about X") or "latest" (newest first - best for monitoring/recency). Default: "top". |
| cursor | string | no | Pagination cursor from previous search. Ranking is strongest on page 1 - paged results under sort:'top' trend toward recency (upstream behavior). |
| start_date | string | no | Only tweets on or after this time. YYYY-MM-DD (UTC midnight) or ISO 8601 datetime with Z/offset (e.g. 2026-04-13T14:30:00Z) |
| end_date | string | no | Only tweets before this time. YYYY-MM-DD (inclusive through end of day UTC) or ISO 8601 datetime with Z/offset (e.g. 2026-04-13T14:30:00Z) |
| format | string | no | Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing. |
| expand_urls | boolean | no | When true, auto-crawl entity URLs and attach crawled_content to tweets. Off by default: responses can grow by up to 4KB per expanded URL. Use glim_web_fetch(url) for targeted crawls instead. |
Fetch a tweet or a user from one reference. A tweet URL (incl. handle-less /i/status/<id>) returns the tweet with full thread context, parent, and optional replies/quotes; a profile URL (https://x.com/<handle>) returns the user with recent tweets. Prefer full URLs - if you only have a numeric id, pass it as a quoted string. Returns a compact human-readable view by default; pass format='json' for f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ref | string | yes | Tweet URL or profile URL. A tweet URL (incl. /i/status/<id>) returns the tweet + thread; a profile URL (https://x.com/<handle>) returns the user + recent tweets. Prefer full URLs - if you only have a |
| include | array | no | Tweet refs only: also fetch 'replies' and/or 'quotes' |
| include_replies | boolean | no | Profile refs only: include replies in the timeline |
| include_mentions | boolean | no | Profile refs only: include the mentions timeline |
| cursor | string | no | Profile refs only: pagination cursor from next_cursor |
| format | string | no | Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing. |
| expand_urls | boolean | no | When true, auto-crawl entity URLs and attach crawled_content to tweets. Off by default: responses can grow by up to 4KB per expanded URL. Use glim_web_fetch(url) for targeted crawls instead. |
Search Reddit posts. Each result comes with full post content and its top comments, so a single search usually answers the question without follow-up. Compact human-readable text by default; pass format='json' for full structured data. Use glim_reddit_get(ref) for a single post's complete comment tree. Page with cursor (response gives next_cursor when more exist). See docs://reddit-search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query (e.g. 'subreddit:programming machine learning') |
| sort | string | no | Sort order. Keep 'relevance' (default) for question or topic queries - it ranks by how well posts match your query. 'top'/'hot' rank by score/recency and largely ignore the query text, so use them onl |
| time | string | no | Time range |
| limit | integer | no | Max posts (1-10), each with full content + top comments |
| cursor | string | no | Pagination cursor from a prior response's next_cursor |
| start_date | string | no | Only posts on or after this date (YYYY-MM-DD) |
| end_date | string | no | Only posts before this date (YYYY-MM-DD) |
| format | string | no | Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing. |
Fetch a Reddit post, subreddit, or user by ref. Posts return comments; subreddits and users return profile metadata plus recent activity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ref | string | yes | Post ID or URL, subreddit ref (r/programming or reddit.com/r/programming), or user ref (u/spez or reddit.com/user/spez) |
| comment_sort | string | no | Comment sort. Post refs only: subreddit/user listings always hydrate a fixed 2 top-level comments sorted by top. |
| comment_limit | integer | no | Max comments (post refs only) |
| comment_depth | integer | no | Max nesting depth (post refs only) |
| sort | string | no | Listing post sort |
| time | string | no | Listing time range |
| limit | integer | no | Max subreddit posts (1-10), each with full content + top comments |
| cursor | string | no | Pagination cursor from a prior subreddit response's next_cursor |
| include_posts | boolean | no | Include recent posts for user refs |
| include_comments | boolean | no | Include recent comments for user refs |
| format | string | no | Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing. |
Semantic web search powered by Exa. Returns titles, URLs, and the top query-relevant excerpt per result. Compact text by default; pass format='json' for full structured data incl. all excerpts per result. Use glim_web_fetch(url) for full page content. Matching is semantic, so a query with no real match still returns ten nearest-neighbour results rather than zero - judge relevance from the excerpts
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query |
| include_domains | array | no | Restrict results to these domains (e.g. ['arxiv.org']) |
| exclude_domains | array | no | Exclude results from these domains. Useful for filtering noisy aggregators or SEO farms when you've seen them dominate results (e.g. ['pinterest.com', 'quora.com']). |
| published_within_days | integer | no | Restrict to results published within the last N days. Skip this for broad queries - it excludes pages without publish-date metadata. Common values: 1, 7, 30, 365. |
| format | string | no | Output format. 'text' (default): compact human-readable list, fewer tokens. 'json': the same results as structured data (title, url, snippet, score, published_date, author). |
Fetch a single web page and extract clean content. Auto-tier server-side: handles SSR (Next.js, Nuxt, TikTok, Pinterest, YouTube), SPA shells, PDFs, paywall detection, residential-proxy escalation, and stealth profiles for TikTok / Instagram / Pinterest / YouTube. Returns clean markdown (default) with a YAML frontmatter header (url, outcome, total_chars). Read 'outcome' to classify the result (suc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | URL to fetch |
| format | string | no | Output format. 'markdown' (default) clean article text; 'html' raw cleaned HTML; 'json' the structured SSR blob (TikTok / Pinterest / YouTube) instead of article text. |
| selector | string | no | CSS selector to scope the result. An anchor-id selector (e.g. a docs anchor like '#usage') that lands on a heading expands to its whole section; other selectors return the matched elements themselves. |
Search GitHub repositories, conversations (issues+PRs), discussions, or code, with full GitHub search syntax in the query: qualifiers (repo:, org:/user:, language:, path:, symbol:, content:, is:, stars:, label:, sort:stars), boolean AND/OR/NOT with parentheses, "exact strings", and /regex/. kind='repos': MINIMAL distinctive keywords - the project/library name only ('rtk', 'react query'); every ext
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query in full GitHub search syntax: qualifiers (repo:owner/name, org:/user:, language:, path: with globs, symbol:, content:, is:, stars:>N, label:, sort:stars), boolean AND/OR/NOT with parenthe |
| kind | string | no | What to search: 'repos', 'conversations' (issues+PRs), 'discussions' (GitHub Discussions - a separate index from issues/PRs), or 'code' (literal/regex/symbol search across 2.8M+ public GitHub repos). |
| repo | string | no | Scope to one repository. Accepts 'owner/name', a github.com URL, or a partial 'owner/' (code). Works with any kind; setting it with kind=repos routes the search to conversations, since repo-name searc |
| page | integer | no | Page number |
| per_page | integer | no | Results per page |
| format | string | no | Output format. 'text' (default): compact human-readable previews, fewer tokens. 'json': full structured data for machine parsing. |
Fetch GitHub data from a single ref. GitHub URL or 'owner/repo' shorthand. A repo URL or owner/repo returns metadata + README; /pull/N -> PR (with comments + changed files), /issues/N -> issue, /discussions/N -> discussion (with threaded replies), /blob/<ref>/<path> -> file (raw.githubusercontent.com URLs work too), /tree/<ref>[/<path>] -> file tree (optionally scoped to a subdirectory), /commit/<
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ref | string | yes | GitHub URL or 'owner/repo' shorthand. A repo URL or owner/repo returns metadata + README; /pull/N -> PR (with comments + changed files), /issues/N -> issue, /discussions/N -> discussion (with threaded |
| page | integer | no | Page number |
| per_page | integer | no | Results per page |
| format | string | no | Output encoding. 'text' (default): compact human-readable text, fewer tokens (file returns raw content). 'json': machine-readable JSON. |
Pass exactly ONE of {query} or {category_slug}. Searches Amazon (com|co.uk|de|fr|es|it) and returns ranked hits with buybox price (gross + VAT-excluded net), ratings, review counts, and ASINs. Drill down with glim_amazon_get(ref). Set sort_by='most_reviewed' (with min_reviews to filter junk) for a trust-weighted re-rank within the current page. Compact text by default; pass format='json' for full
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free-text keyword query (mutually exclusive with category_slug) |
| category_slug | string | no | Amazon bestsellers category slug, e.g. 'electronics' (.com), 'elektronik' (.de), 'electronique' (.fr). Invalid slugs return 'not_found' - retry with a correct slug. |
| tld | string | no | Amazon marketplace: com | co.uk | de | fr | es | it |
| page | integer | no | Page number (1-20) |
| format | string | no | Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': the same hits as machine-readable JSON. Text already carries every field except image_url, which only json returns |
| sort_by | string | no | Server-side sort, except 'most_reviewed' which re-ranks the current page client-side by review count desc (rating tiebreaker). Pair 'most_reviewed' with min_reviews to skip thinly-reviewed items. |
| min_reviews | integer | no | Drop hits with fewer than N reviews. Pair with sort_by='most_reviewed' for a trust-weighted result. Applied client-side to organic/paid/suggested. |
| include_paid | boolean | no | Include sponsored ad results (default: dropped) |
| include_suggested | boolean | no | Include 'people also searched for' suggestions (default: dropped) |
Fetch Amazon product detail from a full product URL (the marketplace - com|co.uk|de|fr|es|it - is read from the URL host; pass the url field from a glim_amazon_search result, or any /dp/<ASIN> page URL). Returns title, buybox price (gross + VAT-excluded net), stock, delivery estimate, rating, top reviews, and an 'other sellers' summary (count + floor price). Text mode (default) returns a compact v
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ref | string | yes | Full Amazon product URL - pass the url from a glim_amazon_search result, or any /dp/<ASIN> product page URL. The URL carries the marketplace (amazon.de, amazon.co.uk, ...), so no separate region is |
| format | string | no | Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': the same product as machine-readable JSON, plus the fields text omits: the full offers[] list (text summarizes it) |
Fetch a YouTube video transcript from a video URL or 11-char id. The transcript is cleaned server-side: deduplicated, tags/HTML stripped, with coarse [m:ss] timestamps - roughly a tenth the size of the raw captions. Default format='text' returns it inline (when it fits ~40K chars / ~10K tokens) so a single call gives you the text directly; long-form videos fall back to a download_url note. Pass fo
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ref | string | yes | YouTube video URL or 11-char video id (e.g. https://youtu.be/dQw4w9WgXcQ, https://www.youtube.com/watch?v=dQw4w9WgXcQ, or dQw4w9WgXcQ) |
| language_code | string | no | ISO 639-1 language code (e.g. 'en', 'de', 'fr') |
| origin | string | no | 'uploader_provided' for human captions (default), 'auto_generated' for YouTube auto-captions. |
| format | string | no | Output format. 'text' (default): the cleaned transcript inline as plain text (omitted with a download_url note when it exceeds the ~40K-char inline cap). 'json': the same cleaned transcript plus trans |
Detect AI-generated text. Scores any text for AI-authorship likelihood and returns an overall verdict (AI / human / mixed) with confidence, the AI/human/AI-assisted fractions, and a segment-by-segment breakdown showing exactly which parts read as AI-written - including per-segment humanizer flags (AI output run through paraphrasing/'humanizer' tools). Use it to verify whether content (comments, ar
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | Text to analyze, plain text, 50+ characters, max 20,000. Detection reliability improves with length; very short texts return lower-confidence verdicts. |
| format | string | no | 'text' (default): compact human-readable report. 'json': structured data incl. per-segment text, scores, and humanizer flags. |
Search Telegram: discovers public channels by name/topic (directory lookup) and finds indexed public post/channel pages (semantic web index scoped to t.me). Telegram has no global full-text search, so treat results as discovery: find the right channel here, then use glim_telegram_get(ref=<handle>) for its live posts or glim_telegram_get(ref, query=...) to search within that channel's full history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Search query (topic, channel name, keyword) |
| kind | string | no | 'channels': channel directory lookup. 'posts': indexed t.me post pages. 'all' (default): both. |
| format | string | no | Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing. |
Fetch a public Telegram channel or post - no account or API key involved. Channel refs (@handle, handle, t.me URL) return channel info + recent posts newest-first with views, reactions, media, polls, and link previews; pass query to search within the channel's full history, and page older posts with before=<next_cursor>. Post refs (t.me/<channel>/<id>) return that post plus its most recent discuss
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ref | string | yes | Public channel (@handle, handle, or t.me/<channel> URL) or post (t.me/<channel>/<id> or '<channel>/<id>') |
| query | string | no | Search within the channel's full history (channel refs only) |
| before | string | no | Return posts older than this message id (from next_cursor) |
| after | string | no | Return posts newer than this message id |
| limit | integer | no | Max posts for channel refs (1-100) |
| include_comments | boolean | no | Post refs: include discussion comments (Telegram serves a small window of the most recent; walk older ones via comment=<oldest returned id>) |
| comment | string | no | Post refs: center the comment window on this comment id |
| format | string | no | Output format. 'text' (default): compact human-readable view, fewer tokens. 'json': full structured data for machine parsing. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install glim.sh or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish glim.sh can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.