# Bob Research Tools (remote · bob.assimilatethis.com)

Paid web research, news, prediction-market evidence, company briefs and fact-checks (x402 USDC)

- Trust score: 66/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `bob.assimilatethis.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-assimilatethis-bob-research-tools/bob.md), [page](https://verifymcp.io/servers/com-assimilatethis-bob-research-tools/bob)

## Channel facts

- Endpoint: `https://bob.assimilatethis.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.6`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1423 tokens (~177/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability check failed: schema churn in the 15 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 8 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Bob Research Tools MCP server?

Bob Research Tools is a hosted endpoint at https://bob.assimilatethis.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-assimilatethis-bob-research-tools 'https://bob.assimilatethis.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-assimilatethis-bob-research-tools": {
      "url": "https://bob.assimilatethis.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-assimilatethis-bob-research-tools": {
      "type": "http",
      "url": "https://bob.assimilatethis.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-assimilatethis-bob-research-tools]
url = "https://bob.assimilatethis.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-assimilatethis-bob-research-tools": {
      "type": "remote",
      "url": "https://bob.assimilatethis.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-assimilatethis-bob-research-tools --url 'https://bob.assimilatethis.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-assimilatethis-bob-research-tools:
    url: "https://bob.assimilatethis.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-assimilatethis-bob-research-tools": {
      "Transport": "http",
      "Url": "https://bob.assimilatethis.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-assimilatethis-bob-research-tools -t streamable-http -u 'https://bob.assimilatethis.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-assimilatethis-bob-research-tools": {
      "type": "http",
      "url": "https://bob.assimilatethis.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-10 (score 66, −1)

- [security regression] Stability: 0.03 → fail
- [functional regression] Schema quality: 156 → 177

### 2026-10-04 (score 67, +11)

- [security improvement] Authorization: unverified → partial
- [security] Tool “bob_extract” rewrote its description, which is the text the model reads
- [security] Tool “bob_factcheck” rewrote its description, which is the text the model reads
- [security] Tool “bob_research” rewrote its description, which is the text the model reads
- [security] Tool “bob_summarize” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 0% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “bob_extract” now declares an output schema
- [functional improvement] Tool “bob_factcheck” now declares an output schema
- [functional improvement] Tool “bob_research” now declares an output schema
- [functional improvement] Tool “bob_summarize” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: good → excellent
- [functional] New tool “bob_search”
- [cosmetic] “bob_extract” reworded the description of “url”
- [cosmetic] “bob_factcheck” reworded the description of “claim”
- [cosmetic] “bob_research” reworded the description of “q”
- [cosmetic] “bob_summarize” reworded the description of “url”

### 2026-10-03 (score 56)

First indexed and scored.

## MCP tools (8)

### `research.answer` (~169 tokens)

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.

Input parameters:

- `q` (string, required): The research question to answer, 1 to 500 characters.

Output parameters:

- `answer` (string): Short answer synthesized from the live web.
- `sources` (array): Source URLs the answer rests on.

### `research.factcheck` (~129 tokens)

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.

Input parameters:

- `claim` (string, required): The factual claim to check, 1 to 500 characters, written as a statement.

Output parameters:

- `explanation` (string): One or two sentences on why.
- `sources` (array): Source URLs behind the verdict.
- `verdict` (string): How the live web treats the claim.

### `page.summarize` (~147 tokens)

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.

Input parameters:

- `url` (string, required): Public http or https address of the page to summarize; private or local addresses are refused.

Output parameters:

- `key_points` (array): Key points from the page.
- `summary` (string): About 80 words.
- `url` (string): The page that was summarized.

### `web.search` (~188 tokens)

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.

Input parameters:

- `n` (integer): How many results to return, 1 to 10. Default 5.
- `q` (string, required): The web search query, 1 to 500 characters.
- `since`: Optional. Only results published on or after this date, written YYYY-MM-DD, e.g. 2026-09-01.
- `until`: Optional. Only results published on or before this date, written YYYY-MM-DD.

Output parameters:

- `published_between` (array): The since/until dates applied, if any.
- `query` (string): The query that was searched.
- `results` (array): Ranked results.

### `page.extract` (~168 tokens)

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.

Input parameters:

- `url` (string, required): Public http or https address of the page to extract; private or local addresses are refused.

Output parameters:

- `markdown` (string): Main content of the page as markdown, up to 8,000 characters.
- `truncated` (boolean): True if the page was longer than the cap.
- `url` (string): The page that was read.

### `web.news` (~194 tokens)

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.

Input parameters:

- `days` (integer): How many days back to look, 1 to 30. Default 7.
- `q` (string, required): The topic, person, company or event to get recent news on, 1 to 500 characters.

Output parameters:

- `developments` (array): Up to 5 dated developments, newest first.
- `query` (string): The topic that was searched.
- `summary` (string): About 50 words on what happened.
- `window_days` (integer): How many days back were searched.

### `research.market` (~177 tokens)

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.

Input parameters:

- `question` (string, required): The prediction-market question to research, 1 to 500 characters, worded as the market words it.

Output parameters:

- `as_of` (string): The date the brief was written, YYYY-MM-DD.
- `evidence_against` (array): Up to 3 facts that support No.
- `evidence_for` (array): Up to 3 facts that support Yes.
- `key_dates` (array): Known or upcoming dates, each 'YYYY-MM-DD: what happens'.
- `note` (string)
- `question` (string)
- `resolution_notes` (string): What usually decides resolution and what is ambiguous.
- `sources` (array): Source URLs.
- `summary` (string): About 50 words of evidence, not a forecast.

### `research.company` (~165 tokens)

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.

Input parameters:

- `company` (string, required): A company name or website, 1 to 500 characters, e.g. Stripe or stripe.com.

Output parameters:

- `company` (string)
- `facts` (array): Up to 5 short facts, only if the sources state them.
- `recent` (array): Up to 3 recent developments.
- `sources` (array): Source URLs.
- `summary` (string): About 60 words.
- `what_it_does` (string): One sentence on the business.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-assimilatethis-bob-research-tools/bob#diagnostics

## Score history

- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 66
- 2026-10-15: 66
- 2026-10-14: 66
- 2026-10-13: 66
- 2026-10-12: 66
- 2026-10-10: 66
- 2026-10-04: 67
- 2026-10-03: 56

## Common questions

### What is the Bob Research Tools MCP server?

Bob Research Tools is an MCP server listed in the public MCP registry as com.assimilatethis.bob/research-tools. Paid web research, news, prediction-market evidence, company briefs and fact-checks (x402 USDC). This page covers its hosted endpoint (https://bob.assimilatethis.com/mcp).

### Is the Bob Research Tools MCP server safe to use?

Bob Research Tools scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Bob Research Tools MCP server expose?

Bob Research Tools exposes 8 tools: research.answer, research.factcheck, page.summarize, web.search, page.extract, and 3 more. Their descriptions and schemas cost roughly 1,337 tokens of context every time the server is loaded.

### Does the Bob Research Tools MCP server require authentication?

No. We connected to Bob Research Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Bob Research Tools MCP server still maintained?

Bob Research Tools is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://bob.assimilatethis.com/mcp
- Website: https://bob.assimilatethis.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-assimilatethis-bob-research-tools/bob.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-assimilatethis-bob-research-tools/bob.json
- HTML version of this page: https://verifymcp.io/servers/com-assimilatethis-bob-research-tools/bob