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。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。