Skip to main content
Glama

Server Details

Web search, fetch, extract, and research for AI agents. Markdown output + AI-synthesized answers.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
99.9% over 60 days
Last Tested
Transport
Streamable HTTP · MCP 2025-03-26
URL
Repository
sofya-co/sofya-mcp
GitHub Stars
2
Server Listing
sofya-mcp

TDQS

A4.7/5.0

Scored across 4 tools

Disambiguation4/5

Search, research, fetch, and extract each have a distinct primary role, and the descriptions explicitly call out when to use one over another. The only mild ambiguity is between fetch and extract, since both operate on URLs and return page-derived content, but their different outputs (full markdown vs. AI-extracted structured data) are clearly explained.

Naming Consistency5/5

All four tool names are single lowercase verbs that match their function directly: search, research, fetch, and extract. The pattern is completely consistent and predictable, with no mixed conventions or vague filler names.

Tool Count5/5

Four tools is a well-scoped size for a web research server. Each tool covers a distinct operation—discovery, deep synthesis, targeted fetching, and structured extraction—so none feels redundant or missing.

Completeness5/5

The tool set covers the full research lifecycle: search for sources, fetch specific URLs, extract structured data from a page, and synthesize an overall report. It includes useful parameters like freshness, domain filtering, and raw HTML access, leaving no obvious dead ends for typical web research workflows.

Available Tools

4 tools
extractInspect

Fetch a webpage and extract specific information using AI. Use this when you need one specific answer from a page (e.g. a price, a spec, contact info) rather than its full content. The answer comes back as text, not JSON. Costs 10 credits.

If the page has no usable text (empty or JavaScript-rendered body), the model is NOT called: content comes back empty and usage.low_content is true, rather than a fabricated answer. Gate on usage.low_content (or usage.content_chars) to detect pages you cannot ground on.

Returns: content (the extracted text), url, credits_used, credits_remaining, usage (input_tokens, output_tokens, content_chars, low_content).

Args: url: The URL to extract from prompt: What information to extract (e.g. "list all pricing tiers with features" or "extract the author name and publication date")

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYes
promptYes
fetchInspect

Fetch one or more URLs and return their content as clean markdown. Use this to read articles, documentation, blog posts, or any page where you need the complete text, not just a snippet from search. Also supports PDF, DOCX, and other document formats. Costs 2 credits per URL. Max 10 URLs per request. Failed URLs are not charged.

Set include_raw_html=true to also get the raw HTML source in each result. Useful for inspecting embedded URLs, data attributes, iframes, or script tags that are stripped during markdown conversion. May be null for non-HTML content (PDF, DOCX, etc.) and for some sites. Same cost.

Returns: results (array of {title, url, content, raw_html, published_time, success, error}), credits_used, credits_remaining.

Args: urls: List of URLs to fetch (max 10) include_raw_html: Include raw HTML source in each result (default false)

ParametersJSON Schema
NameRequiredDescriptionDefault
urlsYes
include_raw_htmlNo
researchInspect

Perform comprehensive research on a topic. Decomposes your query into sub-queries, searches and reads multiple sources in parallel, then synthesizes a structured report with citations. Best for open-ended or comparative questions that need coverage from many angles. For simple factual lookups, use search instead (optionally with include_answer=true for cheap synthesis). Costs 50 credits.

Returns: query, report (structured markdown with citations), sources (array of {title, url, fetched}), sub_queries (the decomposed queries), credits_used, credits_remaining, usage (token counts).

Args: query: The research question or topic topic: "general" (default) or "news" (prioritize recent news articles) freshness: Filter by recency - "day", "week", "month", "year", or "YYYY-MM-DD:YYYY-MM-DD" max_sources: Maximum number of sources to use, 5-30 (default 20)

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes
topicNogeneral
freshnessNo
max_sourcesNo

Tool Schema Changelog

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

  1. 2 tool updates
    • Changedresearch1 field changed
      • addedInput schema / properties / topic / enum
        Added value: +[
        +  "general",
        +  "news"
        +]
    • Changedsearch2 fields changed
      • addedInput schema / properties / search_depth / enum
        Added value: +[
        +  "snippets",
        +  "basic"
        +]
      • addedInput schema / properties / topic / enum
        Added value: +[
        +  "general",
        +  "news"
        +]
  2. 4 tool updates
    • First observedextract
    • First observedfetch
    • First observedresearch
    • First observedsearch

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.