Anweshna Risk Screening

com.anweshna由 anweshna.com 發布官方發布者v1.0.0更新於 Oct 24, 2026

按15個風險類別篩查併購交易檔案中的危險訊號;篩查結果會對照原始檔案進行核實。

AI 翻譯由 AI 模型根據下方的原文描述翻譯,可能有誤。

原文描述

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

已驗證Streamable HTTP可網頁執行

概覽

Anweshna Risk Screening 的託管 MCP 服務(anweshna.com),由 anweshna.com 發布;需要 API 金鑰;Streamable HTTP;4 個工具。

暫無 AI 概覽:以下資訊來自註冊中心條目和服務本身。

發布者
anweshna.com
端點
anweshna.com
最近檢查

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Anweshna Risk Screening,將其新增到工作區。
  2. 連接 X-API-Key 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/com.anweshna%2Frisk-screening/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "anweshna-risk-screening": {
      "type": "http",
      "url": "https://anweshna.com/mcp/",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

工具

4

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.

輸入參數texttitle必填enginefilenameindustrydeal_room_iddocument_typecontent_base64force_precision

get_analysis

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

輸入參數document_id必填

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).

輸入參數engineindustrydocumentsbulk_job_iddeal_room_iddocument_typeforce_precision

get_bulk_status

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

輸入參數upload_job_idanalyze_job_id

版本歷史

1
  1. v1.0.0最新Oct 19, 2026

評分

已滿足適用檢查項的 83%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分

    請宣告包含 README 的 GitHub 儲存庫,或在 OAuth 受保護資源後設資料中提供 resource_documentation。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。