# getresearch: the Data Research door (remote · mcp.getresearch.ai)

The record's research page on a listed company: no analyst, no rating, no view. Signed, receipted.

- Trust score: 70/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.getresearch.ai`: 70/100 (this document), [markdown](https://verifymcp.io/servers/allooloo-getresearch/mcp.md), [page](https://verifymcp.io/servers/allooloo-getresearch/mcp)

## Channel facts

- Endpoint: `https://mcp.getresearch.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## 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-11-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 696 tokens (~232/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 getresearch: the Data Research door MCP server?

getresearch: the Data Research door is a hosted endpoint at https://mcp.getresearch.ai/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 allooloo-getresearch 'https://mcp.getresearch.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "allooloo-getresearch": {
      "url": "https://mcp.getresearch.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "allooloo-getresearch": {
      "type": "http",
      "url": "https://mcp.getresearch.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.allooloo-getresearch]
url = "https://mcp.getresearch.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "allooloo-getresearch": {
      "type": "remote",
      "url": "https://mcp.getresearch.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add allooloo-getresearch --url 'https://mcp.getresearch.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  allooloo-getresearch:
    url: "https://mcp.getresearch.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "allooloo-getresearch": {
      "Transport": "http",
      "Url": "https://mcp.getresearch.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add allooloo-getresearch -t streamable-http -u 'https://mcp.getresearch.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "allooloo-getresearch": {
      "type": "http",
      "url": "https://mcp.getresearch.ai/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-11-21 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 66)

First indexed and scored.

## MCP tools (3)

### `get_research` (~259 tokens)

Get the research page of an issuer

The page is the record's research on the issuer — no analyst, no rating, no view. get_research is Data Research: one research page per listed company on the record, written from the signed record — identity and listing, the disclosure read (filings in the trailing twelve months, cadence, latency against the issuer's exchange and sector), auditor, events and halts, orderability, coverage, open research, licensed (none loaded), as-of depth and sources — with its as-of date and its receipt. Input: ticker with exchange, or ISIN, or LEI. Output: the page (sections and Markdown), its numbers with the source page and read date of every value, its as-of date, the signature and the RCO receipt. Typed errors: unknown_issuer, ambiguous, no_page, invalid_request. Page: https://getresearch.ai/

Input parameters:

- `exchange` (string): Exchange for the ticker (NASDAQ, NYSE, LSE, TSX, …).
- `isin` (string): ISIN (12 characters).
- `lei` (string): LEI (20 characters).
- `ticker` (string): Ticker (AAPL), with exchange in the exchange argument or as NASDAQ:AAPL.

### `resolve_issuer` (~109 tokens)

Resolve issuer

Find a listed company by ticker, ISIN or LEI: the apex names the owning node and forwards to that node's regional door for the record summary.

Input parameters:

- `identifier` (string, required): Ticker with or without exchange (SHOP, TSX:SHOP, SHEL.L, BHP.AX, D05.SI, NESN.SW, SAP.DE, 7203.T, 005930.KS), ISIN, LEI, an exact legal name or a sourced alias.

### `list_nodes` (~33 tokens)

List market nodes

Every market node on the roster (nodes.json, region on each), which are live, their regional doors and Agent Cards.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/allooloo-getresearch/mcp#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 68
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 66
- 2026-11-12: 66

## Common questions

### What is the getresearch: the Data Research door MCP server?

getresearch: the Data Research door is an MCP server listed in the public MCP registry as io.github.allooloo/getresearch. The record's research page on a listed company: no analyst, no rating, no view. Signed, receipted. This page covers its hosted endpoint (https://mcp.getresearch.ai/mcp).

### Is the getresearch: the Data Research door MCP server safe to use?

getresearch: the Data Research door scores 70 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 getresearch: the Data Research door MCP server expose?

getresearch: the Data Research door exposes 3 tools: get_research, resolve_issuer, list_nodes. Their descriptions and schemas cost roughly 401 tokens of context every time the server is loaded.

### Does the getresearch: the Data Research door MCP server require authentication?

No. We connected to getresearch: the Data Research door without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the getresearch: the Data Research door MCP server still maintained?

getresearch: the Data Research door is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the getresearch: the Data Research door MCP server?

VerifyMCP ran 12 checks on getresearch: the Data Research door, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about getresearch: the Data Research door: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.getresearch.ai/mcp
- Repository: https://github.com/allooloo/cm-kg
- Website: https://getresearch.ai/
- Changelog RSS feed: https://verifymcp.io/servers/allooloo-getresearch/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/allooloo-getresearch/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/allooloo-getresearch/mcp.json
- HTML version of this page: https://verifymcp.io/servers/allooloo-getresearch/mcp
