Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL)
RemoteAbout Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL)
Titan Frameworks is a paid MCP server for developers maintaining LangChain, LlamaIndex, Ollama, or XRPL code. It checks and rewrites code against current APIs and provides examples, documentation lookup, and XRPL transaction skeletons that do not submit transactions.
Key features
- 01Review code for deprecated API usage
- 02Rewrite code using cataloged migrations
- 03Diagnose framework errors from stack traces
- 04Look up symbols, syntax, and documentation
- 05Draft non-submitting XRPL transaction skeletons
Use cases
- 01Check a code snippet before running it
- 02Patch code that uses outdated APIs
- 03Find a fix for a framework stack trace
- 04Prepare an XRPL transaction structure without submitting
MCP support
Exposes tools and prompts through Streamable HTTP; MCP calls other than discovery and listing supported frameworks require x402 payment in production. Local stdio mode does not charge.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://titan-frameworks-production.up.railway.app/mcpclaude mcp add --transport http bebopp187-stack-titan-frameworks https://titan-frameworks-production.up.railway.app/mcp{"mcpServers":{"bebopp187-stack-titan-frameworks":{"type":"http","url":"https://titan-frameworks-production.up.railway.app/mcp"}}}Open in Cursor{"servers":{"bebopp187-stack-titan-frameworks":{"type":"http","url":"https://titan-frameworks-production.up.railway.app/mcp"}}}Open in VS Code{"mcpServers":{"bebopp187-stack-titan-frameworks":{"type":"http","url":"https://titan-frameworks-production.up.railway.app/mcp"}}}{"mcpServers":{"bebopp187-stack-titan-frameworks":{"serverUrl":"https://titan-frameworks-production.up.railway.app/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMETitan 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
| Tool | Purpose |
|---|---|
review_framework_code | Lint a snippet for dead APIs before it crashes. Returns hunks, does not execute |
rewrite_framework_code | Apply conservative catalog rewrites; leftover lists unsafe call sites |
diagnose_framework_error | Stack-trace → deprecated API → exact fix. Use only when you have an error |
resolve_symbol | Package, install, import, and call shape for one API name |
fetch_working_example | Complete runnable file for a goal (agent, rag, payment, …) |
fetch_latest_syntax | Working snippets and migration notes for one topic. Use when writing a fragment |
search_ai_framework_docs | Keyword search over local Markdown. Use for concepts/symbols; not stack traces |
draft_xrpl_intent_tx | Typed XRPL tx skeleton. Never submits or moves funds |
list_supported_frameworks | Enumerate framework ids, aliases, and catalog topics (free tools/call) |
list_known_deprecations | Full deprecation catalog for one framework or all four |
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
| Path | Notes |
|---|---|
GET /health | liveness + index stats |
GET /llms.txt | agent discovery |
GET /tools | tool list + live pricing |
GET /.well-known/x402 | x402scan resource index |
GET /.well-known/x402.json | full payment requirements + bazaar metadata |
GET /.well-known/mcp/server-card.json | Smithery static card |
ALL /mcp | Streamable HTTP MCP. Handshake/tools/list/list_supported_frameworks free; other tools/call paid |
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.
| Rail | Price | Network | Facilitator |
|---|---|---|---|
| USDC | $0.001 | Base (eip155:8453) | PayAI |
| XRP | 1000 drops (0.001 XRP) | XRPL mainnet (xrpl:0) | T54 |
| RLUSD | 0.001 | XRPL mainnet (xrpl:0) | T54 |
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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.