Home / MCP registry index / org.448c/sentinel

Sentinel

org.448c/sentinel in the official MCP registry. Endpoint https://448c.org/mcp.

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

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

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

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

code --add-mcp '{"name":"sentinel","type":"http","url":"https://448c.org/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

execute storage_buy storage_renew storage_replace storage_read storage_list storage_usage storage_delete claim_acquire claim_renew claim_acquire_free claim_read claim_release attest_create attest_read handoff_deposit handoff_read deadman_register deadman_confirm deadman_read listing_promote drift_check drift_venues drift_baseline watch_register watch_read check_address check_url pay_requirements pay_send pay_receipt create_inbox read_inbox inbox_status release_inbox dns_rent dns_renew dns_lookup dns_rent_free dns_set_records dns_release placement_order placement_venues placement_ready placement_status placement_cancel x402_supported x402_verify service_card search_listings

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): b7be275734a360fe. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/org-448c-sentinel/badge.svg)](https://lazaretto.dev/mcp-registry/org-448c-sentinel)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers