The MCP tool directory.

Orquestador de Enjambres Multi-Agente — /api/ping endpoint. Fee: $0.01 USDC via x402.

Generate a Portal Link scoped to an Organization.

Compute close rate across all products based on CRM conversion states.

Post a job to the AgentTrust job board. No fee, no funds held. Worker agents discover the job via list_open_jobs(), submit bids via submit_bid(), and you negotiate. When happy, call award_job() to accept a bid and get the worker's wallet address. Then create the bilateral XRPL escrow via create_escrow_vault(). Returns: status: "posted", job_id, expires_at, next_step.

Search court precedents (판례 목록 조회). Search Korean court precedents from Supreme Court and lower courts. Args: query: Search keyword (default "*" for all) display: Number of results per page (max 100, default 20) page: Page number (1-based, default 1) oc: Optional OC override (defaults to env var) type: Response format - "JSON" (default), "XML", or "HTML" search: Search type (1=case name, 2=full text, default 1) sort: Sort order - "lasc"|"ldes"|"dasc"|"ddes"|"nasc"|"ndes" org: Court type code (400201=Supreme Court, 400202=lower courts) curt: Court name (대법원, 서울고등법원, etc.) jo: Referenced law name (형법, 민법, etc.) gana: Dictionary search (ga, na, da, ...) date: Decision date (YYYYMMDD) prnc_yd: Decision date range (YYYYMMDD~YYYYMMDD) nb: Case number (comma-separated for multiple) dat_src_nm: Data source name (국세법령정보시스템, 근로복지공단산재판례, 대법원) pop_yn: Popup flag ("Y" or "N") Returns: Search results with precedent list or error Examples: Search for precedents mentioning "담보권": >>> prec_search(query="담보권", display=10) Search Supreme Court precedents: >>> prec_search(query="담보권", curt="대법원")

Retrieve court precedent full text (판례 본문 조회). Args: id: Precedent sequence number (판례일련번호) lm: Precedent name (optional) sections: Response detail level: - "summary": Returns 판시사항, 판결요지, 참조조문, 참조판례 only (~5KB). Excludes 판례내용 (full judgment text, often 15-25KB). **Recommended for PlayMCP** to stay under 20KB limit. - "full" or None: Returns everything including 판례내용 (default). oc: Optional OC override type: Response format - "JSON" (default), "XML", or "HTML" Returns: Full precedent text with details or error Examples: >>> prec_service(id="228541") >>> prec_service(id="228541", sections="summary") # PlayMCP-safe

Generate a .env-mcp configuration file for MCP server installation. Note: This tool works best with local CLI.

Find products with the highest agent readiness scores — products that are easiest for AI agents to integrate with. Sorted by compositeScore desc; supports skip/limit pagination. All readiness scores are 0-100, higher better. Calibration: <30 = not agent-ready (default minimumScore filter), 30-49 = early/limited, 50-69 = decent, 70-89 = strong, 90+ = exceptional. Ranking basis: compositeScore desc. Tier is NOT a tiebreaker here — buyer intent is technical fit, not paid placement. Every result carries { position (1-based, within the returned page), rank (0..1; 1.0 = top of this page) } so callers can merge results across tools consistently. Response: { products: [{ position, rank, slug, name, tagline, websiteUrl, tier (free|verified|featured), unverified (true on free only), verifiedAt (ISO; nullable), agentReadiness: { compositeScore, apiScore, protocolScore, sdkScore, integrationScore, dxScore } (each 0-100), mcp?: { hasMcpSupport, totalToolCount, serverCount } }] }.

Find B2B SaaS products that support a specific capability — an integration with a named service ('salesforce-integration'), a data format ('xrechnung-support'), an industry standard ('eclass-support'), or a compliance certification ('soc2'). Accepts either a canonical capability slug or natural language; resolves to a structured capability when possible. Ranking basis: tier weight (Featured > Verified > Free), then currentScore desc. Every result carries { position (1-based), rank (0..1; 1.0 = top, scales linearly down by ordinal position) } so callers can merge results across tools consistently. Response: { capability, matchType (none|exactSlug|canonicalSlug|nlpFallback — exactSlug & canonicalSlug are deterministic; nlpFallback is heuristic), resolvedFeatures[], products[] }. Each product: { position, rank, slug, name, tagline, websiteUrl, tier, unverified (true on free only), verifiedAt, evidence[] (per-claim: featureSlug, evidenceUrl, notes, source, confidence) }. Empty: { capability, matchType, message, suggestedSlugs[] } when no capability matched, or products: [] when capability matched but no products claim it yet.

Get full details for a product by slug, including MCP integration data and agent readiness scores. Response: { product: { slug, name, tagline, description, websiteUrl, logoUrl, pricingModel, currentScore (0-100), tier (free|verified|featured), unverified (true on free only), verifiedAt (ISO; absent if never crawled), categories[] }, mcp?: { hasMcpSupport, totalToolCount, totalUseCount, servers[] }, agentReadiness?: { compositeScore (0-100), aiSummary } }. Errors: { error: { code: 'not_found', ... } }.

Get MCP server setup instructions for a product. Returns available servers, their tools, connection details, and whether they support remote (hosted) access. Response when MCP support exists: { product: { slug, name, websiteUrl, tier, unverified, verifiedAt }, hasMcpSupport: true, totalToolCount, servers[], agentReadiness? }. Response when product exists but lacks MCP: { product: {...}, hasMcpSupport: false, message }. Errors: { error: { code: 'not_found', ... } }.

