# Anweshna Risk Screening (remote · anweshna.com)

Screen M&A deal documents for red flags across 15 risk categories; findings checked against source.

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

## Components

- remote · `anweshna.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-anweshna-risk-screening/anweshna.md), [page](https://verifymcp.io/servers/com-anweshna-risk-screening/anweshna)

## Channel facts

- Endpoint: `https://anweshna.com/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 605 tokens (~151/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Anweshna Risk Screening MCP server?

Anweshna Risk Screening is a hosted endpoint at https://anweshna.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-anweshna-risk-screening 'https://anweshna.com/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-anweshna-risk-screening": {
      "url": "https://anweshna.com/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-anweshna-risk-screening": {
      "type": "http",
      "url": "https://anweshna.com/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-anweshna-risk-screening]
url = "https://anweshna.com/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-anweshna-risk-screening": {
      "type": "remote",
      "url": "https://anweshna.com/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-anweshna-risk-screening --url 'https://anweshna.com/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-anweshna-risk-screening:
    url: "https://anweshna.com/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "com-anweshna-risk-screening": {
      "Transport": "http",
      "Url": "https://anweshna.com/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-anweshna-risk-screening -t streamable-http -u 'https://anweshna.com/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "com-anweshna-risk-screening": {
      "type": "http",
      "url": "https://anweshna.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-11-05 (score 69, +1)

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

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

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

### 2026-10-31 (score 67, +1)

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

### 2026-10-29 (score 66, +1)

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

### 2026-10-27 (score 65, +1)

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

### 2026-10-25 (score 64, +1)

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

### 2026-10-23 (score 63, +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-10-21 (score 62, +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.

## MCP tools (4)

### `screen_document` (~192 tokens)

Upload a deal document and score it for risk across 15 categories. Returns the overall score, rating, whether the deal is flagged as blocked, and per-category findings. Provide the file either as 'content_base64' (PDF, DOCX, TXT or CSV) or as plain 'text'. The whole call must stay under 32 MB, and base64 adds about a third, so the document itself should be under roughly 24 MB — a larger one is rejected by the transport before this tool runs, which surfaces as a bare HTTP 413 rather than a normal tool error. Use the REST upload endpoint for anything bigger.

Input parameters:

- `content_base64`
- `deal_room_id`
- `document_type` (string)
- `engine`
- `filename`
- `force_precision` (boolean)
- `industry`
- `text`
- `title` (string, required)

### `get_analysis` (~33 tokens)

Retrieve the stored risk analysis for a document already screened by this account. Read-only.

Input parameters:

- `document_id` (string, required)

### `bulk_screen` (~268 tokens)

Upload up to 25 documents and screen them as one batch. Waits for text extraction, then starts scoring and returns job ids; poll get_bulk_status until the batch is finished. Each item is {title, content_base64 | text, filename?}. The 25-document limit is not the binding one for large files: the whole call must stay under 32 MB including base64 overhead, so send fewer, larger documents per batch rather than filling all 25 slots. Exceeding it is a bare HTTP 413 from the transport, before this tool runs. To RESUME a batch that was uploaded but not scored — this tool timed out waiting for extraction, or scoring failed to start — call it again with 'bulk_job_id' instead of 'documents'. That re-uses the existing upload and does NOT spend the account's quota a second time. If the batch is rejected because one or more documents are too large for the plan's scan engine, retry with force_precision=true to scan those documents truncated to the recall window (coverage beyond it is excluded).

Input parameters:

- `bulk_job_id`
- `deal_room_id`
- `document_type` (string)
- `documents`
- `engine`
- `force_precision` (boolean)
- `industry`

### `get_bulk_status` (~47 tokens)

Check progress of a batch started by bulk_screen. Pass the upload_job_id, the analyze_job_id, or both.

Input parameters:

- `analyze_job_id`
- `upload_job_id`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-anweshna-risk-screening/anweshna#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 68
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 65
- 2026-10-27: 65
- 2026-10-26: 64
- 2026-10-25: 64
- 2026-10-24: 63
- 2026-10-23: 63
- 2026-10-22: 62
- 2026-10-21: 62
- 2026-10-20: 61
- 2026-10-19: 61

## Common questions

### What is the Anweshna Risk Screening MCP server?

Anweshna Risk Screening is an MCP server listed in the public MCP registry as com.anweshna/risk-screening. Screen M&A deal documents for red flags across 15 risk categories; findings checked against source. This page covers its hosted endpoint (https://anweshna.com/mcp/).

### Is the Anweshna Risk Screening MCP server safe to use?

Anweshna Risk Screening 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 Anweshna Risk Screening MCP server expose?

Anweshna Risk Screening exposes 4 tools: screen_document, get_analysis, bulk_screen, get_bulk_status. Their descriptions and schemas cost roughly 540 tokens of context every time the server is loaded.

### Does the Anweshna Risk Screening MCP server require authentication?

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

### Is the Anweshna Risk Screening MCP server still maintained?

Anweshna Risk Screening 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://anweshna.com/mcp/
- Authorisation metadata: https://anweshna.com/.well-known/oauth-protected-resource/mcp
- Website: https://anweshna.com/integrations/
- Changelog RSS feed: https://verifymcp.io/servers/com-anweshna-risk-screening/anweshna.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-anweshna-risk-screening/anweshna.json
- HTML version of this page: https://verifymcp.io/servers/com-anweshna-risk-screening/anweshna