feat(mcp): add OpenSea Arbitrum MCP server, tools, quickstart agent i…

[oxdev6]

Summary
Adds a production-ready OpenSea (Arbitrum-only) MCP server and integrates read‑only marketplace tools into the quickstart agent. Includes robust SSE/STDIO transports, input normalization, retry/rate‑limit handling, and Inspector‑friendly CORS. A headless SSE client is included for testing without the Inspector.
What’s included
New package: @vibekit/opensea-mcp-server
Endpoints: GET /sse, POST /messages + STDIO transport
CORS enabled; HTTP can be toggled via env
Retries with p-retry, HTTP via undici
Tools (Arbitrum only):
get_wallet_nfts, list_arbitrum_collections, get_collection
get_listings_by_collection, get_listings_by_asset (with optional collection fallback)
get_offers_by_asset (with optional collection fallback)
Input robustness: zod preprocess (trim/lowercase/coercions), snake_case + camelCase aliases, clearer validation
Agent integration: new openseaSkill registered in quickstart agent
Headless test client: scripts/sse-client.ts
Docs: package README with setup and testing
Env vars
Required: OPENSEA_API_KEY
Optional: ENABLE_HTTP=true|false, PORT, OPENSEA_BASE_URL
Inspector (local only): DANGEROUSLY_OMIT_AUTH=true
Run locally
From typescript/: pnpm install && pnpm build
Start server (HTTP/SSE):
cd typescript/lib/mcp-tools/opensea-mcp-server
pnpm build
ENABLE_HTTP=true OPENSEA_API_KEY=YOUR_KEY PORT=3051 node dist/index.js
Headless SSE test:
SSE_URL=http://localhost:3051/sse pnpm exec tsx scripts/sse-client.ts
Inspector (optional):
DANGEROUSLY_OMIT_AUTH=true npx -y @modelcontextprotocol/inspector
Open http://localhost:6274 → New session → Transport: HTTP Server (SSE) → URL: http://localhost:3051/sse → Connect

[ParastooGM]

Hey @oxdev6, thanks for your contribution. Would you mind sharing your Telegram handle so we can discuss this further? Could you also create an issue for this PR?

[oxdev6]

@frankkk876

…

On Mon, Sep 1, 2025 at 15:19 Parastoo Gol Mohammadi < ***@***.***> wrote: *ParastooGM* left a comment (EmberAGI/arbitrum-vibekit#204) <#204 (comment)> Hey @oxdev6 <https://github.com/oxdev6>, thanks for your contribution. Would you mind sharing your Telegram handle so we can discuss this further? — Reply to this email directly, view it on GitHub <#204 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAUHLQIFBGB5O4STTZU3Z433QQ2TPAVCNFSM6AAAAACFBD2RROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENBSGE2DQNBZGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ParastooGM]

Awesome, thank you. Could you create an issue for this PR as well, please?

[oxdev6]

Yes of course working in it right away

…

On Mon, Sep 1, 2025 at 16:56 Parastoo Gol Mohammadi < ***@***.***> wrote: *ParastooGM* left a comment (EmberAGI/arbitrum-vibekit#204) <#204 (comment)> Awesome, thank you. Could you create an issue for this PR as well, please? — Reply to this email directly, view it on GitHub <#204 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAUHLQOAV3BLGMIAM4XDCB33QRGAHAVCNFSM6AAAAACFBD2RROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENBSGQ3TONJXGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[oxdev6]

done submitting the issue take a look at it

…

On Mon, Sep 1, 2025 at 4:56 PM Parastoo Gol Mohammadi < ***@***.***> wrote: *ParastooGM* left a comment (EmberAGI/arbitrum-vibekit#204) <#204 (comment)> Awesome, thank you. Could you create an issue for this PR as well, please? — Reply to this email directly, view it on GitHub <#204 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BAUHLQOAV3BLGMIAM4XDCB33QRGAHAVCNFSM6AAAAACFBD2RROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENBSGQ3TONJXGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>