wiaaddress
Registry code: 8c54b5991e603f87
Address translation and Korean road-name address lookup. Results are machine-generated; not official postal confirmation.
- endpoint
- https://wiaaddress.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is wiaaddress live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is wiaaddress free to use?
- Not measured yet.
- What tools does wiaaddress have?
- 2 tools: address_translate, address_korea_lookup.
- Is wiaaddress safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 2 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
address_translate unknown never probed
Translate or transliterate a street address into another language using WIA Address (OpenStreetMap Nominatim geocoding; for Korean addresses also the Korean government road-name address API). Returns structured fields, not an official postal confirmation. The address text is sent to third-party geocoding services. Do not use for mail delivery decisions without verifying with the local postal service. (한국어: 주소를 다른 언어 표기로 변환합니다.)
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "address", "from", "to" ], "properties": { "to": { "type": "string", "pattern": "^[a-zA-Z]{2,3}(-[A-Za-z0-9]{2,8})?$", "description": "Language code for the output (e.g. en, ja, ko)" }, "from": { "type": "string", "pattern": "^[a-zA-Z]{2,3}(-[A-Za-z0-9]{2,8})?$", "description": "Language code of the input address (ISO 639-1/2, e.g. ko, en, ja)" }, "address": { "type": "string", "maxLength": 200, "minLength": 3, "description": "Full street address in any language, e.g. '서울 강남구 테헤란로 152' or '1600 Pennsylvania Avenue NW, Washington DC'" } }, "additionalProperties": false }arguments 28 linesaddress_korea_lookup unknown never probed
Normalize a Korean address using the Korean government road-name address data: returns road-name address, lot-number (jibun) address, postal code, building name and the official English road-name address. Does not return coordinates. The keyword is sent to the government address service via WIA Address. (한국어: 도로명·지번·우편번호·공식 영문 표기를 조회합니다.)
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "keyword" ], "properties": { "keyword": { "type": "string", "maxLength": 100, "minLength": 2, "description": "Korean address keyword, e.g. '서울 강남구 테헤란로 152' or '강남파이낸스센터'" } }, "additionalProperties": false }arguments 16 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id8c54b5991e603f87.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/8c54b5991e603f87/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/8c54b5991e603f87?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.