Bob Research Tools is answering right now. Last checked 14 min ago. It exposes 8 tools.
Paid web research, news, prediction-market evidence, company briefs and fact-checks (x402 USDC)
Uptime history
9 days of history · worst day 99%
9 days agonow
100.0%
Uptime 24h
91 of 91 checks
8
Tools
read from the server
539 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 42
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 5 October 2026. No other catalogue keeps this.
5 Oct
19 tools appeared
bob_company_brief, bob_market_research, bob_news and 16 more
5 Oct
16 tools disappeared
bob_company_brief, bob_extract, bob_factcheck and 13 more
5 Oct
7 tool descriptions were rewritten
bob_extract, bob_factcheck, bob_research and 4 more
Bob Research Tools missed one check this week
Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.
run in your terminal
claude mcp add research-tools --transport http https://bob.assimilatethis.com/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"research-tools": {
"url": "https://bob.assimilatethis.com/mcp"
}
}
}~/.codex/config.toml
[mcp_servers.research-tools]
url = "https://bob.assimilatethis.com/mcp".cursor/mcp.json
{
"mcpServers": {
"research-tools": {
"url": "https://bob.assimilatethis.com/mcp"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"research-tools": {
"url": "https://bob.assimilatethis.com/mcp"
}
}
}Available tools 8
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
research
research.answer
Answers one open research question from the live web in at most 80 words with up to 3 source URLs, returned as {answer, sources}, usually in 4 to 9 seconds. Use it for a synthesized answer; use web.search for raw links or research.factcheck to verify a claim. Name the people, places and dates the question depends on, and ask one question per call: several in one call get one blended answer. Read-only. Paid per call with x402, up to 60 calls a minute per client; a call that fails, times out or hits capacity is not charged. For several questions, make one call per question: calls are independent and can run in parallel.
research.company
Returns a short sourced brief on one company as {company, summary, what_it_does, facts, recent, sources}, usually in 5 to 8 seconds. Pass a website address such as stripe.com to avoid name clashes; a bare name resolves to the best-known company with that name and the summary says when the name is ambiguous. Facts such as founding year, location, size, funding or leadership appear only when the sources state them, and conflicting figures are reported as the most recent one with its date. Read-only. Paid per call with x402; if the company cannot be described in time the call fails and is not charged.
research.factcheck
Checks one factual claim against the live web and returns {verdict, explanation, sources}, where verdict is supported, contradicted or unclear, usually in 4 to 9 seconds. Write the claim as a plain statement such as 'The Eiffel Tower is in Berlin' and split a compound claim into separate calls. Use research.answer for open questions. For several claims, call once per claim. Read-only. Paid per call with x402; a failed call is not charged.
research.market
Builds an evidence brief for a prediction-market question (Kalshi, Polymarket or similar) from the live web: {question, as_of, summary, evidence_for, evidence_against, key_dates, resolution_notes, sources}, usually in 5 to 8 seconds. Pass the question as the market words it, including its date or threshold (for example 'by Dec 31, 2026' or 'above 4.5%'). It reports evidence and what decides resolution; it gives no probability, forecast or trading advice. Use research.answer for general questions. Read-only. Paid per call with x402; if it cannot answer in time the call fails and is not charged.
page
page.extract
Returns the main text of one public web page as clean markdown, unchanged and not summarized, up to 8,000 characters, as {url, markdown, truncated}, usually in 2 to 5 seconds. Pass the address of the specific page, not a site's home page; pages that need a login cannot be read, and longer pages are cut and flagged truncated. Use page.summarize for a short version. To read several pages, or to crawl a topic, get the addresses from web.search and call this once per address. Read-only. Paid per call with x402, up to 60 calls a minute per client; a failed call is not charged.
page.summarize
Condenses one public web page into an 80-word summary with up to 4 key points, returned as {url, summary, key_points}, usually in 3 to 6 seconds. The page is fetched live, so the summary reflects it now; pages behind a login or paywall may return little. Pass the address of the specific page, not a site's home page. Use page.extract for the page's own text. Read-only. Paid per call with x402; if the page cannot be read in time the call fails and is not charged.
web
web.news
Returns recent news on one topic, person, company or event as {query, window_days, summary, developments: [{headline, date, source}]}: a summary of about 50 words and up to 4 dated developments, newest first, usually in 3 to 7 seconds. A short topic or name works better than a full question; days sets the look-back from today (1 to 30, default 7), so a quiet topic needs a larger value. Use web.search for raw links. Read-only; only what the dated results support is returned. Paid per call with x402; if nothing recent is found the call fails and is not charged.
web.search
Runs a web search and returns ranked results as {query, results: [{title, url, snippet}]}. Use it for raw links to read yourself; use research.answer for a written answer. Plain phrases work as well as keywords; since and until (YYYY-MM-DD) limit results to a publish-date range, which suits recent news. Needs an x402 payment per call; if the search fails or finds nothing, you are not charged.
Tools removed
Tools this server used to expose. Anything built against them stopped working on the day they went.
bob_company_brief
removed 5 Oct 2026
bob_extract
removed 5 Oct 2026
bob_factcheck
removed 5 Oct 2026
bob_market_research
removed 5 Oct 2026
bob_news
removed 5 Oct 2026
bob_research
removed 5 Oct 2026
bob_search
removed 5 Oct 2026
bob_summarize
removed 5 Oct 2026
bob.page.extract
removed 5 Oct 2026
bob.page.summarize
removed 5 Oct 2026
bob.research.answer
removed 5 Oct 2026
bob.research.company
removed 5 Oct 2026
bob.research.factcheck
removed 5 Oct 2026
bob.research.market
removed 5 Oct 2026
bob.web.news
removed 5 Oct 2026
bob.web.search
removed 5 Oct 2026
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://bob.assimilatethis.com/mcp | streamable-http | answering | 536 ms | 14 min ago |
Alternatives to Bob Research Tools
same job, measured the same wayTollbooth
by huwhitememes
37 paid x402 MCP tools for OSINT, prediction markets, web intel, and agent security on Base USDC.
P
Paid Base Token Tools
by replit-paid-mcp-opportunity-lab-taylorboucher1
Base token facts and ERC-20 allowance checks. Per-call USDC on Base; x402 wallet required.
Texttostl
by texttostl
x402-paid tools: text to 3D-printable STL, web search, and search+read. USDC on Base.
Connskill Growth MCP
by conn-skill
Local market checks, rankings and keyword research as JSON, paid per call via x402 in USDC on Base.
Tanod
by tanod
Pay-per-call agent tools: PDF, OCR, translation, news search, prediction markets, web, chain reads.
Tools
by borisinc
Pay-per-call AI tools over x402: web research, summarization, structured extraction (USDC, Base).
Agent Decision & Evidence Tools (MCP + x402)
by patrickpi1312
40 MCP tools: multi-chain RPC, market and transaction decisions, AI, EU compliance and US imports
Agent Newsstand
by agentnewsstand
Market data and web intelligence for AI agents, paid per call in USDC on Base via x402.
Bob Research Tools — questions
Answers built from our own checks of this server.
What can Bob Research Tools do?
It exposes 8 tools, read directly from the server on our last check. Among them: page.extract, page.summarize, research.answer, research.company, research.factcheck, research.market and 2 more. 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 →
What is Bob Research Tools mostly used for?
Its tools cluster around research, web and page. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Bob Research Tools 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 539 ms. The bar chart above shows every period we have measured.
Did Bob Research Tools ever remove tools?
Yes. bob_company_brief, bob_extract, bob_factcheck, bob_market_research and 12 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Bob Research Tools?
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 Bob Research Tools need an API key?
No. Bob Research Tools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Bob Research Tools?
It answers our handshake in 539 ms on average, which is faster than 23% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.