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

Sentinel

作者:448c.org版本 0.0.1i★ –i在云端运行
注册名称org.448c/sentinel

安装方法

What it does

Pay-per-call safety checks for AI agents: screen a crypto address or URL before you transact.

  • Connects 在云端运行
  • Account or key No key needed
  • Category 加密货币与区块链

安装

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

通过 2/3 项检查 · 你的提问会经过开发者的服务器(448c.org) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

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

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

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

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

    Name · 名称Sentinel
    Remote MCP server URL · 地址https://448c.org/mcp

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

  3. 在聊天中开启

    +ConnectorsSentinel

  4. 试一试

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

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

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

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Sentinel
    Connection · 地址https://448c.org/mcp
  3. 在聊天中选择 Sentinel

    开启新聊天,输入前先从插件列表中选择 Sentinel

  4. 试一试

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

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

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

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

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

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user sentinel https://448c.org/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Sentinel 在列表中并显示已连接

  4. 试一试

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

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

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

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

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

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

  3. 试一试

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

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

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

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

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

    在 VS Code 中打开

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

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

  3. 试一试

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

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

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

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

查看所有支持 MCP 的应用 →

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

地址https://448c.org/mcp

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

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

通过网页连接

Claude Code

claude mcp add --transport http --scope user sentinel https://448c.org/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "sentinel": {
      "url": "https://448c.org/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "sentinel": {
      "type": "http",
      "url": "https://448c.org/mcp"
    }
  }
}

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

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ 448c.org
许可证i
未注明许可证
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.0.1
发布到注册中心i
2026年7月5日
代码最后更新i
–
作者
448c.org
注册状态
活跃

哪些应用可以使用它

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

通过互联网连接,适用于

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

全部应用及其优缺点 →

