Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Nothing to run from here
1gateway is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
18
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Pay-per-call tools for agents via x402 (USDC on Base): Korean data, doc-to-Markdown, web utilities.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http 1gateway-mcp https://1gateway.dev/mcp
# 2 — ask your agent for something these tools do
# kr_apartment_trades, kr_apartment_trades_summary, kr_bok_ecos_series and 15 more
1gateway costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
COAll 1 server
code0xff1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http 1gateway-mcp https://1gateway.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
18 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 p
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region | string | yes | 5-digit 시군구 code (LAWD_CD), e.g. 11680 = Seoul Gangnam-gu, 11110 = Jongno-gu, 41135 = Seongnam Bundang-gu. Unknown codes → 400 (not charged). |
| month | string | yes | Contract month YYYYMM, 200601 to the current month (KST) |
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=1168
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region | string | yes | 5-digit 시군구 code (LAWD_CD), e.g. 11680 = Seoul Gangnam-gu. Unknown codes → 400 (not charged). |
| month | string | yes | Contract month YYYYMM, 200601 to the current month (KST) |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stat | string | yes | ECOS statistic table code, e.g. 722Y001 (base rate). Non-BOK tables → 403 (not charged). |
| cycle | string | yes | A annual, S semi-annual, Q quarterly, M monthly, SM semi-monthly, D daily |
| start | string | yes | Start period in ECOS format (A: YYYY, Q: YYYYQn, M: YYYYMM, D: YYYYMMDD) |
| end | string | yes | End period, same format as start |
| item | string | no | Item code 1 (e.g. 0101000). Optional item2..item4 also accepted. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| lat | number/string | yes | Latitude, WGS84 decimal degrees (KMA domain ≈ 32–44; outside → 400, not charged) |
| lon | number/string | yes | Longitude, WGS84 decimal degrees (KMA domain ≈ 123–133) |
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. Exam
| Parameter | Type | Required | Notes |
|---|---|---|---|
| year | number/string | yes | Year YYYY (2004–2100) |
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 an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| month | string | no | Release month YYYYMM (default: latest release; data from 2024-09) |
| period | string | no | 10 (days 1-10), 20 (days 1-20) or full; requires month. Default: latest available for the month |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hs | string | yes | HS code prefix, 2-10 digits (e.g. 8542 integrated circuits, 870323 passenger cars) |
| month | string | no | Month YYYYMM (default: latest finalized month) |
| limit | number/string | no | Max 10-digit lines returned (1-100, default 20) |
| sort | string | no | Line order (default exports) |
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
No parameter schema on file.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Public http(s) URL; private/internal addresses → 400 (not charged) |
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 conta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| domain | string | yes | Public domain or hostname (punycode for IDNs, e.g. xn--...); a URL is reduced to its hostname. Internal/reserved names → 400 (not charged) |
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 C
| Parameter | Type | Required | Notes |
|---|---|---|---|
| base | string | no | Base currency, ISO 4217 (one of the 30 ECB reference currencies; default EUR) |
| symbols | string | no | 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 |
| date | string | no | Fixing date YYYY-MM-DD within the last ~90 days (default latest) |
| amount | number/string | no | Amount in base currency to convert |
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-12
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to | string | yes | 1–25 target zones, comma-separated (IANA names like Asia/Seoul, UTC, or abbreviations like KST, PST, CET) |
| from | string | no | Zone of the input local time (default UTC; ignored when time has an offset) |
| time | string | no | ISO 8601 date-time (2026-10-12T09:00, 2026-10-12T09:00:00+09:00), Unix seconds/ms, or now |
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 e
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Site URL or bare domain (https:// assumed); private/internal targets → 400 (not charged) |
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 cha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | 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) |
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. Ex
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | 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 | no | 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. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | 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 | no | Optional address whose token balance and share of total supply to include |
| spender | string | no | Optional spender; with holder, adds allowance(holder, spender). Needs holder. |
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=0x284f8abed91b5631ee
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hash | string | yes | Transaction hash on Base mainnet (0x + 64 hex). Unknown or not yet mined → 404 (not charged) |
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.0
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | Public http(s) URL of a web page, PDF, DOCX, HWP or HWPX (max 10 MB) |
| contentBase64 | string | no | Document bytes as base64 (alternative to url; max 10 MB decoded) |
| filename | string | no | Original file name, e.g. report.hwp (helps detection) |
| type | string | no | Optional expected type: html, text, pdf, docx, hwp, hwpx |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install 1gateway or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish 1gateway can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.