Task402 Agent Evidence Tools MCP server
2026년 10월 12일 커밋유료 툴셋을 사용하여 PDF, 공개 웹페이지, OpenAPI 계약 및 Base 체인 데이터로부터 AI agent에게 검증 가능한 증거를 제공합니다.
다른 이름 xbckz/task402, task402
- 스타
- 0
- Tools
- 4
- 다운로드, 30일
- —
- 최신 버전
- 0.3.2
- 마지막 커밋
- 2026년 10월 12일
- 라이선스
- MIT
Task402 Agent Evidence Tools MCP란?
유료 툴셋을 사용하여 PDF, 공개 웹페이지, OpenAPI 계약 및 Base 체인 데이터로부터 AI agent에게 검증 가능한 증거를 제공합니다. 4개 도구를 제공합니다. 예: generate_pdf, web_evidence, inspect_openapi.
프로젝트 README에서 생성된 요약
Task402 Agent Evidence Tools MCP server 정보
Task402 Agent Evidence Tools는 다양한 데이터 소스로부터 AI agent에게 검증 가능한 증거를 제공합니다. 개발자는 Streamable HTTP 엔드포인트를 통해 20개의 도구가 포함된 호스팅 MCP 서비스에 agent를 연결할 수 있습니다. 이를 통해 로컬 서버나 탐색을 위한 API key 없이도 Cursor 및 VS Code와 같은 클라이언트와 호환됩니다. 이 서비스는 agent가 공개 웹페이지, OpenAPI 계약 및 Base 체인 데이터와 상호작용하여 특정 정보를 검색할 수 있도록 지원합니다.
사용자는 Base 네트워크의 x402 v2 USDC를 사용하는 유료 모델을 통해 전문적인 기능을 이용할 수 있습니다. 탐색은 무료이지만 web_evidence, inspect_openapi, get_chain_balance와 같은 특정 도구는 승인된 결제가 필요합니다. 시스템은 보안을 위해 설계되었으며, 모든 트랜잭션에 대해 명시적인 지갑 승인을 요구하고 개인 키를 절대 요청하지 않습니다. ingest_document 작업을 통해 PDF가 인덱싱되면, agent는 search_document, verify_document_citation, compare_pdfs와 같은 고급 도구를 사용하여 심층 분석을 수행할 수 있습니다.
활용 사례
- 1웹 기반 정보 검증agent가 공개 HTTPS 페이지에서 제한된 범위의 증거를 검색하여 자신의 주장을 뒷받침할 수 있습니다.
- 2심층 PDF 조사 수행문서를 인덱싱한 후, agent는 텍스트를 검색하거나 특정 인용구를 검증할 수 있습니다.
- 3블록체인 데이터 쿼리agent가 Base 체인에서 잔액이나 트랜잭션 세부 정보를 확인하기 위한 읽기 전용 작업을 수행할 수 있습니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Task402 Agent Evidence Tools MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Task402 Agent Evidence Tools MCP 설치
$ claude mcp add --transport http task402 https://task402.xyz/mcpCursor에 Task402 Agent Evidence Tools MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"task402": {
"url": "https://task402.xyz/mcp"
}
}
}VS Code에 Task402 Agent Evidence Tools MCP 설치
.vscode/mcp.json
{
"servers": {
"task402": {
"type": "http",
"url": "https://task402.xyz/mcp"
}
}
}VS Code CLI에 Task402 Agent Evidence Tools MCP 설치
$ code --add-mcp '{"name":"task402","type":"http","url":"https://task402.xyz/mcp"}'Codex에 Task402 Agent Evidence Tools MCP 설치
$ codex mcp add task402 --url https://task402.xyz/mcpCodex config.toml에 Task402 Agent Evidence Tools MCP 설치
~/.codex/config.toml
[mcp_servers.task402] url = "https://task402.xyz/mcp"
Gemini CLI에 Task402 Agent Evidence Tools MCP 설치
$ gemini mcp add -s user --transport http task402 https://task402.xyz/mcpGemini settings.json에 Task402 Agent Evidence Tools MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"task402": {
"url": "https://task402.xyz/mcp",
"type": "http"
}
}
}Task402 Agent Evidence Tools MCP 도구 4
README에서 감지됨generate_pdfweb_evidenceinspect_openapiget_pdf_job
| generate_pdf | — | |
| web_evidence | — | |
| inspect_openapi | — | |
| get_pdf_job | — |
구성
MCP_ALLOWED_ORIGINSPAYMENTS_MODEPRICE_CHAIN_USDPRICE_DOCUMENT_USDPRICE_OPENAPI_USDPRICE_USDPRICE_WEB_EVIDENCE_USDPUBLIC_BASE_URLX402_ASSETX402_FACILITATOR_URLX402_NETWORKX402_PAY_TO
| 이름 | 설명 | 유형 |
|---|---|---|
| MCP_ALLOWED_ORIGINS | — | |
| PAYMENTS_MODE | — | |
| PRICE_CHAIN_USD | — | |
| PRICE_DOCUMENT_USD | — | |
| PRICE_OPENAPI_USD | — | |
| PRICE_USD | — | |
| PRICE_WEB_EVIDENCE_USD | — | |
| PUBLIC_BASE_URL | — | |
| X402_ASSET | — | |
| X402_FACILITATOR_URL | — | |
| X402_NETWORK | — | |
| X402_PAY_TO | — |
자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능xbckz/task402 is public and reachablegithub.com/xbckz/task402 ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)MITspdx.org/licenses/MIT.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-10-12github.com/xbckz/task402 ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음4 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨No tool named like delete, drop or exec통과
- 원격 엔드포인트가 MCP 핸드셰이크에 응답Endpoint did not answer initialize: HTTP 530결함 발견
README
GitHub에서 보기Task402 Agent Evidence Tools
Give agents bounded evidence from PDFs, public webpages, OpenAPI contracts, and Base chain data. Connect to the hosted 20-tool MCP service at https://task402.xyz/mcp; no local server, API key, or wallet is needed for discovery. Paid calls use x402 v2 USDC on Base. Connecting an MCP host does not automatically give it a payment signer.
Connect your agent
For Cursor, merge examples/cursor.mcp.json into .cursor/mcp.json. For VS Code, merge examples/vscode.mcp.json into .vscode/mcp.json. Other Streamable HTTP clients can use:
{
"mcpServers": {
"task402": { "url": "https://task402.xyz/mcp" }
}
}
Initialize the connection and run tools/list to inspect executable schemas. With Node.js 24 and this repository's dependencies installed, npm run discover performs discovery through the official MCP SDK and prints tool names only. It never calls a paid tool or signs a payment.
Every hosted tool advertises a tool-specific output schema, parameter descriptions, and MCP safety annotations. Agents can therefore plan the result shape and retry behavior from tools/list before approving any x402 payment.
| Tools | Billing at the 12 October 2026 live check |
|---|---|
generate_pdf |
$0.01 per PDF |
web_evidence |
$0.005 per public HTTPS page |
inspect_openapi |
$0.001 per specification |
plan_api_request, diff_openapi |
$0.002 per call |
get_chain_balance, get_chain_transaction, get_erc20_balance |
$0.001 per read |
get_pdf_job |
Included with generation; requires the job capability |
inspect_pdf, get_document_map, search_document, batch_search_document, prepare_document_context, extract_document_fields, read_document, verify_document_citation, compare_pdfs, validate_pdf_text, render_pdf_page_region |
Included after paid PDF indexing; requires document capabilities |
PDF indexing is the separate REST operation POST /v1/documents ($0.01 per PDF); binary upload is not an MCP tool. Generated PDF download is also REST-only. Read /v1/pricing and the payment challenge for current terms before approving payment. Native-text PDF tools do not provide OCR or verify factual truth.
Start with docs/FIRST-PAID-CALL.md for a challenge, signed retry, and result workflow. Use docs/PUBLISHING.md to publish the repository and remote MCP metadata.
Service architecture
This project converts Markdown into paginated PDF files through one shared service used by REST and MCP. The local runner uses Playwright Chromium and SQLite; the Cloudflare Worker adapter uses Browser Run Quick Actions, D1, and R2. The live payment path uses the official x402 SDK facilitator client, verifies before rendering, and settles only after a PDF artifact is stored.
The paid operations are generate_pdf, ingest_document, web_evidence, OpenAPI inspection/planning/diffing, and fixed-method Base chain reads. Retrieval, citation, batch search, bounded context preparation, and explicit-label field matching are included after indexing. Web evidence is public HTTPS HTML/text only, OpenAPI tools accept caller-supplied JSON and local references only, and chain tools never sign or submit transactions. Input HTML is not executed, remote images and other external resources are omitted or blocked, and hyperlinks are preserved in generated PDFs but never fetched during rendering.
Distribution metadata, conversion guidance, and channel-ready copy live in docs/MARKETING.md and docs/LAUNCH-KIT.md; the public MCP directory metadata is in server.json, glama.json, and lhm.plugin.json for LobeHub.
The detailed agent, discovery, operations, deployment, operator-stats, and security guide is docs/AGENT-GUIDE.md.
Use the hosted MCP server
No local process is required. Add the Streamable HTTP endpoint to an MCP-compatible client:
{
"mcpServers": {
"task402": {
"type": "http",
"url": "https://task402.xyz/mcp"
}
}
}
The server is discoverable without payment. Paid operations return an x402 v2 challenge; the client must inspect the network, USDC asset, recipient, amount, resource, and timeout, obtain explicit wallet approval, then retry the same request with the signed payment. Task402 never receives a private key and never signs or submits transactions for the caller. Start with the first paid call, then use examples/agent-flow.ts for a complete injected-signer flow.
What is included
| Capability | Payment | Interface |
|---|---|---|
| Generate a paginated PDF from Markdown | $0.01 | REST, MCP |
| Index one native-text PDF | $0.01 | REST |
| Search, cite, compare, validate, map, read, extract fields, prepare context, and render | Included after indexing | REST, MCP |
| Bounded public-page evidence | $0.005 | REST, MCP |
| OpenAPI inspect, request plan, and diff | $0.001–$0.002 | REST, MCP |
| Read-only Base balance, transaction, and ERC-20 data | $0.001 | REST, MCP |
Prices, limits, schemas, and payment terms are machine-readable at /v1/pricing. The service does not provide OCR, JavaScript page rendering, arbitrary API execution, transaction signing, or visual/legal PDF redlining.
The remote MCP server metadata is version 0.3.2 in server.json. In the 2026-10-12 audit, the official Registry served 0.2.0; publishing the new metadata requires the domain publisher proof key, which is intentionally not stored in this workspace. Recheck the live Registry record before claiming the release is published. Paid REST and MCP challenges include x402 Bazaar discovery metadata, and the production facilitator is https://facilitator.openx402.ai.
Public discovery pages are available at https://task402.xyz/, /docs#first-paid-call, /llms.txt, /demo, /v1/tools, /openapi.json, /v1/pricing, /.well-known/x402.json, /.well-known/mcp/server-card.json, /.well-known/ai-plugin.json, and /sitemap.xml. They give agents and directory crawlers a clear entry point without requiring payment or an operator credential. Registry publication improves discoverability for clients that sync the MCP Registry; it does not create synthetic traffic or guarantee calls.
The public quickstart includes focused workflows for citation verification, PDF revision comparison, and reducing PDF context before model calls. Copy-paste client files are in examples/agent-flow.ts, examples/cursor.mcp.json, and examples/vscode.mcp.json. The TypeScript example obtains unsigned generation and indexing challenges and exposes explicit retry methods for a separately approved wallet payload; it never signs or submits a payment automatically.
When you are ready for one controlled live payment, follow docs/TEST-TRANSACTION.md. It requires an external wallet signer and never asks for a private key.
For a disposable local test wallet, the repository also includes a guarded terminal helper: npm run test:live. It validates the live Base/USDC challenge before signing, requires TASK402_CONFIRM=YES, downloads the PDF, and never prints the payment payload or capability. See the terminal section of the test guide for setup and cleanup.
To reproduce an MCP agent exactly, use npm run test:agent; it performs discovery, receives the structured x402 challenge, signs through the official EVM client, retries with _meta["x402/payment"], checks the job through get_pdf_job, and downloads the result.
Local development
Use Node.js 24 or newer (verified with Node 24.13; local durable state uses node:sqlite). From this directory:
npm ci
Copy-Item .dev.vars.example .dev.vars
npm run setup:browser
npm run dev
The local server binds only to 127.0.0.1:8787 and accepts only the matching loopback/localhost Host authority (plus the configured public authority in live mode). The local web-evidence adapter resolves every hostname before fetching and rejects private, loopback, link-local, and reserved DNS destinations; the hosted Worker relies on its platform egress boundary plus the same URL checks. The example .dev.vars enables an explicit no-payment development bypass, and the bypass exists only in src/local.ts; src/worker.ts rejects it unconditionally. If .dev.vars is absent, the server starts with payments unconfigured and paid generation fails closed. Local jobs and artifacts are durable under .data/ and are ignored by Git.
If Playwright cannot find its pinned Chromium download on your machine, point it to an installed Chromium executable before starting the local process:
$env:BROWSER_EXECUTABLE_PATH = "C:\path\to\chrome.exe"
npm run dev
Generate and download a sample PDF:
$body = @{ title = "Quarterly Report"; markdown = "# Summary`n`n| Metric | Value |`n| --- | ---: |`n| Revenue | 42 |" } | ConvertTo-Json
$job = Invoke-RestMethod -Method Post -Uri http://127.0.0.1:8787/v1/pdf `
-Headers @{ "Idempotency-Key" = "report-2026-q3-0001" } `
-ContentType "application/json" -Body $body
$job | Format-List
Invoke-WebRequest -Uri $job.downloadUrl `
-Headers @{ Authorization = "Bearer $($job.capability)" } `
-OutFile .\report.pdf
The capability is a bearer secret. Keep it in memory, do not log it, and send it only to the returned status/download URLs. Status and download access require Authorization: Bearer <capability> (or X-Job-Capability); a job ID or idempotency key alone does not authorize access.
API and limits
| Route | Purpose |
|---|---|
GET /v1/pricing |
Machine-readable operation, price, payment mode, and size/TTL limits |
GET /.well-known/x402 |
Same discovery document at a well-known path |
GET / and GET /docs |
Public service overview and agent quickstart |
GET /llms.txt and GET /sitemap.xml |
Compact agent-readable metadata and crawler discovery |
POST /v1/pdf |
Generate a PDF; requires Idempotency-Key; live mode uses x402 v2 PAYMENT-SIGNATURE |
GET /v1/jobs/{jobId} |
Read authorized job state |
GET /v1/jobs/{jobId}/download |
Download an authorized completed PDF |
GET /v1/admin/stats |
Password-protected aggregate tool statistics; optional ?hours=24 |
GET /admin |
Mobile-friendly password form for viewing the protected stats endpoint |
POST /mcp |
MCP Streamable HTTP endpoint with PDF, web, OpenAPI, and Base read-only tools |
POST /v1/documents |
Paid raw PDF indexing for deterministic native-text operations |
GET /v1/documents/{documentId} and /map |
Inspect document metadata or read its page map |
POST /v1/documents/{documentId}/search, /batch-search, /context, /fields, /read, /citation, /validate |
Search, build cited context, read selected pages, verify a text quote, or validate stated expectations |
POST /v1/documents/compare |
Compare two separately authorized PDFs by page and normalized native text |
GET /v1/documents/{documentId}/pages/{page}/render |
Render a bounded page crop to PNG |
POST /v1/web/evidence |
Paid public HTTPS page extraction with bounded text, links, source hash, and prompt-injection warning |
POST /v1/openapi/inspect |
Paid OpenAPI operation, parameter, request-body, security, and local-reference inspection |
POST /v1/openapi/request-plan and /v1/openapi/diff |
Paid safe request planning and deterministic API contract comparison; no requests are executed |
POST /v1/chain/balance, /v1/chain/transaction, /v1/chain/erc20-balance |
Paid read-only Base RPC utilities; no signing or fund movement |
The default limits are a 256 KiB request body, 240 KiB normalized Markdown, 160 title characters, 20,000 Markdown lines, 20 MiB PDF output, a 24-hour artifact lifetime, and a 90-second render deadline. The PDF uses A4 layout, repeats table headers, keeps rows together when possible, and includes page numbers. Cleanup runs once an hour in Cloudflare, and on startup and hourly in the local process. Cleanup batches are bounded; expired capabilities stop working immediately, while physical deletion can take additional batches. Uncertain settlements retain their artifacts for operator reconciliation.
Local PDF inspection and retrieval
The deployed Worker exposes the deterministic PDF document operations through an isolated Cloudflare Container parser. The Worker keeps capabilities, D1 metadata, R2 source/index objects, validation, and cleanup; the Container performs native PDF.js extraction and bounded page rendering with outbound Internet disabled. Local development continues to use the same operations directly through the Node.js parser.
Upload a raw PDF with a caller-generated idempotency key and separate high-entropy recovery secret (the recovery secret scopes that key to the caller). Save the returned capability and recovery secret in the caller's secret store; the server never returns the recovery secret. Reuse both keys only to recover the same upload after a lost response. The idempotency key alone cannot disclose an existing document capability.
$recovery = [Convert]::ToHexString([Security.Cryptography.RandomNumberGenerator]::GetBytes(32)).ToLowerInvariant()
$doc = Invoke-RestMethod -Method Post -Uri http://127.0.0.1:8787/v1/documents `
-Headers @{ "Idempotency-Key" = "research-pdf-2026-0001"; "X-Document-Recovery-Key" = $recovery; "X-File-Name" = "research.pdf" } `
-ContentType "application/pdf" -InFile .\research.pdf
$headers = @{ Authorization = "Bearer $($doc.capability)" }
Invoke-RestMethod -Uri $doc.inspectUrl -Headers $headers
Invoke-RestMethod -Method Post -Uri "$($doc.inspectUrl)/search" -Headers $headers `
-ContentType "application/json" -Body '{"query":"revenue","limit":5}'
Invoke-RestMethod -Method Post -Uri "$($doc.inspectUrl)/read" -Headers $headers `
-ContentType "application/json" -Body '{"pages":[1,2]}'
The returned capability is a bearer secret. Keep it private and send it only in the Authorization header to the returned URLs. Binary upload accepts at most 20 MiB and 100 pages. Parsing builds a bounded local index containing metadata, page labels and sizes, bookmarks, native text blocks with normalized bounding boxes, form-field names/types/values, annotation counts, and embedded-attachment filenames/sizes. The index is limited to 8 MiB and 50,000 text blocks. GET .../map?page=1 includes up to 500 positioned blocks for that page; the default map returns compact page summaries. Source PDF bytes and the extracted index are stored durably in .data/document-objects/ and .data/documents.sqlite and removed at expiry; the default retention is 24 hours (DOCUMENT_TTL_SECONDS can extend it to at most seven days).
The MCP endpoint adds inspect_pdf, get_document_map, search_document, batch_search_document, prepare_document_context, extract_document_fields, read_document, verify_document_citation, compare_pdfs, validate_pdf_text, and render_pdf_page_region when the deployed parser Container is configured. MCP does not upload binary content; first use the REST upload and then pass its document ID and capability to the tools.
Search is case-insensitive exact matching after whitespace normalization. Reading is capped at 10 pages and 32,000 output characters. Citation checks establish only that normalized text appears on the stated page and return nearby text blocks and their bounding boxes; they do not establish truth or visual reading order. Comparison reports page-level normalized-text changes and does not inspect image, visual, metadata, or signature differences. Validation checks parser readability, optional page count, and required text only. Page crops use normalized page fractions and are limited to four million raster pixels and 4 MiB of PNG output.
No OCR, table-structure extraction/query, form filling, attachment download, PDF/A conformance test, or cryptographic signature validation is provided. Sparse native text is reported as a warning; scanned pages do not receive invented text. PDF links are retained as text and never fetched. A PDF signature marker is surfaced as metadata only; trust and validity are not checked.
Native PDF parsing and rendering run in the isolated parser Container. The Worker admits one parser task at a time, enforces a 60-second startup/processing deadline, and destroys the Container after each task to reset process and filesystem state. Concurrent uploads or renders receive 503 and should retry shortly with the same recovery/idempotency keys. Upload, page, text, index, output, and instance memory limits also apply; the Container has no outbound Internet access and receives no payment or capability secrets. OCR, visual semantic comparison, PDF/A conformance, and cryptographic signature verification remain unsupported and are reported explicitly by the validation tool.
The idempotency key is scoped to the verified payer in live mode and bound to the normalized input and payment payload. Reusing it with different content or payment returns 409; a duplicate exact payment authorization is rejected using the EVM network/asset/payer/authorization nonce. Payment replay tombstones are retained for at least 30 days after both the artifact expiry and authorization expiry. The same completed request can recover its original capability during the job lifetime without another render or settlement.
REST clients receive x402 v2 terms in a 402 response and a standard PAYMENT-REQUIRED header. MCP clients receive the same PaymentRequired object as an isError: true tool result, and send payment through params._meta["x402/payment"]; a settled tool result includes _meta["x402/payment-response"].
MCP client with a protected wallet
examples/mcp-client.ts demonstrates the official MCP SDK Streamable HTTP client and the x402 MCP transport fields. It takes an ApprovedWallet adapter from the caller and has no private-key field, environment key, or signing implementation. Implement that adapter with a hardware wallet, HSM, KMS, or a separately sandboxed wallet service; have the signer enforce the expected network, USDC asset, recipient, amount ceiling, and nonce policy before it signs. Do not add a long-lived private key to the MCP client or repository.
The example performs an unpaid call to obtain the challenge, asks the injected signer for a payload, retries with _meta["x402/payment"], then returns the job capability for an authenticated download. This is a minimal happy-path example: a production client should persist the idempotency key and exact signed payment payload securely so it can retry the same request, and should retain recovery details returned after an uncertain settlement. The local development bypass does not create or settle chain payments; use a properly configured test wallet and testnet facilitator for an end-to-end x402 transfer.
Task402 Agent Evidence Tools MCP 질문
Task402 Agent Evidence Tools MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http task402 https://task402.xyz/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Task402 Agent Evidence Tools MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Task402 Agent Evidence Tools MCP는 어떤 도구를 제공하나요?
4개 도구를 제공합니다. 예: generate_pdf, web_evidence, inspect_openapi, get_pdf_job.
도구를 탐색하기 위해 API key나 지갑을 제공해야 하나요?
아니요, 탐색은 무료이며 로컬 서버, API key 또는 지갑이 필요하지 않습니다.
유료 도구의 비용은 어떻게 청구되나요?
유료 호출은 Base 체인의 x402 v2 USDC를 사용하며, agent는 각 트랜잭션에 대해 명시적인 지갑 승인을 제공해야 합니다.
서비스에서 PDF에 대한 OCR을 제공하나요?
아니요, native-text PDF 도구는 OCR을 제공하거나 사실 여부를 검증하지 않습니다.