# Knowra (remote · mcp.knowra.app)

Search arXiv papers and read Scout reports with methods, evidence and verification points.

- Trust score: 69/100 (medium)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.knowra.app`: 69/100 (this document), [markdown](https://verifymcp.io/servers/app-knowra-knowra/mcp.md), [page](https://verifymcp.io/servers/app-knowra-knowra/mcp)

## Channel facts

- Endpoint: `https://mcp.knowra.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.8.16`

## 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-05.

- **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**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 658 tokens (~219/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**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% 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 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 current MCP spec version (2026-07-28).

## Install

### How do I install the Knowra MCP server?

Knowra is a hosted endpoint at https://mcp.knowra.app/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 app-knowra-knowra 'https://mcp.knowra.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-knowra-knowra": {
      "url": "https://mcp.knowra.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-knowra-knowra": {
      "type": "http",
      "url": "https://mcp.knowra.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-knowra-knowra]
url = "https://mcp.knowra.app/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add app-knowra-knowra --url 'https://mcp.knowra.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-knowra-knowra:
    url: "https://mcp.knowra.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-knowra-knowra": {
      "Transport": "http",
      "Url": "https://mcp.knowra.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-knowra-knowra -t streamable-http -u 'https://mcp.knowra.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-knowra-knowra": {
      "type": "http",
      "url": "https://mcp.knowra.app/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-05 (score 69, −4)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-11-04 (score 73, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HTTPS: pass → unverified
- [security regression] Stability: 0.30 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional] First check of Schema quality: unverified
- [functional] Server version: 0.8.15 → 0.8.16

### 2026-11-03 (score 73, +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-01 (score 72, +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-10-31 (score 71, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.8.14 → 0.8.15

### 2026-10-30 (score 71, +1)

- [functional] Server version: 0.8.13 → 0.8.14
- [functional] Server version: 0.8.12 → 0.8.13

### 2026-10-29 (score 70, 0)

- [functional] Server version: 0.8.11 → 0.8.12

### 2026-10-28 (score 70, +1)

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

## MCP tools (3)

### `search_papers` (~287 tokens)

Search papers

Discover indexed arXiv papers using titles, authors and abstracts to assess relevance.
Prefer an English research topic or question, preserving important entities and phrases.
For broad questions, consider distinct research dimensions and query each as useful.
Independent queries can run concurrently; 5-10 concurrent requests are recommended
for larger batches. Results can complement findings from other research tools and
sources for broader coverage.
scout_available indicates whether deeper paper-based analysis can be requested
with get_scout; choose further reading according to the evidence needed.
Use from/to as YYYY-MM-DD UTC dates with both days included.
Provide both or neither; each dated query covers at most one calendar month,
with dates available from 2025-08-01 onward. Omit both for all indexed dates.
For timeouts, wait at least retry_after_seconds when supplied before retrying.

Input parameters:

- `from`: First included UTC date, YYYY-MM-DD. The database supports 2025-08-01 onward. Provide both from and to, or omit both to search all supported content.
- `limit` (integer)
- `query` (string, required): Prefer English natural-language research topics or questions; keep important entities and technical phrases.
- `to`: Last included UTC date, YYYY-MM-DD; the entire day is included. Provide both from and to. At most one calendar month after from; same-day queries valid.

Output parameters:

- `papers` (array)
- `query_hint`
- `returned` (integer)

### `get_scout` (~145 tokens)

Get Scout report

Read a structured paper-based analysis of key signals, methodology, evidence,
experimental conditions and verification points, with author-stated limitations
where available. Use it when these details help assess a candidate, compare findings,
or understand the context of a claim beyond the abstract.
Search results mark supported papers with scout_available=true.
Returns text including figure captions and descriptions. If needed, consult the
original paper through source_url for further verification.
Independent papers can be requested concurrently; up to five concurrent requests
are recommended per batch. For a timeout, wait as indicated and retry the same paper.

Input parameters:

- `paper_id` (string, required): Paper identifier from search results; scout_available indicates Scout availability.

Output parameters:

- `paper_id` (string)
- `scout` (string): Paper-based Scout analysis with evidence, verification points and figure descriptions.
- `source_url` (string)

### `get_usage` (~40 tokens)

Get usage

Check Scout quota, usage, remaining allowance and reset time, along with plan and
entitlement details. Entitlement expiry and quota reset time describe different events.

Output parameters:

- `billing_owner`
- `entitlement_expires_at`
- `entitlement_source` (string)
- `hard_limit` (boolean)
- `limit` (integer)
- `plan_tier` (string)
- `remaining` (integer)
- `resets_at` (string)
- `subscription_expired` (boolean)
- `used` (integer)
- `user_id` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 69
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 68

## Common questions

### What is the Knowra MCP server?

Knowra is an MCP server listed in the public MCP registry as app.knowra/knowra. Search arXiv papers and read Scout reports with methods, evidence and verification points. This page covers its hosted endpoint (https://mcp.knowra.app/mcp).

### Is the Knowra MCP server safe to use?

Knowra scores 69 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 Knowra MCP server expose?

Knowra exposes 3 tools: search_papers, get_scout, get_usage. Their descriptions and schemas cost roughly 472 tokens of context every time the server is loaded.

### Does the Knowra MCP server require authentication?

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

### Is the Knowra MCP server still maintained?

Knowra is still listed as active in the MCP registry. We last reached this channel on 5 November 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://mcp.knowra.app/mcp
- Website: https://knowra.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-knowra-knowra/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-knowra-knowra/mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-knowra-knowra/mcp