Give your agent the
attribution layer.

Gray Wolf analytics as callable tools, over Model Context Protocol. Authorized with the API key you already have.

Requires an active Gray Wolf API key.

For agents

https://mcp.graywolfai.com/setup.md

Point an agent at that URL and it can install and verify the connection on its own. The guide carries the install steps for every supported client, the authorization flow, the tool contract and the error codes, as Markdown.

Connect in one command

One Streamable HTTP endpoint. Your client opens a browser, you authorize once, and it holds short-lived read-only credentials from then on.

https://mcp.graywolfai.com/mcp

An active Gray Wolf API key is required to authorize the connection. Contact us if you need one.

Claude Code
claude mcp add --transport http graywolf-mcp https://mcp.graywolfai.com/mcp
Codex
codex mcp add graywolf-mcp --url https://mcp.graywolfai.com/mcp
codex mcp login graywolf-mcp
Claude Desktop
Customize, then Connectors, then Add custom connector. Enter the endpoint above and complete the browser authorization.
Headless clients
A client that cannot run OAuth may send the API key as a bearer token instead. Keep it in a secret manager, never in a prompt.

Eight read-only tools

Attribute first, then screen for risk. Tracing is the expensive call, so an agent should start narrow and check the point budget before widening.

Attribute

graywolf_get_attribution
Entity, category and source metadata behind one Bitcoin, Ethereum/EVM or Tron address, with clusters and tags where available.
graywolf_get_attribution_batch
The same for 2 to 100 addresses in a single call, results in input order.
graywolf_get_cluster_members
The addresses belonging to a cluster returned by an attribution result.

Screen

graywolf_get_address_risk
Overall, fraud, sanctions and illicit indicators for one address, each with the evidence behind it.
graywolf_get_exposure
Known paths connecting an address to deceptive entities, bounded by hop count.

Trace

graywolf_get_first_funder
The earliest observed funder of an address, attributed. A funding event, not proof of ownership.
graywolf_trace_money_flow
Inbound and outbound transfers with sender and receiver attribution, bounded by hops, detail level and date range.
graywolf_get_usage
Point usage, monthly limit and remaining points for the calling key, with an endpoint breakdown.

Results are screening signals, not proof and not a legal compliance determination. An unknown or false indicator does not mean an address is safe.

Your key never reaches the agent

The agent holds a short-lived token scoped to read-only analytics, and nothing else.

  • The client opens the Gray Wolf authorization page at api.staysafecrypto.com. Confirm that host before typing anything.
  • You enter an existing API key once. It is validated, then discarded. It is never returned to the client, never placed in a token, and never stored in the grant tables.
  • The client receives credentials scoped to analytics:read and refreshes them without ever learning the key.
  • Every tool is read-only, and usage bills against the same key and point budget you already track.