Home / MCP server directory / io.github.adamgraymon/depin-gpu-compute-sla-escrow

Depin Gpu Compute Sla Escrow

io.github.adamgraymon/depin-gpu-compute-sla-escrow in the official MCP registry. Endpoint https://own-adam.onrender.com/mcp. Source: github.com/adamgraymon/Own_adam.

The registry describes it as: ERC-8183 DePIN & GPU Compute Benchmark SLA Auditor (TFLOPS/VRAM) & USDC Escrow on Base.

We read its 23 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 Code
claude mcp add --transport http depin-gpu-compute-sla-escrow https://own-adam.onrender.com/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "depin-gpu-compute-sla-escrow": {
      "url": "https://own-adam.onrender.com/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"depin-gpu-compute-sla-escrow","type":"http","url":"https://own-adam.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.

Install lazaretto-guard
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

check_mcp_server_trust review_agent_skill_free get_trust_dossier_sample discover_verified_stores quote_multitoken_escrow open_escrow_job submit_encrypted_deliverable claim_escrow_timeout_refund audit_quant_backtest_escrow audit_smart_contract_escrow audit_api_sla_escrow audit_agent_skill_escrow audit_rag_embeddings_escrow audit_ai_inference_escrow audit_depin_gpu_sla_escrow verify_onchain_escrow_status purchase_firstparty_catalog_item register_and_certify_store inspect_veritas_8183_seal submit_veritas_tier_upgrade_exam manage_buyer_finops_spend_passport notarize_and_witness_a2a_deal match_verified_buyers_by_intent

Tool changes

This server changed its tools after we first read them. If you approved it before the latest change, what you approved is not what it serves now: read its tools again.

Fingerprint of its tools at our last full read (2026-11-19): 6e3fbcbac1a7157f. 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: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-adamgraymon-depin-gpu-compute-sla-escrow/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-adamgraymon-depin-gpu-compute-sla-escrow)

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.