# 1gateway (remote · 1gateway.dev)

Pay-per-call tools for agents via x402 (USDC on Base): Korean data, doc-to-Markdown, web utilities.

- Trust score: 62/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `1gateway.dev`: 62/100 (this document), [markdown](https://verifymcp.io/servers/code0xff-1gateway/1gateway.md), [page](https://verifymcp.io/servers/code0xff-1gateway/1gateway)

## Channel facts

- Endpoint: `https://1gateway.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 18 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3810 tokens (~211/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the 1gateway MCP server?

1gateway is a hosted endpoint at https://1gateway.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http code0xff-1gateway 'https://1gateway.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "code0xff-1gateway": {
      "url": "https://1gateway.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "code0xff-1gateway": {
      "type": "http",
      "url": "https://1gateway.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.code0xff-1gateway]
url = "https://1gateway.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "code0xff-1gateway": {
      "type": "remote",
      "url": "https://1gateway.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add code0xff-1gateway --url 'https://1gateway.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  code0xff-1gateway:
    url: "https://1gateway.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "code0xff-1gateway": {
      "Transport": "http",
      "Url": "https://1gateway.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add code0xff-1gateway -t streamable-http -u 'https://1gateway.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "code0xff-1gateway": {
      "type": "http",
      "url": "https://1gateway.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-14 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 60, 0)

- [functional regression] Schema quality: 3129 → 3810
- [functional] New tool “base_token_info”
- [functional] New tool “base_tx”
- [functional] New tool “base_wallet_balances”

### 2026-10-12 (score 60, +1)

- [security] Tool “convert_to_markdown” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 2828 → 3129
- [functional] Server version: 0.1.0 → 0.1.1
- [functional] New tool “kr_bok_ecos_series”

### 2026-10-11 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-10 (score 59)

First indexed and scored.

## MCP tools (18)

### `kr_apartment_trades` (~228 tokens)

Korea apartment sale transactions (MOLIT) — English JSON with KRW & USD

Use when you need actual apartment sale prices in a South Korean district for a month (property research, valuation, comps). Data: MOLIT (Korea land ministry) reported deals since 2006, updated daily. Input: region (5-digit LAWD_CD, e.g. 11680 Gangnam-gu), month (YYYYMM). Output: JSON trades with contract date, complex (Korean + romanized), area m2, floor, build year, price in KRW and USD, price per m2, deal type, cancelled flag. Example: ?region=11680&month=202609 Price: $0.0045 USDC via x402.

Input parameters:

- `month` (string, required): Contract month YYYYMM, 200601 to the current month (KST)
- `region` (string, required): 5-digit 시군구 code (LAWD_CD), e.g. 11680 = Seoul Gangnam-gu, 11110 = Jongno-gu, 41135 = Seongnam Bundang-gu. Unknown codes → 400 (not charged).

### `kr_apartment_trades_summary` (~189 tokens)

Korea apartment price summary for a district-month (count, median/avg price and price per m²)

Use when you need a quick housing-market snapshot for a South Korean district-month instead of raw trades. Data: MOLIT reported apartment sales, cancelled deals excluded. Input: region (5-digit LAWD_CD, e.g. 11680), month (YYYYMM). Output: JSON count, median/average/min/max price and price per m2 and per pyeong in KRW and USD, breakdown by size class, top complexes by volume. Example: ?region=11680&month=202609 Price: $0.0045 USDC via x402.

Input parameters:

- `month` (string, required): Contract month YYYYMM, 200601 to the current month (KST)
- `region` (string, required): 5-digit 시군구 code (LAWD_CD), e.g. 11680 = Seoul Gangnam-gu. Unknown codes → 400 (not charged).

### `kr_bok_ecos_series` (~297 tokens)

Bank of Korea ECOS statistics (BOK-authored series only) with attribution

Use when you need official Bank of Korea statistics (base rate, money supply, key indicators) as a time series. Input: stat (ECOS table code, e.g. 722Y001), cycle (A/S/Q/M/SM/D), start, end (period format of cycle), optional item (e.g. 0101000). Output: JSON series with English labels, units, observations [{period,value}] (max 1,000 rows) and source attribution. Only BOK-authored tables are served. Example: ?stat=722Y001&cycle=M&start=202401&end=202412&item=0101000 Price: $0.0045 USDC via x402.

Input parameters:

- `cycle` (string, required): A annual, S semi-annual, Q quarterly, M monthly, SM semi-monthly, D daily
- `end` (string, required): End period, same format as start
- `item` (string): Item code 1 (e.g. 0101000). Optional item2..item4 also accepted.
- `start` (string, required): Start period in ECOS format (A: YYYY, Q: YYYYQn, M: YYYYMM, D: YYYYMMDD)
- `stat` (string, required): ECOS statistic table code, e.g. 722Y001 (base rate). Non-BOK tables → 403 (not charged).

### `kr_weather_forecast` (~193 tokens)

Korea short-term weather forecast (KMA) by latitude/longitude

Use when you need the official weather forecast for a point in South Korea for the next ~3-5 days. Data: KMA (Korea Meteorological Administration) village forecast on a 5 km grid, issued 8 times a day. Input: lat, lon (WGS84 decimal; Korea only). Output: JSON hourly then 3-hourly temperature C, sky, precipitation type and probability %, rain and snow amounts, humidity %, wind; plus daily min/max. Example: ?lat=37.5665&lon=126.978 Price: $0.0045 USDC via x402.

Input parameters:

- `lat` (number|string, required): Latitude, WGS84 decimal degrees (KMA domain ≈ 32–44; outside → 400, not charged)
- `lon` (number|string, required): Longitude, WGS84 decimal degrees (KMA domain ≈ 123–133)

### `kr_public_holidays` (~131 tokens)

Korea public holidays for a year (KASI), English names

Use when you need South Korea's official public holidays for a year (business-day calculation, scheduling, settlement and payroll calendars). Data: KASI (Korea Astronomy and Space Science Institute) special-day register, incl. substitute and temporary holidays once promulgated. Input: year (YYYY, 2004-2100). Output: JSON list with date, weekday, Korean and English name, isPublicHoliday, kind. Example: ?year=2026 Price: $0.0027 USDC via x402.

Input parameters:

- `year` (number|string, required): Year YYYY (2004–2100)

### `kr_trade_exports_10day` (~216 tokens)

Korea 10-day export flash (Korea Customs): totals, YoY, top items and markets

Use when you need South Korea's earliest export read: the Korea Customs 10-day provisional release (days 1-10, 1-20, full month; out on the 11th, 21st and 1st). Input: optional month (YYYYMM) and period (10, 20, full); default latest. Output: JSON exports in USD with YoY %, latest 10-day increment, 10 key items (semiconductors, cars, ships...) and 10 markets (China, US, EU, Vietnam...) with YoY and share, next release date. Example: ?month=202609 Price: $0.0045 USDC via x402.

Input parameters:

- `month` (string): Release month YYYYMM (default: latest release; data from 2024-09)
- `period` (string): 10 (days 1-10), 20 (days 1-20) or full; requires month. Default: latest available for the month

### `kr_trade_hs` (~230 tokens)

Korea monthly exports/imports by HS code (Korea Customs), English HS descriptions, YoY

Use when you need South Korea's monthly trade for a product by HS code (e.g. 8542 chips, 870323 cars, 2710 petroleum). Data: Korea Customs Service, finalized monthly. Input: hs (2-10 digit prefix), optional month (YYYYMM, default latest), limit (1-100), sort (exports, imports, balance, total). Output: JSON totals (exports FOB, imports CIF, balance in USD, kg) with YoY % and 10-digit HSK lines with English HS descriptions and YoY. Example: ?hs=8542&month=202608 Price: $0.0045 USDC via x402.

Input parameters:

- `hs` (string, required): HS code prefix, 2-10 digits (e.g. 8542 integrated circuits, 870323 passenger cars)
- `limit` (number|string): Max 10-digit lines returned (1-100, default 20)
- `month` (string): Month YYYYMM (default: latest finalized month)
- `sort` (string): Line order (default exports)

### `kr_trade_pulse` (~131 tokens)

Korea Trade Pulse: latest export flash, 12-month trend and semiconductor detail in one call

Use when you need a one-call read on South Korea's export cycle for macro, FX or chip-sector analysis. Data: Korea Customs 10-day and monthly releases. Input: none. Output: JSON headline (latest exports and YoY, semiconductor share, strongest/weakest item and market, 3-month average YoY, momentum), latest release by item and market, 12 monthly export totals with YoY, and HS 8542 integrated-circuit trade for the latest month. Example: /v1/trade/pulse Price: $0.0045 USDC via x402.

### `web_metadata` (~152 tokens)

URL metadata / link preview: title, description, Open Graph, Twitter card, icons, feeds, JSON-LD

Use when an agent needs to know what a URL is before reading it, or to build a link preview or citation. Input: url (public http/https). Output: JSON with final URL after redirects, HTTP status, content type, title, description, site name, language, canonical, preview image, favicon, Open Graph and Twitter tags, RSS/Atom feeds, hreflang alternates, JSON-LD types, robots, first H1. No JavaScript is run. Example: ?url=https://developer.mozilla.org/en-US/ Price: $0.002 USDC via x402.

Input parameters:

- `url` (string, required): Public http(s) URL; private/internal addresses → 400 (not charged)

### `domain_lookup` (~182 tokens)

Domain lookup: DNS records, mail provider, SPF/DMARC, RDAP registrar, creation/expiry dates

Use when an agent must check a domain: does it resolve, who hosts its DNS and mail, is email authenticated, how old is it, when does it expire. Input: domain (e.g. example.com; URLs accepted). Output: JSON DNS records (A, AAAA, CNAME, MX, NS, TXT, CAA, SOA), mail provider, parsed SPF and DMARC, DNS provider, and RDAP registration (registrar, created, expires, age in days, status, DNSSEC). No contact data. Example: ?domain=google.com Price: $0.0045 USDC via x402.

Input parameters:

- `domain` (string, required): Public domain or hostname (punycode for IDNs, e.g. xn--...); a URL is reduced to its hostname. Internal/reserved names → 400 (not charged)

### `fx_rates` (~295 tokens)

FX reference rates (ECB): 30 currencies incl. KRW, any base, conversion, last 90 days

Use when you need an official daily FX rate or currency conversion (USD, EUR, KRW, JPY, CNY, GBP + 24 more). Input: base (default EUR), optional symbols (comma list), date (YYYY-MM-DD, last ~90 days; weekends use the prior fixing), amount. Output: JSON rates for the fixing date, % change vs prior fixing, converted amounts, raw ECB EUR rates. Source: ECB statistics, updated each TARGET day ~16:00 CET; reference only. Example: ?base=USD&symbols=KRW,JPY&amount=100 Price: $0.002 USDC via x402.

Input parameters:

- `amount` (number|string): Amount in base currency to convert
- `base` (string): Base currency, ISO 4217 (one of the 30 ECB reference currencies; default EUR)
- `date` (string): Fixing date YYYY-MM-DD within the last ~90 days (default latest)
- `symbols` (string): Comma-separated target currencies (default: all). Supported: EUR,USD,JPY,KRW,CNY,GBP,AUD,BRL,CAD,CHF,CZK,DKK,HKD,HUF,IDR,ILS,INR,ISK,MXN,MYR,NOK,NZD,PHP,PLN,RON,SEK,SGD,THB,TRY,ZAR

### `time_convert` (~252 tokens)

Time-zone conversion: one instant in many zones, DST-aware, offsets, business hours

Use when scheduling across time zones or turning a local time into UTC without guessing DST. Input: to (IANA zones or KST, PST, CET...), optional from (zone of a local time, default UTC), time (ISO 8601, Unix seconds, or now). Output: JSON UTC instant, Unix time, and per zone: local ISO time with offset, weekday, abbreviation, DST and business-hours flags, day difference. Example: ?time=2026-10-12T09:00&from=Asia/Seoul&to=America/New_York,Europe/London Price: $0.002 USDC via x402.

Input parameters:

- `from` (string): Zone of the input local time (default UTC; ignored when time has an offset)
- `time` (string): ISO 8601 date-time (2026-10-12T09:00, 2026-10-12T09:00:00+09:00), Unix seconds/ms, or now
- `to` (string, required): 1–25 target zones, comma-separated (IANA names like Asia/Seoul, UTC, or abbreviations like KST, PST, CET)

### `site_profile` (~151 tokens)

Site profile: page metadata + security headers + robots/llms.txt + DNS, mail auth and domain age in one call

Use when an agent must vet or research a website in one call (lead research, security or SEO check, is this site legit). Input: url or bare domain. Output: JSON page metadata, HTTP status, HTTPS and HTTP-to-HTTPS redirect, server and hosting hints, 7 security headers, robots.txt (sitemaps, AI-crawler rules), llms.txt presence, plus domain DNS, mail provider, SPF/DMARC and RDAP registrar, age and expiry. Example: ?url=stripe.com Price: $0.009 USDC via x402.

Input parameters:

- `url` (string, required): Site URL or bare domain (https:// assumed); private/internal targets → 400 (not charged)

### `base_token_risk` (~212 tokens)

Base token / contract risk signals: proxy, owner, privileged functions, pools, buy/sell simulation

Use when an agent must vet a Base ERC-20 before buying or integrating it. Input: address. Output: JSON risk signals with block+evidence: proxy+admin, owner (renounced/EOA/contract/undeclared), mint/pause/blacklist/fee selectors, Uniswap v2/v3/v4 (incl. hooked launch pools, hook permissions) + Aerodrome pools, buy/sell simulation, notChecked. Signals, not a safe verdict. Bad input/EOA: 400, not charged. Example: ?address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 Price: $0.009 USDC via x402.

Input parameters:

- `address` (string, required): Token contract on Base mainnet (0x + 40 hex; mixed case must be a valid EIP-55 checksum). EOAs, bad checksums → 400 before payment (not charged)

### `base_wallet_balances` (~248 tokens)

Base wallet balances: ETH + many ERC-20s in one call, with nonce and contract flag

Use when an agent needs what a Base address holds in one call instead of one RPC call per token. Input: address; optional tokens (up to 20 ERC-20 addresses, comma-separated; default USDC, EURC, USDbC, WETH, cbBTC, cbETH, wstETH). Output: JSON block+time, ETH balance, per-token symbol, decimals, raw and decimal balance, nonce, isContract. Chain state only, no prices. Bad input: 400, not charged. Example: ?address=0x6246eee0355Dd7A93C888fE59e1151388A0cC5a1 Price: $0.002 USDC via x402.

Input parameters:

- `address` (string, required): Wallet or contract on Base mainnet (0x + 40 hex; mixed case must be a valid EIP-55 checksum). Bad input → 400 (not charged)
- `tokens` (string): Up to 20 comma-separated ERC-20 contract addresses on Base. Omit for the default set. A contract that is not an ERC-20 is listed with status not_an_erc20.

### `base_token_info` (~244 tokens)

Base ERC-20 token info: name, symbol, decimals, total supply, optional holder balance and allowance

Use when an agent needs an ERC-20's basics on Base before quoting, transferring or approving it. Input: address (token contract); optional holder (adds balance and share of supply) and spender (adds allowance, flags unlimited approvals). Output: JSON block+time, name, symbol, decimals, totalSupply raw and decimal, known issuer if curated. Name/symbol are self-reported. EOA or non-ERC-20: 4xx, not charged. Example: ?address=0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 Price: $0.002 USDC via x402.

Input parameters:

- `address` (string, required): ERC-20 token contract on Base mainnet (0x + 40 hex; mixed case must be a valid EIP-55 checksum). EOA → 400, non-ERC-20 contract → 422 (not charged)
- `holder` (string): Optional address whose token balance and share of total supply to include
- `spender` (string): Optional spender; with holder, adds allowance(holder, spender). Needs holder.

### `base_tx` (~189 tokens)

Base transaction status with decoded ERC-20 transfers, fee and confirmations

Use when an agent must confirm a Base transaction or payment landed: did it succeed, who paid whom, how much of which token. Input: hash. Output: JSON status (success/reverted), block+time, confirmations, from, to, ETH value, fee (L2 gas + L1 data fee), decoded ERC-20 transfers with symbol and decimal amount (first 25). Unknown or unmined hash: 404, not charged. Example: ?hash=0x284f8abed91b5631ee28bdb1ccfe78374e18c480cb2ab25f28e3bfac5210fe0b Price: $0.0045 USDC via x402.

Input parameters:

- `hash` (string, required): Transaction hash on Base mainnet (0x + 64 hex). Unknown or not yet mined → 404 (not charged)

### `convert_to_markdown` (~270 tokens)

Document to Markdown: web pages, PDF, DOCX and Korean HWP/HWPX

Use when an agent must read a document as clean Markdown: web page, PDF, DOCX or Korean HWP/HWPX, tables kept. Input: url (http/https) via GET, or POST a file (multipart 'file', raw body, or JSON contentBase64+filename). Free-plan size cap → 413 before payment: HWP 48 KB, HWPX 100 KB XML. Output: JSON markdown, title, pages, sourceType, warnings. Price by detected type: HTML $0.0027, PDF/DOCX $0.0045, HWP/HWPX $0.009. Example: ?url=https://example.com/ Price: $0.0027–$0.009 USDC via x402.

Input parameters:

- `contentBase64` (string): Document bytes as base64 (alternative to url; max 10 MB decoded)
- `filename` (string): Original file name, e.g. report.hwp (helps detection)
- `type` (string): Optional expected type: html, text, pdf, docx, hwp, hwpx
- `url` (string): Public http(s) URL of a web page, PDF, DOCX, HWP or HWPX (max 10 MB)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/code0xff-1gateway/1gateway#diagnostics

## Score history

- 2026-10-17: 62
- 2026-10-16: 62
- 2026-10-15: 61
- 2026-10-14: 61
- 2026-10-13: 60
- 2026-10-12: 60
- 2026-10-11: 59
- 2026-10-10: 59

## Common questions

### What is the 1gateway MCP server?

1gateway is an MCP server listed in the public MCP registry as io.github.code0xff/1gateway. Pay-per-call tools for agents via x402 (USDC on Base): Korean data, doc-to-Markdown, web utilities. This page covers its hosted endpoint (https://1gateway.dev/mcp).

### Is the 1gateway MCP server safe to use?

1gateway scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the 1gateway MCP server expose?

1gateway exposes 18 tools: kr_apartment_trades, kr_apartment_trades_summary, kr_bok_ecos_series, kr_weather_forecast, kr_public_holidays, and 13 more. Their descriptions and schemas cost roughly 3,810 tokens of context every time the server is loaded.

### Does the 1gateway MCP server require authentication?

No. We connected to 1gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the 1gateway MCP server still maintained?

1gateway is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://1gateway.dev/mcp
- Website: https://1gateway.dev/
- Changelog RSS feed: https://verifymcp.io/servers/code0xff-1gateway/1gateway.xml
- Changelog JSON feed: https://verifymcp.io/servers/code0xff-1gateway/1gateway.json
- HTML version of this page: https://verifymcp.io/servers/code0xff-1gateway/1gateway