mcpbeat Sign in

Anweshna Risk Screening MCP Server

answering

Anweshna Risk Screening is answering right now. Last checked 10 min ago. It exposes 4 tools.

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

Uptime history 15 days of history
15 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
497 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Anweshna Risk Screening every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add risk-screening --transport http https://anweshna.com/mcp/
Settings → Connectors → Add custom connector, then paste this address
https://anweshna.com/mcp/
~/.codex/config.toml
[mcp_servers.risk-screening]
url = "https://anweshna.com/mcp/"
.cursor/mcp.json
{
  "mcpServers": {
    "risk-screening": {
      "url": "https://anweshna.com/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "risk-screening": {
      "type": "http",
      "url": "https://anweshna.com/mcp/"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

bulk
bulk_screen
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).
get_bulk_status
Check progress of a batch started by bulk_screen. Pass the upload_job_id, the analyze_job_id, or both.
analysis
get_analysis
Retrieve the stored risk analysis for a document already screened by this account. Read-only.
screen
screen_document
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.

Endpoints

URLTransportStateLatencyChecked
https://anweshna.com/mcp/ streamable-http answering 510 ms 10 min ago

Alternatives to Anweshna Risk Screening

same job, measured the same way
SuperLocalMemory
by qualixar

Local-first memory for AI agents: recall with sources, answer checks, documents, mesh, governance.

2 500 installs/wk local only
FinalPeace
by finalpeace

State document requirements for all 50 US states, an after-a-loss checklist, and a planning gap chec

4 tools answering
V
vera.ink
by vera

Check documents against rules taken from the law itself. Every finding cites the exact clause.

7 tools answering
Document Integrity Validator
by ojaskord

AI reasoning checks any document against known international standards before your agent acts on it.

65 installs/wk 2 tools answering
Liminary
by liminary-api

Your AI's memory for what you actually know: recall across your documents, notes, and meetings

answering
PortMem
by portmem

Check AI-written drafts against your source documents, with the passage behind every verdict.

answering
Myco Brain
by thegoodguysla

Shared, source-backed memory for AI agents on your own Postgres, with an optional document engine.

83 installs/wk local only
Groundwork
by nickjlamb

Deployment-readiness checks for document-QA and extraction AI: grounding, extraction, CI gate.

50 installs/wk local only

Anweshna Risk Screening — questions

Answers built from our own checks of this server.

What can Anweshna Risk Screening do?
It exposes 4 tools, read directly from the server on our last check. Among them: bulk_screen, get_analysis, get_bulk_status, screen_document. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Anweshna Risk Screening working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 497 ms. The bar chart above shows every period we have measured.
How do I connect Anweshna Risk Screening?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Anweshna Risk Screening need an API key?
No. Anweshna Risk Screening completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Anweshna Risk Screening?
It answers our handshake in 497 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.