Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL)

Titan Frameworks

Paid MCP that reviews and rewrites LangChain, LlamaIndex, Ollama, and XRPL code against current APIs — plus runnable examples, import lookup, and tx skeletons that never submit. Live docs are still included.

Live Streamable HTTP: https://titan-frameworks-production.up.railway.app/mcp Paid with x402: $0.001 USDC on Base or 1000 drops XRP / 0.001 RLUSD on XRPL mainnet.

Agent discovery: llms.txt · Smithery smithery.yaml · MCP Registry server.json

Tools

Prompts: migrate_framework_code, diagnose_stack_trace, start_from_example.

Pick one: source about to run → review_framework_code; need a patched file → rewrite_framework_code; stack trace → diagnose_framework_error; know the symbol → resolve_symbol; need a full file → fetch_working_example; topic fragment → fetch_latest_syntax; concept → search_ai_framework_docs; XRPL tx → draft_xrpl_intent_tx; which frameworks → list_supported_frameworks; all deprecations → list_known_deprecations.

Connect a client

{

"mcpServers": { "titan-frameworks": { "url": "https://titan-frameworks-production.up.railway.app/mcp" } } }

x402-capable clients send PAYMENT-SIGNATURE / X-PAYMENT after a 402. Local stdio (titan-frameworks / npm run dev) does not charge.

To pay production from Cursor, enable titan-frameworks-paid in MCP settings (runs scripts/cursor-x402-proxy.ts, signs Base USDC from EVM_PRIVATE_KEY in .env, cap X402_PROXY_MAX_CALLS default 25). Check the proxy with npx tsx scripts/cursor-x402-proxy.ts --check.

HTTP endpoints

Run locally (stdio)

cd titan-frameworks

npm install npm run dev

Project config is in .cursor/mcp.json. Seed docs ship in src/data/seed-fallback.json.

npm run index-docs

Production re-indexes automatically when the live index is older than 24 hours. /admin can still trigger a crawl immediately.

HTTP mode (Vercel / Railway)

npm run dev:http

POST http://127.0.0.1:3333/mcp

npm run build

npm start

Railway uses railway.toml (npm run start). Vercel rewrites to api/index.ts.

x402 micropayments

Production billing is on. Unpaid tools/call on POST https://titan-frameworks-production.up.railway.app/mcp returns 402, except list_supported_frameworks which is free. initialize, ping, and tools/list are free so directories can health-check the connector.

A raw wallet transfer is not an x402 proof. Clients retry /mcp with PAYMENT-SIGNATURE / X-PAYMENT. Local stdio (npm run dev) does not charge.

To reproduce the gate locally: X402_ENABLED=true (mock) plus X402_USDC_LIVE=true / X402_XRPL_LIVE=true for live verify/settle.

Password-gated admin

Production dashboard: https://titan-frameworks-production.up.railway.app/admin

It is not a public stats page. Login is a password checked against ADMIN_SECRET_KEY. Unauthenticated /api/admin/* calls return 401. The old public /admin/api/stats route is gone (404).

Layout

src/app/           Next.js admin UI + /api/admin routes

src/components/ Admin dashboard React components src/tools/ MCP tool handlers src/mcp/tools.ts tool registration (includes xrpl) src/indexer/ xrpl.js crawl targets src/services/ search, indexer, store, x402, earnings, discovery src/data/ JSON index, syntax catalog, known errors, symbol map, examples, XRPL intents src/types/ Zod schemas + TS types scripts/ index-docs, x402-smoke server.json MCP Registry remote listing smithery.yaml Smithery remote listing glama.json Glama maintainer claim