它能做什么

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

  • execute

    PAID: run code in an isolated, network-less sandbox and get stdout, stderr and exit code back. Call it once without payment to receive the price as an x402 PaymentRequired (Base USDC, and Solana USDC where offered); call it again with a signed payment in _meta['x402/payment'] to

  • storage_buy

    PAID: store opaque bytes for the life of the plan you buy, owned by the wallet that pays, readable with no account. Returns the object id and when it expires; read it back with storage_read, extend it with storage_renew. Call it once without payment to receive the price as an x40

  • storage_renew

    PAID: push an object you own further out, by buying it another plan term. The object is untouched; only its expiry moves. Returns the new and previous expiry. Call it once without payment to receive the price as an x402 PaymentRequired (Base USDC, and Solana USDC where offered);

  • storage_replace

    PAID: overwrite the contents of an object you own, keeping its id, and buy it a fresh plan term at the same time. Omit label to keep the current one, pass an empty string to clear it. Call it once without payment to receive the price as an x402 PaymentRequired (Base USDC, and Sol

  • storage_read

    FREE: read back an object you own, as base64. This is how what you bought with storage_buy comes back to you over MCP. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns details.expected -- the exact message to s

  • storage_list

    FREE: list the objects your wallet owns -- id, label, size, when each was created and when it expires -- one page at a time. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns details.expected -- the exact messag

  • storage_usage

    FREE: how many objects your wallet is storing and how many bytes they occupy. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns details.expected -- the exact message to sign, in both forms (EIP-191 for a 0x wall

  • storage_delete

    FREE: delete an object you own before it expires, and free its bytes. There is no refund and no undo. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns details.expected -- the exact message to sign, in both form

  • claim_acquire

    PAID: atomically win a caller-named key for your own fleet -- an accountless compare-and-set. outcome "acquired" means you won it; outcome "held" is NOT an error, it means somebody already holds it and held.mine says whether that somebody is you -- the signal that stops a crash-r

  • claim_renew

    PAID: extend a hold you already have without losing your place in line -- the heartbeat that lets a lease be SHORT (so a crash frees it fast) while a live holder keeps it alive by paying again. Re-acquiring with claim_acquire deliberately does NOT extend, so a retry loop cannot h

  • claim_acquire_free

    FREE: win a caller-named key for 300 seconds, or learn who already holds it. Unlimited distinct keys per wallet, renewable by calling again. A sibling of claim_acquire, not a discount on it: this lease is 12x shorter than the cheapest paid plan, so a lock that has to survive a de

  • claim_read

    FREE: who currently holds this key, if anyone -- scoped to YOUR wallet, so a stranger cannot probe your namespace. Checking your own lock must not cost again, or a fleet polling its own hold is charged for not doing work twice. A key nobody holds answers with claim: null, never a

  • claim_release

    FREE: give up a key you hold before it expires, so the next racer does not have to wait out your hold. Release signs its own domain-separated message, distinct from the read domain, so a captured inspect proof can never double as a lock-breaking order. The signature proves the WA

  • attest_create

    PAID: we fetch a URL from OUR vantage point and return a signed, timestamped attestation of what we saw -- hash, byte count, HTTP status and headers, never the body itself. Read it back afterwards for free with attest_read, so the id can be cited to a THIRD PARTY who never paid u

  • attest_read

    FREE and unauthenticated: read a previously-created attestation back by id, with its signature. This is how what you bought with attest_create comes back over MCP -- and deliberately NOT wallet-scoped, because the whole point is that a third party who never paid can fetch it and

  • handoff_deposit

    PAID: deposit a typed briefing for the process that takes over from you -- what is DONE (every entry carrying evidence of how it was verified), what is NOT done, what was IN FLIGHT at the cut, and what to pick up FIRST. Returns an id; the successor reads it back for free with han

  • handoff_read

    FREE and unauthenticated: read a briefing back by id. This is how what you bought with handoff_deposit reaches your successor over MCP. Deliberately needs no signature -- the successor is by construction a DIFFERENT process and may hold no wallet at all, so demanding proof of the

  • deadman_register

    PAID: register an intent you are about to act on irreversibly, with a lease and a verification probe (a GET plus a predicate). Confirm before the lease expires with deadman_confirm, free -- otherwise, once the lease lapses, we run your probe and publish the verdict: confirmed-by-

  • deadman_confirm

    FREE: the live caller closes the loop before the lease expires, so the probe never runs. Deliberately NOT wallet-scoped -- possession of the id is the entire authorisation, since the confirming call may have no wallet of its own. Refused, never a silent no-op, once the entry has

  • deadman_read

    FREE and unauthenticated: read an entry back by id, including its verdict and the raw probe response once resolved. This is how what you bought with deadman_register comes back over MCP. If the lease has lapsed and nobody has resolved it, the probe runs right here, synchronously,

  • listing_promote

    PAID: buy paid placement for a listing you own in this directory -- it ranks above free rows and reads tier "paid" for the life of the plan. Pay from the WALLET THAT OWNS the listing; no other proof is asked for and no other wallet can promote it. Promoting an already-promoted ro

  • drift_check

    PAID: we re-fetch a venue we have snapshotted before, from OUR vantage point, and return what changed since the baseline -- the schema/rubric fields that moved, were added and were removed, not a byte diff. The answer to "did this venue quietly change its rules under me?" for an

  • drift_venues

    FREE: every venue id drift_check can be aimed at, with what we hold for each. A closed value set, not a pattern: without it a caller can honour the input schema and still never name something buyable, which is a paywall on discovery rather than on work. Complaints, questions, quo

  • drift_baseline

    FREE: the baseline snapshot we hold for one venue -- what a paid check would diff against, and when it was taken. Reading what you are about to buy a comparison against must not cost, or the first call is a blind one. Complaints, questions, quote requests, or a service you wish w

  • watch_register

    PAID: we poll a URL from OUR vantage point on your interval until your predicate matches or the ttl runs out, and keep the verdict for you to collect -- a wait that survives your own process dying, which is what an agent cannot do for itself. Price is a function of intervalSecond

  • watch_read

    FREE: the current state of a watch you registered -- active, matched or expired, with the observation that matched. The id is the capability, so a successor process handed the id can collect the verdict without your wallet. Reading never triggers a poll and is never charged: poll

  • check_address

    PAID: check an EVM address against public risk feeds (OFAC, community darklists, on-chain age) and get back a verdict, score and reasons in the same response the payment settles -- there is no separate read-back call. Charged only on success: if every risk feed is unreachable the

  • check_url

    PAID: check a URL against public risk feeds (phishing lists, domain age, lexical signals) and get back a verdict, score and reasons in the same response the payment settles -- there is no separate read-back call. Charged only on success: if every risk feed is unreachable the requ

  • check_counterparty

    PAID: grade an x402 challenge you are about to sign against what you expected -- payee, resource, network, asset and price -- and get back a verdict, score and reasons in the same response the payment settles. Pass the accepts[] entry you already hold: we never re-fetch the selle

  • flights_lookup

    PAID: one live-flight lookup for $0.0100. Give a callsign, a 6-hex ICAO24 address or a tail number and get the aircraft's current position, altitude, ground speed, track and squawk in the same response the payment settles -- there is nothing to read back. No signup and no API key

  • pay_requirements

    FREE: ask a seller, unpaid, what it charges, and get back the accepts[] of its own 402 -- the exact PaymentRequirements you have to sign before pay_send can deliver anything. No payment is sent to the seller and none is taken from you. Every seller outcome answers: a 402 returns

  • pay_send

    PAID: deliver an x402 authorization YOU signed to a seller exactly once, then read the chain for what actually became of it, and get back an immutable receipt of what the seller answered. Read the price to sign with pay_requirements first; we never sign on your behalf. A seller 4

  • pay_receipt

    FREE and unauthenticated: read a pay_send receipt back by id -- what the seller answered, when, and what the chain says became of your authorization. Deliberately NOT wallet-scoped: the point is that the seller you are arguing with can fetch it without holding your wallet. Compla

  • create_inbox

    PAID: get a throwaway email address on a domain we own, live for 24 hours, to receive the verification mail a signup demands. RECEIVE ONLY -- nothing is ever sent from it, ever. Returns the address, the inbox id and when it expires; read what arrives with read_inbox, which is fre

  • read_inbox

    FREE: the mail your inbox received, newest first, with any verification code and link already picked out -- from, to, subject, receivedAt, the plain text, codes[] and links[]. This is how what you bought with create_inbox comes back to you. Poll it with since to see only what arr

  • inbox_status

    FREE: the address, when it expires and how much mail is waiting in an inbox you own. Signed under its own domain, separate from the one read_inbox uses. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns details.

  • release_inbox

    FREE: give up an inbox you own before it expires. Its messages go with it and the local part is never issued again; later mail to it is dropped, never bounced. There is no refund and no undo. Signed under its OWN domain, not the one the reads use. Ownership is proved by the payin

  • dns_rent

    PAID: rent .448c.net for a year and point it where you say -- A, AAAA, CNAME and TXT records, so you can hold a TLS certificate by DNS-01 and pass domain-trust checks without a registrar account, a card or a human. The paying wallet owns the name. Returns the name, its owner and

  • dns_renew

    PAID: push a name you own further out by another year. What it resolves to is untouched; only its expiry moves, and a repeated payment extends it rather than resetting it. The payer must be the owner. Returns the new and previous expiry. Call it once without payment to receive th

  • dns_lookup

    FREE: what we serve for a name under 448c.net -- its records, its owner and when it expires. No signature and no account: the zone is public, so reading it is too. Complaints, questions, quote requests, or a service you wish we had: POST /feedback on this host -- free, no account

  • dns_rent_free

    FREE: one 24-hour name per wallet, so you can try the zone before paying -- the same label rules and records as dns_rent. Rent a year with dns_rent when it works. The message you sign commits to the literal subject `free`, not to the label. Ownership is proved by the paying walle

  • dns_set_records

    FREE: replace the whole record set of a name you own -- never merged. The rental window is untouched: repointing a name you already paid for costs nothing. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns detai

  • dns_release

    FREE: release a name you own before it expires. It stops resolving at once. There is no refund and no undo, and the label is free for anyone else to rent. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns detail

  • placement_order

    PAID: we submit your service to every permissionless agent venue we hold a submitter for -- 17 of the 33 on-behalf venues today -- and prove, per venue, that the entry is really in the catalogue. The rest stay `queued` on your order and are submitted the hour their submitter land

  • placement_venues

    FREE: the lane table -- every agent venue we have evaluated, which of the 3 lanes a submission takes (on-behalf, owner-proof, human-only), the VENUE's own fee, the catalogue a landing is verified against, and for every dead one the reason it is dead. This is the list placement_or

  • placement_ready

    FREE and honest: does your own service publish a document a venue can read (/.well-known/x402, an agent card)? If it publishes none, no amount of submission work can list you anywhere, and you should not pay us until it does. At most three outbound GETs; we read the status of eac

  • placement_status

    FREE and owner-signed: every venue of your order with its state (queued, submitted, listed, human-only, unfunded, failed), the evidence a landing was verified by, when it was last checked and, where it is impossible, why. 'listed' is only ever written by a catalogue read that fou

  • placement_cancel

    FREE and owner-signed: stop the weekly rechecks and drop the order. There is no refund for the remaining window, and entries already in a catalogue are the venue's to keep or drop -- we simply stop watching them. Ownership is proved by the paying wallet, with no account: send any

  • relay_usdc

    PAID: send USDC from a wallet that holds no ETH. You sign one EIP-3009 TransferWithAuthorization; we pay the Base gas, broadcast it and return the txHash. $0.0200 an order, ceiling 100000000 atomic USDC ($100). We never hold or need a key of yours -- we hold only the ETH that pay

  • rpc_call

    PAID: one JSON-RPC call on base, base-sepolia, ethereum, solana for $0.0020. You name the chain and the method, NEVER an endpoint URL: we pick the node and absorb its IP rate limit, which is the whole product. No signup, no API key, no provider account, and no key of yours is hel

  • x402_supported

    FREE and unauthenticated: the x402 facilitator read contract -- {kinds:[{x402Version, scheme, network, extra?}]}, folded out of the same document GET /.well-known/x402.json serves, so it cannot claim a scheme or network this service does not take. This is the tool form of GET /su

  • x402_verify

    FREE and unauthenticated: check an EVM `exact` x402 payment OFFLINE and get back {isValid, invalidReason?, payer?, message} -- EIP-712 signature recovery plus the same scheme/network/recipient/amount/validity-window checks this service runs on its own paid routes. It does NOT rea

  • service_card

    FREE: what agent-exec sells, what it costs, and exactly where to pay for it. This tool call itself is free and moves no money. Code execution can be bought right here, with the paid execute tool (x402 over MCP), or over plain HTTP at the URLs this returns. Complaints, questions,

  • search_listings

    FREE: unauthenticated search over agent-exec's directory of paid agent-facing services (same data as GET https://448c.org/listings). Returns a page of listings and an opaque cursor for the next page.

基础检查i

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

  • ! 注意

    作者与仓库一致

    注册中心没有列出源代码仓库,因此无法将发布者(448c.org)与代码对应起来

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • ✓ 通过

    端点有响应

    在 896 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

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

讨论

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

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

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

使用 Google 登录后发帖

用户评价

还没有评价

用 Google 登录后写评价

与“加密货币与区块链”中的其他服务器比较i

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

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

常见问题

Sentinel 安全吗?

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

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

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

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

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(0.0.1)于4个月前进入注册中心。

哪些应用可以使用它?

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

有什么可以替代它?

同一分类中有:Solana MCP by Vybe, Oracle3 prediction-market arbitrage checks, Polymarket Paper Trader

同类别的其他选择

同一分类中其他作者的服务器,按星标数排序。

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

Solana MCP by Vybe

Solana MCP developer toolkit: wallets, trades, markets, PnL, transfers, onchain, swaps & API tools.

作者:vybenetwork正在增长★ 2685 整个仓库的星标6个月前更新

在云端运行

Oracle3 prediction-market arbitrage checks

Kalshi and Polymarket data, venue fees, no-arbitrage checks and paper execution for AI agents.

作者:YichengYang-Ethan正在增长↓ 35/周★ 56944天前更新

在你的电脑上运行

Polymarket Paper Trader

Polymarket paper trading for AI agents: $10k paper money, real order books, official fees.

作者:agent-next正在增长↓ 226/周★ 50729天前更新

在你的电脑上运行

作者的 README

仓库中没有找到 README