Skip to content

Anweshna Risk Screening MCP server

com.anweshna/risk-screeninganweshna.comstreamable-httpv1.0.0Scanned

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

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Anweshna Risk Screening MCP server can do

The Anweshna Risk Screening MCP server is published by anweshna.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: screen_document and bulk_screen), but cannot delete data. 2 tools only read.

1 tool reads private data (get_analysis).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • bulk_screenUpload up to 25 documents and screen them as one batch.No findings

    Why it is in this group

    • The description's first verb is "upload": a word for a change.
    Description, as the server wrote it
    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).
  • screen_documentUpload a deal document and score it for risk across 15 categories.No findings

    Why it is in this group

    • The description's first verb is "upload": a word for a change.
    Description, as the server wrote it
    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.
Only reads 2Show 2 read-only tools
  • get_analysisRetrieve the stored risk analysis for a document already screened by this account.Reads private dataNo findings

    Why it is in this group

    • The name "get_analysis" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "retrieve" and "document": it reads documents.
    Description, as the server wrote it
    Retrieve the stored risk analysis for a document already screened by this account. Read-only.
  • get_bulk_statusCheck progress of a batch started by bulk_screen.No findings

    Why it is in this group

    • The name "get_bulk_status" says "get": a word for reading.
    Description, as the server wrote it
    Check progress of a batch started by bulk_screen. Pass the upload_job_id, the analyze_job_id, or both.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:34 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://anweshna.com/mcp/: tools/list returned 4 tools to an anonymous client, including screen_document (write), bulk_screen (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http risk-screening https://anweshna.com/mcp/ --header 'X-API-Key: <your-x-api-key>'
claude mcp add --transport http risk-screening https://anweshna.com/mcp/ --header 'X-API-Key: <your-x-api-key>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__risk-screening__get_analysis",
      "mcp__risk-screening__get_bulk_status"
    ],
    "ask": [
      "mcp__risk-screening__screen_document",
      "mcp__risk-screening__bulk_screen"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as risk-screening. Review it before you use it.

Capability tags behind 1 rule
  • mcp__risk-screening__get_analysis private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.anweshna/risk-screening/verify?hash=8b97268e2cfdba398960c7b8ea6ab82499a0729e6957aadd323e91c581b47fba" | jq -e '.changed == false'

Pinned hash 8b97268e2cfd, from Nov 12, 2026, 15:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.anweshna/risk-screening/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.anweshna/risk-screening
[![Anlyon Radar](https://radar.anlyon.com/badge/com.anweshna/risk-screening.svg)](https://radar.anlyon.com/servers/com.anweshna/risk-screening)

Source: MCP Registry. Synced Oct 21, 2026, 17:49 UTC.

Anweshna Risk Screening MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Anweshna Risk Screening MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Anweshna Risk Screening MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Anweshna Risk Screening MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Anweshna Risk Screening MCP server have?

4 tools: 2 write, 2 read. screen_document, bulk_screen, get_analysis and get_bulk_status.

Does the Anweshna Risk Screening MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Anweshna Risk Screening MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Anweshna Risk Screening MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.