Home / MCP registry index / ai.greyridgesignals/tech-risk
ai.greyridgesignals/tech-risk
ai.greyridgesignals/tech-risk in the official MCP registry.
Endpoint https://api.greyridgesignals.ai/mcp.
The registry describes it as: x402 pay-per-call: pre-trade swap gate, token safety, Base RPC, DeFi/Polymarket data (USDC)
We read its 26 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.
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 every week.
Tools it advertises
enrich_tech_risk enrich_domain scan_mcp_server scan_mcp_preview crypto_prices crypto_funding defi_yields pm_markets crypto_prices_preview crypto_funding_preview defi_yields_preview pm_markets_preview chain_block_number chain_gas_price chain_balance chain_token_balance chain_tx chain_wallet chain_token_security chain_block_number_preview chain_gas_price_preview chain_token_report gate_swap gate_swap_preview chain_token_report_preview chain_token_security_preview
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-greyridgesignals-tech-risk)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.