原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

SentriSend Email Validation

✓ 服务方 · sentrisend.com

作者:sentrisend版本 0.1.0i★ 0i在云端运行官方网站 ↗
注册名称com.sentrisend/validation

安装方法

What it does

SentriSend checks email syntax, disposable domains and DNS/MX records; it never sends email.

  • Connects 在云端运行
  • Account or key Needs Authorization
  • Category 聊天与邮件

为什么排在这里

此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列

1. 在 Claude 连接器目录中否
2. 团队实测过否
3. 适合泰国用户否
4. 不计星标的使用量20/100热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0
5. 登记日期2026-11-16

用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。

质量: 基础检查通过 4/4 项(仅展示,不用于排序)

安装

选择你使用的 AI 应用,然后复制设置。

用一句话让 AI 帮你安装

请帮我安装 SentriSend Email Validation。按照 https://mcp.popnx.com/i/sentrisend-validation.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 4/4 项检查 · 你的提问会经过开发者的服务器(sentrisend.com) · ✓ 命令已检查 2026年11月17日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 5 分钟

需要 SentriSend Email Validation 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 注册并创建 SentriSend Email Validation 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    获取密钥的方法见下方开发者的 README

  2. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  3. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称SentriSend Email Validation
    Remote MCP server URL · 地址https://sentrisend.com/mcp

    在 Request headers 下添加这个名称和值

    Header 名称Authorization
    值Bearer <在这里粘贴你的密钥>

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  4. 在聊天中开启

    +ConnectorsSentriSend Email Validation

  5. 试一试

    用 SentriSend Email Validation 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 SentriSend Email Validation,或回答中出现 SentriSend Email Validation 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

ChatGPT 暂时无法连接 SentriSend Email Validation

SentriSend Email Validation 连接时需要你自己的密钥,但 OpenAI 帮助页面只说明了 OAuth 登录,没有我们能核实的填密钥方式

你可以改用这些方式

A · 使用能连接 SentriSend Email Validation 的应用

  • 需要 SentriSend Email Validation 的密钥(在开发者网站创建) · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
  • 需要 SentriSend Email Validation 的密钥(在开发者网站创建)
  • 需要 SentriSend Email Validation 的密钥(在开发者网站创建)
  • 需要 SentriSend Email Validation 的密钥(在开发者网站创建)

B · 聊天与邮件 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

可连接 Claude Code · 约 5 分钟

需要 SentriSend Email Validation 的密钥(在开发者网站创建)

  1. 注册并创建 SentriSend Email Validation 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    获取密钥的方法见下方开发者的 README

  2. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  3. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user validation https://sentrisend.com/mcp --header 'Authorization: Bearer your-value'

    按 Enter 前,把“your-value”改成你的密钥

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Claude Code 中输入 /mcp

    应能看到 SentriSend Email Validation 在列表中并显示已连接

  5. 试一试

    用 SentriSend Email Validation 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 SentriSend Email Validation,或回答中出现 SentriSend Email Validation 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 5 分钟

需要 SentriSend Email Validation 的密钥(在开发者网站创建)

  1. 注册并创建 SentriSend Email Validation 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    获取密钥的方法见下方开发者的 README

  2. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 SentriSend Email Validation 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 Cursor 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 SentriSend Email Validation 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 SentriSend Email Validation,或回答中出现 SentriSend Email Validation 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 5 分钟

需要 SentriSend Email Validation 的密钥(在开发者网站创建)

  1. 注册并创建 SentriSend Email Validation 的密钥

    打开开发者网站,注册账户并创建 API 密钥,下一步要用。价格和免费方案请看开发者网站。

    获取密钥的方法见下方开发者的 README

  2. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  3. 填写你的密钥

    在 SentriSend Email Validation 的设置中,Authorization 还是空的,填入你的密钥并保存

    只把密钥粘贴到应用的输入框里,不要粘贴到聊天中或发给任何人

  4. 在 VS Code 中以 Agent 模式打开 AI 聊天

  5. 试一试

    用 SentriSend Email Validation 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 SentriSend Email Validation,或回答中出现 SentriSend Email Validation 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://sentrisend.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 SentriSend Email Validation 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user validation https://sentrisend.com/mcp --header 'Authorization: Bearer your-value'

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "validation": {
      "url": "https://sentrisend.com/mcp",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "validation": {
      "type": "http",
      "url": "https://sentrisend.com/mcp",
      "headers": {
        "Authorization": "Bearer your-value"
      }
    }
  }
}

