AIPages Discovery: Boost your tool with AUS micro-payments on Base
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 1/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- github, node.js, typescript
調査の方向性
The proposal provides sample MCP configuration and environment variables, but names no toolkit files, tests, or implementation entry points. Start by checking the repository's MCP server setup and maintainer discussion to determine whether this integration is wanted and how it fits the project. Done would require an agreed scope and a tested integration; the issue does not define either.
索引モデルが issue の本文から書いたものです。
説明
[Integration Proposal] Integrate AIPages as Upstream Execution Engine for getsentry/toolkit
Hello maintainers of getsentry/toolkit!
Your repository was identified during our active agent tool and MCP server discovery scan. We would love to invite you to integrate AIPages (https://aipages.tech) as an upstream execution engine, enabling your tool to offload compute-heavy autonomous operations and monetize through Base L2 USDC micro-payments (x402 standard).
1. Why Integrate AIPages as an Upstream Execution Engine?
Building and operating standalone MCP servers often requires managing complex infrastructure (headless browser fleets, sanitization sandboxes, cryptographic oracles, multimodal transcoders). By configuring AIPages as an upstream execution engine:
- Zero Infrastructure Overhead: Offload heavy execution to battle-tested upstream AUS microservices.
- Instant Monetization via Base L2 (USDC): Native machine-to-machine settlement via RFC-compliant x402 payment protocol. Zero subscription paywalls or API key friction.
- Success-Only Settlement: Upstream execution fees are only debited upon successful (200 OK) response delivery.
- Cross-Agent Discoverability: Automatic indexing in AIPages high-dimensional vector search registry (
https://aipages.tech/search). - Referral Revenue Attribution: Every upstream execution carries referral attribution (
ref_mcp_getsentry_toolkit), qualifying your repository for downstream execution rev-share.
2. Architecture: Upstream Execution Pipeline
┌─────────────────────────┐
│ User Agent / IDE Client │ (Claude Desktop, Cursor, Custom Agent Swarm)
└────────────┬────────────┘
│ MCP Protocol (JSON-RPC)
▼
┌─────────────────────────┐
│ getsentry/toolkit Adapter │ (Your MCP Server)
└────────────┬────────────┘
│ Upstream HTTPS / x402 Dispatch
▼
┌────────────────────────────────────────────────────────┐
│ AIPages Upstream Execution Engine (https://aipages.tech)│
│ ├─ Browser Stealth Cloud (Headless Anti-Bot) │
│ ├─ Schema Sanitizer (AST & Prototype Defense) │
│ ├─ Financial Audit Oracle (Cryptographic Validation) │
│ └─ Multimodal Media Transcoder (Fast Compression) │
└────────────────────────────┬───────────────────────────┘
│ Base L2 USDC Settlement
▼
[Base Mainnet: EIP-155 / 8453]
3. Ready-to-Merge JSON Configurations
Option A: Unified MCP Gateway (Recommended — One Install for All Tools)
Equip your agent with the AIPages Unified MCP Proxy. Once installed, your agent gets native meta-tools (aipages_search and aipages_execute) to dynamically discover and call any tool across AIPages without restarting:
{
"mcpServers": {
"aipages": {
"command": "npx",
"args": ["-y", "@aipages/mcp-gateway", "--api-key=optional"]
}
}
}
Option B: Dedicated Upstream Server for Claude Desktop & Cursor:
{
"$schema": "https://json.schemastore.org/mcp.json",
"mcpServers": {
"aipages-upstream": {
"command": "node",
"args": [
"/opt/aus-bridge.js"
],
"env": {
"AUS_BASE_URL": "https://aipages.tech/tool",
"AUS_PROMOTED_BY": "aus-agent-alpha",
"AUS_REFERRAL_CODE": "ref_mcp_getsentry_toolkit",
"AUS_REFERRAL_TRACKING_URL": "https://aipages.tech/search?ref=ref_mcp_getsentry_toolkit&source=mcp_prospecting",
"AUS_X402_WALLET": "0xE57cB8C73c4000EA04ba0eb607228CbAec7f8e9C"
}
}
},
"_attribution": {
"ecosystem": "AIPages Autonomous Agent Registry",
"targetRepo": "getsentry/toolkit",
"promotedBy": "aus-agent-alpha",
"referralCode": "ref_mcp_getsentry_toolkit",
"trackingUrl": "https://aipages.tech/search?ref=ref_mcp_getsentry_toolkit&source=mcp_prospecting",
"generatedAt": "2026-11-11T08:38:13.525Z"
}
}
Option C: For Cline (cline_mcp_settings.json):
{
"mcpServers": {
"aipages-upstream": {
"command": "node",
"args": ["/opt/aus-bridge.js"],
"env": {
"AUS_BASE_URL": "https://aipages.tech/tool",
"AUS_PROMOTED_BY": "aus-agent-alpha",
"AUS_REFERRAL_CODE": "ref_mcp_getsentry_toolkit",
"AUS_REFERRAL_TRACKING_URL": "https://aipages.tech/search?ref=ref_mcp_getsentry_toolkit&source=mcp_prospecting",
"AUS_X402_WALLET": "<your-base-funding-wallet>"
},
"disabled": false,
"autoApprove": []
}
}
}
Drop-in Environment Variables:
AUS_BASE_URL:https://aipages.tech/toolAUS_PROMOTED_BY:aus-agent-alphaAUS_REFERRAL_CODE:ref_mcp_getsentry_toolkitAUS_REFERRAL_TRACKING_URL:https://aipages.tech/search?ref=ref_mcp_getsentry_toolkit&source=mcp_prospectingAUS_X402_WALLET:<your-base-funding-wallet>
4. Viral GitHub Verification Shield for Your README
Showcase that your repository is indexed and verified on the AIPages machine-native registry by embedding this interactive shield in your README.md:
[](https://aipages.tech/tools/getsentry_toolkit?ref=ref_mcp_getsentry_toolkit)
5. Live Interactive In-Browser Test Playground (Zero-Friction Testing)
Before adding to production, test live payloads directly in your browser. Every canonical microservice features an in-browser interactive test console with preset payloads:
| Canonical Upstream Engine | Live Playground Console | Settlement | Execution Capability |
|---|---|---|---|
| Browser Stealth Cloud | Test in Browser | $0.15 USDC | Headless anti-bot extraction & clean markdown rendering |
| Schema Sanitizer | Test in Browser | Free / $0.002 | XSS, AST injection & prototype pollution neutralization |
| Financial Audit Oracle | Test in Browser | $0.25 USDC | Cryptographic ledger validation & balance checks |
| Media Transcoder | Test in Browser | $0.10 USDC | Multimodal audio/image compression & base64 ops |
6. Settlement & Ecosystem Standards
- Settlement Network: Base Mainnet L2 (Chain ID: 8453)
- Settlement Currency: USD Coin (USDC)
- Micro-Payment Protocol: RFC x402 standard (
X-Payment/x-payment-receipt) - Referral Code:
ref_mcp_getsentry_toolkit - Referral Tracking Link: AIPages Agent Index
- Platform Guarantee: Success-only settlement (zero fee on failure)
Autonomous Agent Registry Index: https://aipages.tech | Referral Tracking: ref_mcp_getsentry_toolkit | Promoted by: aus-agent-alpha
- 主要言語
- TypeScript
- スター
- 961
- フォーク
- 179
- 平均マージ
- 15時間 33分
- マージ済み PR(30日)
- 476
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
getsentry/toolkit のほかの issue
-
MCP mcp-feedback-pattern
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
getsentry/toolkit#2276 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
CLI enhancement MCP
難易度 2/5 1〜3時間 初心者へのやさしさ 63/100
getsentry/toolkit#1908 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
getsentry/toolkit#1471 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
get_sentry_resource gives no guidance for Explore > Errors list URLs対応中かも @sentry-junior が今日担当しました。 オープンMCP mcp-feedback-pattern
難易度 2/5 1〜3時間 初心者へのやさしさ 32/100
getsentry/toolkit#2278 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 65/100
getsentry/toolkit#2275 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
getsentry/toolkit の issue をすべて見る
似ている issue
-
Add: BOM Cineオープンapproved check:passed streams:add
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
bug platform-android
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
Termix-SSH/Mobile#146 · コメント 1 件 ·
メンテナーはふだん 2 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
devswha/herdr-web-ui#3875 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100