alienprobe-who-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRIVATE_KEY | No | A throwaway Base-mainnet wallet holding a little USDC. Optional. Never logged, echoed, or returned in a tool result. | |
| MAX_USD_PER_CALL | No | Hard ceiling on one lookup. The lookup is advertised at $0.05. | 0.10 |
| MAX_USD_PER_SESSION | No | Hard ceiling on everything this server process spends before restart. | 1.00 |
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 |
|---|---|
| who_termsA | FREE, read-only. Returns the advertised x402 payment terms for a |
| whoA | SPENDS REAL MONEY: $0.05 USDC on Base mainnet per successful answer, paid from the wallet in the server's PRIVATE_KEY env var. Not a subscription, not credits — an on-chain payment per call. Check Returns exactly one GLEIF Level 1 record: LEI, legal name, jurisdiction, entity status, registration status, last update, how it matched, and (domain queries only) the official website. No addresses, no officers, no ownership graph, no guesses. FREE refusals — these cost nothing and are returned as ordinary results: invalid_subject (malformed) | not_found (no match) | ambiguous (up to 5 candidates; re-ask with an exact legal_name and a ;jurisdiction suffix) | source_unavailable. Refuses without paying when the advertised price exceeds MAX_USD_PER_CALL (currently $0.10) or would exceed MAX_USD_PER_SESSION ($1.00). Known gap: legal names that normalize to fewer than 2 Latin alphanumerics (CJK, Cyrillic, Arabic, Hebrew, Thai...) are absent from this data vintage entirely. |
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 have clearly distinct roles: who_terms is a free, read-only price preview; who is the paid lookup. Descriptions explicitly guide the agent to call who_terms first, and there is no overlap in purpose.
Both tools use lowercase snake_case and share the 'who' stem, but neither follows a standard verb_noun pattern (who is a bare interrogative, who_terms is a noun phrase). Still, the style is consistent and readable.
Two tools are exactly right for a single-purpose lookup service: one free preview and one paid action. No tools are superfluous, and the count avoids bloat for a narrow domain.
The tool set covers the full lifecycle for a paid lookup: check terms, then perform lookup with comprehensive result fields and free refusal handling. The only gap is a data vintage limitation (non-Latin names), which is not a tool surface gap.