Home / MCP registry index / io.github.jsymen1290/pokt-agent-x402

POKT Agent Korea data (x402 paid)

io.github.jsymen1290/pokt-agent-x402 in the official MCP registry. Endpoint https://mcp-paid.pokt-agent.com/mcp.

The registry describes it as: Korean company due diligence, sanctions screening, Upbit/Bithumb events, HWP. Pay per call (x402).

We read its 29 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http pokt-agent-x402 https://mcp-paid.pokt-agent.com/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "pokt-agent-x402": {
      "url": "https://mcp-paid.pokt-agent.com/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"pokt-agent-x402","type":"http","url":"https://mcp-paid.pokt-agent.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

list_services kr_law_query kr_law_article kr_rates_query kr_fx_rate kr_figure_check dart_correction_impact kr_apartment_query kr_apartment_trend kr_exports_query kr_exports_pulse dart_events_query dart_changes backtest_reconcile kr_business_status kr_business_status_batch kr_business_day_add kr_business_days_count kr_business_day_check kr_web_read kr_address_normalize kr_company_due_diligence kr_company_resolve kr_crypto_events kr_crypto_ticker_status kr_hwp_to_markdown kr_entity_resolve kr_name_sanctions_screen kr_name_romanize

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-jsymen1290-pokt-agent-x402/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-jsymen1290-pokt-agent-x402)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
io.github.praneeth12098/x402-factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26