需要你填写的值

  • Authorization 机密 必填 HTTP header
    使用 Bearer 格式的 SentriSend API 密钥
    查看英文原文SentriSend API key using the Bearer format

说明为自动翻译,变量名保持原样;不确定时请查看原文。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ sentrisend.com
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.1.0
发布到注册中心i
2026年11月17日
代码最后更新i
2026年11月18日
最近检查
2026年11月17日
作者
sentrisend
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月17日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • validate_email

    Validate one email address with SentriSend's existing validation API. Checks syntax, disposable-domain status, and DNS/MX records; it does not check whether a specific mailbox exists. Uses the connected SentriSend API key and the same monthly request allowance as a direct validat

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 sentrisend.com 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • – 不适用

    有许可证

    不适用:由 sentrisend.com 的所有者自己运行的云端服务器,你不会运行仓库里的代码

  • ✓ 通过

    端点有响应

    在 334 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 1 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/sentrisend-validation.svg)](https://mcp.popnx.com/en/servers/sentrisend-validation)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“聊天与邮件”中的其他服务器比较i

  • 星标数多于此分类中其他 2024 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 2024 个服务器的 90% 更新
  • 基础检查结果等于或优于此分类中其他 2024 个服务器的 99%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

SentriSend Email Validation 安全吗?

它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

你需要填写:Authorization

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(0.1.0)于前天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

作者:anypost广泛使用↓ 5432/周★ 13945天前更新

电脑或云端✓ 服务方 · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

作者:infobip起步阶段★ 3613个月前更新

在云端运行✓ 服务方 · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

作者:w1ne起步阶段★ 3523天前更新

在云端运行✓ 服务方 · kernelcad.com
与相似项目对比
本项
SentriSend Email Validation
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
运行位置在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥是否否否否否
可在 Claude 中按 + 添加否否否否是否
基础检查4/45/54/44/44/44/4
许可证MITMITAGPL-3.0Apache-2.0MITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

SentriSend

Email validation, gated sending and a signup-protection hook for Supabase, as a simple HTTP API.

SentriSend checks an email address *before* you send to it or let it sign up: is the syntax valid, is the domain a known disposable provider, does the domain exist, and can it receive mail? It can also send the message for you behind sender-reputation controls and return a signed audit receipt.

What you can use it for:

  • Validate addresses in signup forms and before sending (POST /validate, or the npm package).
  • Block disposable and non-existent domains in Supabase Auth with a hosted "Before User Created" hook. No code to deploy: guide.
  • Send through a gateway that runs the same address checks, content and threat checks, rate limits and a sender-reputation circuit breaker before the message goes to your delivery provider (POST /send).

Links:

  • Website and free key: https://sentrisend.com
  • API base URL: https://sentrisend.com/api/v1
  • Built by Bench Tech Audio Ltd

This repository holds the public documentation and examples. The service itself is hosted; its source code is not published here.


What it checks

POST /validate runs these checks on one address:

CheckDetail
SyntaxThe address is a plain name@domain address of 3-254 characters. Quoted and internationalised address forms are not supported.
Disposable domainsMatched against a bundled list of about 134,100 disposable domains, including their subdomains.
Domain existsA live DNS lookup tells a non-existent domain apart from a domain with no mail records.
Can receive mailLooks for MX records. If there are none, a usable IPv4 A record is accepted as a fallback. An explicit "null MX" (a domain that says it takes no mail) is rejected.

What it does not do. It does not confirm that a particular mailbox exists, it does not contact the recipient's mail server, and it does not detect role accounts (such as info@), suggest typo fixes or detect bots. A passing result means the domain can receive mail, not that the person's mailbox is real.

If DNS is slow or unavailable, the address is allowed with a MEDIUM risk score and the reason DNS_INCONCLUSIVE, rather than being rejected.


Quick start

  1. Get a free key at https://sentrisend.com. Keys start with ss_live_. There is one free key per normalised email address (see Free keys).
  2. Keep the key secret. Use it from your server, never from browser code.
Validate an address
curl -X POST 'https://sentrisend.com/api/v1/validate' \

-H 'Authorization: Bearer YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -d '{"email":"user@example.com"}'

Allowed (HTTP 200):

{"allowed":true,"disposable":false,"risk_score":"LOW"}

Blocked (HTTP 400):

{"allowed":false,"disposable":true,"reason":"DISPOSABLE_DOMAIN","risk_score":"HIGH"}

reason is DISPOSABLE_DOMAIN, DOMAIN_NOT_FOUND or NO_MX_RECORDS for blocked addresses (HTTP 400), or DNS_INCONCLUSIVE for an address that is allowed because DNS could not be checked (HTTP 200, MEDIUM risk).

/validate accepts the key only as Authorization: Bearer YOUR_API_KEY.

Use the npm package
npm install sentrisend
import { validate } from "sentrisend";

const result = await validate("user@example.com", { apiKey: process.env.SENTRISEND_API_KEY }); if (result.allowed === false) console.log("Blocked:", result.reason);

Node.js 18 or newer, no runtime dependencies. The default failureMode: "open" allows the address on timeout, network failure or API 5xx; "closed" throws instead. Server-side only. The package validates addresses; it does not send email. See sentrisend on npm.

Send an email
curl -X POST 'https://sentrisend.com/api/v1/send' \

-H 'Authorization: Bearer YOUR_API_KEY' \ -H 'Content-Type: application/json' \ -H 'Idempotency-Key: welcome-email-001' \ -d '{ "to": "user@example.com", "subject": "Welcome", "html": " Your account is ready. " }'

With a free key, replace `user@example.com` with your own address, the one you signed up with. Any other recipient returns 403 RECIPIENT_NOT_VERIFIED.

/send runs the same address checks first, plus content-policy and threat-signature checks, abuse controls and sender-reputation checks, then hands the message to the delivery provider. It accepts the key as Authorization: Bearer ... or as x-api-key: ... (if both are sent, x-api-key is used).

Success (HTTP 200). The values shown are illustrative:

{

"success": true, "status": "DELIVERED", "providerId": "PROVIDER_MESSAGE_ID", "attempts": 1, "complianceProof": "hmac-sha256:v1:<64 hex characters>", "receipt": "hmac-sha256:v1: ", "riskLevel": "LOW", "riskScore": 0, "advisories": [] }

"Delivered" means the delivery provider accepted the message. It is not confirmation that it reached an inbox. status can also be DELIVERED_AFTER_RETRY; attempts is 1 to 3; providerId can be null.

Request fields for /send
FieldRequiredNotes
toYesOne address, or a non-empty array of addresses.
subjectYes3-100 characters.
htmlYesAt least 5 characters.
textNoPlain-text alternative. If supplied, at least 1 character.
fromNoSender address, with or without a display name. Some sender identities are reserved, and your delivery provider must accept the address.
reply_toNoReply address.
intendedUseNoFree-text label. Defaults to General Notification.
whiteLabelNoRequests white-label sending. It only takes effect if SentriSend has enabled it for your account (see Limits and pricing).

The request body is limited to 100 KB. The optional Idempotency-Key header (1-256 characters from A-Z a-z 0-9 . _ : -) makes retries safe: reuse the same value for retries of the same email. If you leave it out, a repeat request is treated as a new email.


Supabase signup protection (hosted hook)

SentriSend can check every new signup in Supabase Auth before the account is created, using Supabase's "Before User Created" HTTP hook. There is nothing to deploy.

  1. Get a SentriSend key and create a hook in the SentriSend dashboard. You receive a hook URL and a signing secret.
  2. In Supabase, open Authentication > Hooks > Before User Created, choose the HTTP option, and paste the URL and secret.
  3. Test with a signup.
  • Allowed signups get HTTP 200 {}.
  • Blocked signups get HTTP 200 with a Supabase error object (http_code 400, "This email address can't be used to sign up."). The 200 status is intentional: Supabase currently passes hook errors through only when the hook returns 200 or 202.
  • Fail-open: if a check times out or fails, the signup is allowed. A missing email, a disabled hook or an unknown hook ID are also allowed.
  • Requests are signature-checked (Standard Webhooks). The hook has its own limit of 60 requests a minute.
  • Safe retries: a retried request gets the earlier verdict and is not charged twice.
  • In our testing, users created directly from the Supabase dashboard do not trigger this hook.

We have tested allow and block against a real Supabase project. Full guide: https://sentrisend.com/supabase


Sender-reputation circuit breaker

Sends are tied to an API key, and delivery events (delivered, bounced, complained) are fed back to SentriSend. When a key's recent hard bounces or complaints get too high, the gateway first warns, then slows the key down, and then pauses it. A paused key needs an administrator to un-pause it, after which it runs under a probation period. The aim is to stop one bad send run from damaging your provider account. The exact thresholds are not published.

The stages are covered by automated tests. A live end-to-end threshold test against real bounce events is still to be done, so treat the breaker as new.


Errors

The error format is not uniform yet (see the roadmap). Check the HTTP status first, then code or status.

/validate
HTTPCodeMeaning
400INVALID_EMAILThe address is missing or malformed.
400*(no code; allowed: false)*A blocked verdict, with a reason.
401-Missing or invalid key.
403-Subscription inactive.
429RATE_LIMITEDToo many requests. Includes a Retry-After header and a retry_after field.
429QUOTA_EXCEEDEDMonthly allowance used up.
503-Authentication, quota or rate-limit service unavailable.
/send
HTTPCodeWhat to do
400INVALID_EMAIL, DISPOSABLE_DOMAIN_REJECTED, DOMAIN_NOT_FOUND, NO_MX_RECORDSFix the address. Don't retry unchanged.
403RECIPIENT_NOT_VERIFIEDFree keys can only send to the key owner's address.
409IDEMPOTENCY_CONFLICTThat Idempotency-Key was already used for different content.
409IDEMPOTENCY_IN_PROGRESSThe original request is still processing, or its outcome is unconfirmed. Retry with the same key, never a new one.
429QUOTA_EXCEEDEDMonthly allowance used up.
429DAILY_SEND_LIMITFree keys: daily send cap reached; resets at 00:00 UTC.
429recipient_rate_limitedToo many sends to the same recipient. Wait before retrying.
429SENDER_REPUTATION_SLOWDOWNThe key is being slowed because of recent bounces or complaints.
403SENDER_REPUTATION_PAUSEDThe key is paused. Contact SentriSend.
503SENDER_REPUTATION_UNAVAILABLEThe reputation check could not be completed. The send is not made.
503IDEMPOTENCY_UNCONFIRMEDResponse has doNotRetry: true. Check what happened to the original request first.

Some responses carry a status field instead of a code:

HTTPstatusMeaning
403BLOCKED, BLOCKED_BY_GLOBAL_INTELLIGENCERejected by a content-policy or threat check.
502DELIVERY_FAILEDThe provider reported a failure. The body has providerError and attempts. Read the error before deciding whether to retry.
503DELIVERY_UNCONFIRMEDResponse has doNotRetry: true. Don't resend blindly.
503AUDIT_UNCONFIRMEDThe provider already accepted the email. Don't send it again.

These tables are not exhaustive. You may also see 401 (missing or invalid key), 403 (inactive subscription), 413 (request body too large), other 400 responses with only error and details, and other 503 responses with no code.


Free keys

  • One free key per normalised email address. Normalisation removes +tags on every domain, removes dots only for Gmail and Googlemail addresses, and treats googlemail.com as gmail.com. So you+test@example.com and you@example.com count as the same address.
  • Already have a free key? On the sign-up form choose "Regenerate my existing free key". A new sign-up for the same address will not send an email.
  • Sign-up needs a human check and email verification before the key is shown.
  • A free key can send only to its owner's address (including those equivalent spellings), and no more than 10 sends per UTC day.

Recommended pattern: fail open

Validation should never be the reason a real person can't sign up. Block only on a definite "no" and let everything else through. Here is an example for a signup form (Node 18+):

export async function checkEmail(email, { apiKey, baseUrl = "https://sentrisend.com/api/v1", timeoutMs = 800 } = {}) {

try { const res = await fetch(${baseUrl}/validate, { method: "POST", headers: { Authorization: Bearer ${apiKey}, "Content-Type

只显示了开头部分;其余内容请在仓库中阅读