Home / MCP server directory / xyz.apexfaucet/apex-safety
Apex Safety
xyz.apexfaucet/apex-safety in the official MCP registry.
Endpoint https://apexfaucet.xyz/api/mcp/safety.
The registry describes it as: AI Agent Trust Stack MCP: Veritas Proof-Chain Notary, Machine Credit Bureau, Firewall & Grader.
We read its 25 tools on 2026-11-19. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http apex-safety https://apexfaucet.xyz/api/mcp/safety{
"mcpServers": {
"apex-safety": {
"url": "https://apexfaucet.xyz/api/mcp/safety"
}
}
}code --add-mcp '{"name":"apex-safety","type":"http","url":"https://apexfaucet.xyz/api/mcp/safety"}'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 lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
agent_firewall work_grade veritas_notary agent_credit agent_launch_audit html_sanitize token_safety_check tx_check delivery_score agent_card_grade url_threat_check package_audit contract_audit evm_log_decode wallet_investigate base_verdict base_token_price solana_token_report threat_intel_bulk token_exit_matrix robinhood_exit_check prompt_guard pii_redact content_safety cve_lookup
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-11-19):
d95c89db50358afb. 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.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read:
[](https://lazaretto.dev/mcp-registry/xyz-apexfaucet-apex-safety)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. MCP tool poisoning, explained. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse the MCP server directory.