crypto-link-check
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_crypto_linkA | Checks one URL or domain for signs of crypto phishing and tells you whether it belongs to a known wallet, exchange or dapp. Use it before an agent or user opens a link to connect a wallet, sign a message or approve a token, for example a link from an email, DM, ad, search result or support chat. It runs locally and offline. It makes no network request, does not visit the page, and does not ask for keys. It compares the hostname with a hand-curated list of official domains for about 60 brands and flags lookalike characters (0/o, rn/m, Cyrillic), typosquats, punycode, free hosting and bait words such as 'claim', 'airdrop' or 'sync'. Returns: verdict (official = on the official list; no_red_flags = nothing found, which is not proof of safety; caution = one warning, such as the brand name on a different TLD; suspicious = two or more warnings; dangerous = impersonation or lookalike), the parsed host and its Unicode form, the official brand it matches or the brand it seems to imitate, and a list of findings. Each finding has a level, code and message. It does not check domain age, DNS, redirects or page content. For those, see full_report_info (a paid hosted check). Unknown brands are not covered. |
| full_report_infoA | Returns the endpoint, price and payment method of the optional paid hosted check. It does not call the API and does not pay or sign anything. The paid check covers what check_crypto_link cannot see offline: domain registration age (RDAP), DNS resolution, the redirect chain, and one fetch of the page scanned for seed-phrase prompts and token-approval drainer code. It accepts 1-10 URLs per call for 0.005 USDC on Base via x402. Use it when check_crypto_link returns no_red_flags or caution for a link that someone is about to trust with a wallet and you want more evidence. If check_crypto_link already says dangerous or official, you usually do not need it. Returns: method, url_template, price_usdc, network, asset, protocol, max_urls, settles and docs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are mostly distinct: one performs a local link check and the other only returns metadata about a paid hosted service. However, the name 'full_report_info' could be mistaken for an actual deep-scan operation, and only the description prevents that misselection.
Both names use snake_case and are readable, but they follow different structural conventions: an action verb phrase (check_crypto_link) versus a noun-ish descriptor (full_report_info). Minor deviation rather than inconsistency.
Two tools is thin for a security-checking server; a single checking tool plus a metadata/info tool is borderline. The narrow scope keeps it defensible, but it feels under-scoped.
There is a notable dead end: the server advertises a paid hosted check but exposes no tool to actually invoke it, only an info endpoint. There is also no batch-check tool or way to list supported brands, so agents cannot complete the advertised deeper-verification workflow.