Skip to main content
Glama

alienprobe-who-mcp

An MCP server that gives any agent one legal-entity fact — LEI, legal name, jurisdiction, entity and registration status — for $0.05 USDC on Base, paid per call over x402. No signup, no API key, no account. The wallet is the account.

Two tools:

Tool

Cost

What it does

who_terms

free

Returns the advertised price, network, payee and coverage. Never pays. Works with no wallet.

who

$0.05, real money

Returns the entity record. Misses and ambiguities cost nothing.

Client config

Three lines. Claude Desktop (claude_desktop_config.json) or Cursor (.cursor/mcp.json):

{ "mcpServers": { "who": { "command": "npx", "args": ["-y", "@alienprobe/who-mcp"],
  "env": { "PRIVATE_KEY": "0x...", "MAX_USD_PER_SESSION": "1.00" } } } }

Drop the env block entirely and the server still starts — who_terms works, who refuses with wallet_not_configured. That is the safe way to try it.

Related MCP server: gocreative-mcp

Environment

Var

Default

Meaning

PRIVATE_KEY

(none)

A throwaway Base-mainnet wallet holding a little USDC. Optional. Never logged, echoed, or returned in a tool result.

MAX_USD_PER_CALL

0.10

Hard ceiling on one lookup. The lookup is advertised at $0.05.

MAX_USD_PER_SESSION

1.00

Hard ceiling on everything this server process spends before restart.

See .env.example. Never commit a real key. Fund a wallet that holds nothing else — about $1 of USDC covers 20 lookups. This repo does not tell you how to get USDC onto Base; see https://docs.base.org/base-chain/tools/bridges/.

Spend caps

The server preflights every who call with a plain, unwrapped fetch — no signer exists on that path — reads the advertised price out of the 402, and only then decides. If the price exceeds MAX_USD_PER_CALL, or would push the running total past MAX_USD_PER_SESSION, it refuses with a result the model can read and act on:

{
  "error": "spend_cap_exceeded",
  "scope": "per_session",
  "price_usd": 0.05,
  "cap_usd": 1.0,
  "spent_usd_this_session": 1.0,
  "remaining_usd": 0.0,
  "hint": "the session budget is spent; raise MAX_USD_PER_SESSION and restart the MCP server to buy more"
}

A session is one server process. Restarting the client resets the counter, so the per-session cap is a brake, not a ledger — the wallet balance is the real ceiling. Keep it small.

What comes back

A paid hit is the API's body verbatim plus paid_usd:

{
  "schema_version": "who-lookup.v1",
  "subject": { "type": "who", "value": "apple.com" },
  "answer": {
    "lei": "HWUPKR0MPOU8FGXBT394",
    "legal_name": "Apple Inc.",
    "jurisdiction": "US-CA",
    "entity_status": "ACTIVE",
    "registration_status": "ISSUED",
    "match": { "by": "domain", "rule": "domain_exact" },
    "official_website": "https://apple.com/"
  },
  "source": { "name": "...", "vintage": "...", "coverage": "..." },
  "paid_usd": 0.05
}

q is a company name, a registrable domain, or a 20-character LEI. To disambiguate a name, append a jurisdiction in the same string: "Acme Corp;US-DE".

paid_usd is the authorized price, not the receipt

paid_usd is the amount the server authorized — the price the API advertised in its 402 and that the spend caps were judged against. It is not read back from the chain.

One case where it overstates: a wallet's first successful lookup on this pricing shelf settles at $0 (first-can-free; a property of the service, not of this client). That call still reports "paid_usd": 0.05. Every subsequent call actually moves $0.05.

The server's session counter inherits the same overstatement, which is the safe direction — it stops you early, never late. If you need the truth, the on-chain USDC Transfer from your wallet is the only receipt. Do not use paid_usd for accounting.

Free refusals

These never pay, and they come back as ordinary tool results the model can reason about — not exceptions:

Upstream

Result

400

{"error":"invalid_subject","reason":"empty"}

404

{"error":"not_found","coverage":"..."}

409

{"error":"ambiguous","candidates":[...],"hint":"re-ask with the exact legal_name, then a ;jurisdiction suffix if it still collides"}

503

{"error":"source_unavailable"}

The API only charges once it can commit to one entity, so an ambiguous re-ask is still free while it stays ambiguous.

What this does not do

  • No street addresses, no officers or directors, no ownership graph.

  • No guessing. A miss is a 404, not a best-effort answer.

  • Legal names that normalize to fewer than 2 Latin alphanumerics (CJK, Cyrillic, Greek, Arabic, Hebrew, Thai) are absent from this data vintage entirely — every door, not just the name door.

  • Domains match only where the source links an LEI to an official website, on the exact registrable domain. A subdomain misses.

Development

npm install
npm test     # 28 contract rows over a mocked fetch: no network, no wallet, no payment
npm run smoke  # spawns the server, drives initialize/tools/list/who_terms over real stdio

npm run smoke hits the live endpoint to fetch the 402. It runs with PRIVATE_KEY blank and asserts the advertised amount is "50000" ($0.05). It cannot pay.

src/core.mjs holds the transport-free logic and takes an injected fetch, which is why the tests never need a wallet. src/index.mjs is only the MCP wiring; @x402/* and viem are imported lazily, on a call already cleared to pay.

Built on @modelcontextprotocol/sdk 1.30.0. See SPEC.md for the full contract and the distribution plan.

License

MIT © Brent Bryson. See LICENSE.

Available Tools

2 tools
whowho: paid legal-entity lookupA
Read-only

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 who_terms first if the price matters.

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.

Inputs: q (required).

who_termswho: price and coverage (free)A
Read-only

FREE, read-only. Returns the advertised x402 payment terms for a who lookup — price, asset, network, payee, and the source's coverage statement — without paying anything and without needing a wallet. Use this before who to decide whether the lookup is worth the money (currently $0.05 USDC on Base mainnet). If the subject is malformed, missing or ambiguous, this returns that free refusal instead of terms, which means who would also cost nothing.

Inputs: q (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Pay-per-call x402 data products on Base mainnet — sanctions screening, aviation weather, mortgage rates, US property dossier, title chain, wallet balance, and agent session auth. Every call settles in USDC with an on-chain receipt, no accounts or API keys.
      7
      115 npm
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Keyless, pay-per-call compliance & regulated-data tools for AI agents: OFAC wallet + sanctions/PEP + KYB screening, SEC filings, FRED economics, FDA recalls, federal awards, and continuous monitoring (watch a wallet/company/brand for status changes). USDC via x402 on Base/Solana, no API key, no signup.
      -
    • F
      license
      A
      quality
      D
      maintenance
      Verified Latin American data for autonomous AI agents via x402 micropayments. Sanctions screening (OFAC SDN + SARLAFT + CNBV + COAF + UAF) with EU AI Act Art.12/13 compliant hash-chain audit trail, entity enrichment (RUES/CNPJ/RFC), and real-time LATAM central bank rates including Argentina dólar blue. $0.02–$0.10 USDC per call on Base and Solana. No API key required.
      4
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to look up token risk verdicts and ERC20 facts, wallet snapshots, gas prices, transaction summaries, and Basename resolution on the Base network. Each call is paid in USDC over x402 from a dedicated wallet the user controls, with per-call price caps and a session budget.
      94 npm
      MIT