mcpbeat Sign in

Sofya MCP Server

answering

Sofya is answering right now. Last checked 9 min ago. It exposes 4 tools.

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

Uptime history 47 days of history · worst day 97%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
452 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 5

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 27 August 2026. No other catalogue keeps this.

2 Sep a tool description was rewritten search
27 Aug 4 tool descriptions were rewritten extract, fetch, research and 1 more

Nothing serious here today

Today is the operative word: we check Sofya every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add sofya --transport http https://sofya.co/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sofya": {
      "url": "https://sofya.co/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.sofya]
url = "https://sofya.co/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sofya": {
      "url": "https://sofya.co/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "sofya": {
      "url": "https://sofya.co/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

extract
extract
Fetch a webpage and extract specific information using AI. Use this when you need structured data from a page (e.g. pricing, specs, contact info) rather than the raw content. 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")
fetch
fetch
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. Returns null for non-HTML content (PDF, DOCX, etc.). 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)
research
research
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)
search
search
Search the web for current information on any topic. Returns extracted page content, not just snippets. Best for factual lookups, specific questions, or when you need a list of sources. For open-ended questions that need synthesis across many sources, use the research tool instead. For news queries (current events, breaking news, politics, world events), set topic="news" to search news sources specifically. This returns recent articles with publication dates. Set include_answer=true to get an AI-synthesized answer alongside results (adds 10 credits). This is the sweet spot for most agent tasks, e.g. basic + include_answer = 12 credits, much cheaper than a full 50-credit research call. Returns: query, answer (if requested), results (array of {title, url, content, description, fetched, published_date}), search_depth, topic, elapsed_ms, credits_used, credits_remaining, altered_query, relaxed_query (set when the query matched nothing and was retried once with its site: operator, else its quotes, removed - the results answer that looser query). Args: query: The search query search_depth: "basic" (default) for extracted page content (2 credits), "snippets" for SERP snippets only without page fetching (1 credit) max_results: Number of results (default 10, max 20) include_answer: Generate an AI answer that synthesizes the search results (adds 10 credits) include_domains: Only include results from these domains (max 10) exclude_domains: Exclude results from these domains (max 10) topic: "general" for web search, "news" for news articles. use "news" for current events, breaking news, politics, or any time-sensitive query freshness: Filter by recency - "day", "week", "month", "year", or "YYYY-MM-DD:YYYY-MM-DD"

Endpoints

URLTransportStateLatencyChecked
https://sofya.co/mcp streamable-http answering 436 ms 9 min ago

Alternatives to Sofya

same job, measured the same way
Andi Search
by andiai

Real-time web search and page fetch for AI agents from Andi's own index. LLM-ready markdown output.

answering
Linkup
by mcparmory

Search the web and fetch pages with sourced results, optimized for AI agents

223 installs/wk local only
Web Search
by hec-ovi

Keyless multi-engine web search, fetch, and clean-Markdown read for AI agents. No API keys.

198 installs/wk local only
Search
by neurobird

Web search for AI agents. Ranked results with page passages already extracted, plus URL to markdown.

2 tools answering
Web Research MCP
by csoai-org

AI-powered web research MCP server for agents. Supports web search, browse page, extract...

96 installs/wk local only
Agentsearch MCP
by isaiahdupree

LLM-ready web search + instant answers + URL-to-clean-text fetch for agents and RAG.

3 tools answering
SearchPipe
by searchpipe

Real-time web search for AI agents: ranked results, source URLs, and optional AI answers.

1 tools answering
Nimrod Research
by orchis

Web research for agents: quality-scored Google search, webpage extraction, and deep research.

answering

Sofya — questions

Answers built from our own checks of this server.

What can Sofya do?
It exposes 4 tools, read directly from the server on our last check. Among them: extract, fetch, research, search. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Sofya working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 452 ms. The bar chart above shows every period we have measured.
How do I connect Sofya?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Sofya need an API key?
No. Sofya completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Sofya?
It answers our handshake in 452 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.