Home / MCP registry index / io.github.canoydario847-cloud/privi-agent-survival
Privi Agent Survival & Premium
io.github.canoydario847-cloud/privi-agent-survival in the official MCP registry.
Endpoint https://privi-ai-21-gateway.onrender.com/mcp. Source: github.com/canoydario847-cloud/Privi-Network.
The registry describes it as: 32 agent utilities and 51 premium analyzers. API key required; automated checkout not active.
We read its 83 tools on 2026-11-14. 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 privi-agent-survival https://privi-ai-21-gateway.onrender.com/mcp{
"mcpServers": {
"privi-agent-survival": {
"url": "https://privi-ai-21-gateway.onrender.com/mcp"
}
}
}code --add-mcp '{"name":"privi-agent-survival","type":"http","url":"https://privi-ai-21-gateway.onrender.com/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 lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
privi_time_now privi_nonce_generate privi_payload_hash privi_receipt_hash privi_receipt_verify privi_secret_scan privi_log_redact privi_prompt_risk privi_scope_check privi_url_safety privi_retry_schedule privi_backoff_window privi_timeout_budget privi_circuit_decide privi_rate_budget privi_uptime_calculate privi_slo_budget privi_latency_percentiles privi_error_classify privi_traceparent privi_json_canonical privi_json_pointer privi_json_merge_preview privi_csv_profile privi_dedupe_records privi_token_cost privi_quota_remaining privi_batch_plan privi_dependency_order privi_tool_schema_check privi_idempotency_key privi_expiry_window privi_pro_manifest_fingerprint privi_pro_manifest_diff privi_pro_scope_excess privi_pro_policy_coverage privi_pro_approval_gate privi_pro_action_chain_append privi_pro_action_chain_verify privi_pro_nonce_replay_window privi_pro_auth_session_review privi_pro_delegation_review privi_pro_uptime_slo privi_pro_error_budget privi_pro_latency_slo privi_pro_response_status_mix privi_pro_retry_risk privi_pro_incident_priority privi_pro_deployment_canary privi_pro_dependency_availability privi_pro_run_health_summary privi_pro_circuit_threshold privi_pro_dataset_quality privi_pro_csv_column_consistency privi_pro_json_schema_minimal privi_pro_schema_version_diff privi_pro_payload_field_audit privi_pro_data_freshness privi_pro_pii_presence privi_pro_retention_schedule and 23 more
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-14):
697806e361dd740c. 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/io-github-canoydario847-cloud-privi-agent-survival)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. How tool poisoning works. 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 every server in the index.