AIPages Discovery: Boost your tool with AUS micro-payments on Base
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 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 分钟
- 30 天内合并 PR
- 476
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 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