Home / MCP registry index / io.github.GrayWolf8-creator/gw8-signal-api

GW8 Signal API

io.github.GrayWolf8-creator/gw8-signal-api in the official MCP registry. Endpoint https://micro-saas-agent.onrender.com/mcp. Source: github.com/GrayWolf8-creator/micro-saas-agent.

The registry describes it as: Pay-per-call crypto signals, token verdicts, flows & briefs. x402 USDC on Base. Signal-only.

Connect it

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

claude mcp add --transport http gw8-signal-api https://micro-saas-agent.onrender.com/mcp

{
  "mcpServers": {
    "gw8-signal-api": {
      "url": "https://micro-saas-agent.onrender.com/mcp"
    }
  }
}

code --add-mcp '{"name":"gw8-signal-api","type":"http","url":"https://micro-saas-agent.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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

get_sample get_brief_teaser list_paid_endpoints get_full_signal get_band_dots get_regime get_coin subscribe_green_dot_alerts buy_day_pass get_history get_token_verdict get_flows get_rwa_feed get_gov_contracts get_kraken_listings get_crypto_rules get_relative_strength get_payment_rails check_spend_policy check_seller_reputation should_i_pay get_daily_brief get_value_score get_value_screen get_value_history get_growth_setup get_growth_screen get_growth_history get_signing_pubkey

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-graywolf8-creator-gw8-signal-api/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-graywolf8-creator-gw8-signal-api)

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