Search for B2B SaaS products by name OR by capability. The query is first resolved against the canonical capability taxonomy (e.g. 'salesforce-integration', 'xrechnung-support', 'soc2'); on hit, products that claim that capability are returned. Falls back to name/slug/tagline substring search. Optional category scope. Ranking basis: tier weight (Featured > Verified > Free), then currentScore desc. Every result carries { position (1-based), rank (0..1; 1.0 = top, scales linearly down by ordinal position) } so callers can merge results across tools consistently. Response: { query, matchType (none|exactSlug|canonicalSlug|nlpFallback), resolvedCapabilities[], products[] }. Each product carries { position, rank, tier (free|verified|featured), unverified (true only when tier=free; omitted otherwise — absence means trusted), verifiedAt (ISO timestamp of last claim crawl; absent if never crawled), currentScore (0-100), compositeScore (agent-readiness 0-100, nullable), matchedCapability (true if surfaced by capability path) }. Errors: { error: { code: 'not_found'|'bad_input', ... } }.

Get details about specific GitHub Projects resources. Use this tool to get details about individual projects, project fields, and project items by their unique IDs.

Tools for listing GitHub Projects resources. Use this tool to list projects for a user or organization, or list project fields and items for a specific project.

Add, update, or delete project items, or create status updates in a GitHub Project.

Returns the IP ranges used by the Ahrefs public web crawler, typically for allowlisting or firewall configuration. Use doc tool first to get the real input schema.

Returns the list of individual IP addresses currently used by the Ahrefs public web crawler. Use doc tool first to get the real input schema.

Get information on a specific pull request in GitHub repository.

Create and/or submit, delete review of a pull request. Available methods: - create: Create a new review of a pull request. If "event" parameter is provided, the review is submitted. If "event" is omitted, a pending review is created. - submit_pending: Submit an existing pending review of a pull request. This requires that a pending review exists for the current user on the specified pull request. The "body" and "event" parameters are used when submitting the review. - delete_pending: Delete an existing pending review of a pull request. This requires that a pending review exists for the current user on the specified pull request.

Get machine-readable payment instructions to purchase an OpenClaw Intel Pro API key ($9 one-time). Returns multiple payment options (PayPal, crypto) with direct action URLs. Pro key unlocks: full market reports (15+ metrics vs 3), 1000 API calls/day (vs 10 free), historical data access, and growth projections. ROI: One actionable insight from full data can save hours of manual research.

Run Python in a Pyodide sandbox with optional PEP 723 requirements.

奇门遁甲（Qimen Dunjia）是中国古代三式之一，被称为"帝王之学"。通过天时、地利、人和三维度分析时空能量场。 ## 核心概念 - **九宫**：坎(1)、坤(2)、震(3)、巽(4)、中(5)、乾(6)、兑(7)、艮(8)、离(9)，对应八方和五行 - **天盘/地盘**：天干在九宫中的分布，天盘为动态，地盘为静态 - **九星**：天蓬、天芮、天冲、天辅、天禽、天心、天柱、天任、天英 - **八门**：休门、生门、伤门、杜门、景门、死门、惊门、开门 - **八神**：值符、腾蛇、太阴、六合、白虎、玄武、九地、九天 - **值符/值使**：当前时刻的主星和主门，是判断吉凶的核心 ## 解读要点 1. **看值符值使**：值符星和值使门的状态决定总体吉凶 2. **看用神宫位**：根据用途找到对应宫位（如求财看生门所在宫） 3. **看三奇六仪**：乙丙丁为三奇（吉），戊己庚辛壬癸为六仪 4. **看格局**：天盘与地盘天干组合形成吉格（如龙遁、虎遁）或凶格（如击刑、入墓） 5. **看空亡**：落入空亡的宫位力量减弱 ## 常见用途 - 求财：重点看生门、戊 - 事业：重点看开门、值使 - 感情：重点看六合、天后 - 出行：重点看三奇得使、门迫否

Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best information you have.

Manage per-connection SQL rules: block dangerous patterns, require WHERE on large tables, log PII access. [ARCHITECT tier]

Return recent queries executed through ThinAir with timing, row counts, and status. [BUILD tier]

Execute a read-only SQL query against the target connection. ONLY SELECT / WITH / EXPLAIN permitted. Write dialect-appropriate SQL for the connection's engine — use PostgreSQL syntax for postgres connections (`SELECT NOW()`, `LIMIT`, `ILIKE`), T-SQL for mssql (`SELECT GETDATE()`, `TOP N`, `LIKE`), MySQL for mysql (`SELECT NOW()`, `LIMIT`). Response meta includes `connection` + `dialect` so you know which syntax worked; reuse that dialect in follow-up calls. Default LIMIT 100 unless the user asks for all rows.

Gets a list of pages contained in a database, filtered and ordered by the provided criteria.

Check current API usage, daily limit, plan name, and upgrade options.

Assess a request for risk using the Radar engine and receive a verdict.

You may optionally inform Radar that an authentication attempt or challenge was successful using this endpoint. Some Radar controls depend on tracking recent successful attempts, such as impossible travel.