Titan Frameworks MCP server
Commit Sep 15, 2026Reviews and rewrites LangChain, LlamaIndex, Ollama, and XRPL code against current APIs with runnable examples and transaction skeletons.
Also known as bebopp187-stack/titan-frameworks, titan-frameworks
- Stars
- 0
- Tools
- 10
- Downloads, 30 days
- —
- Latest version
- 1.0.1
- Last commit
- Sep 15, 2026
- License
- MIT
What is Titan Frameworks MCP?
Titan Frameworks reviews and rewrites LangChain, LlamaIndex, Ollama, and XRPL code against current APIs with runnable examples and transaction skeletons. It exposes 10 tools, such as review_framework_code, rewrite_framework_code, diagnose_framework_error.
Summary generated from the project's README
About Titan Frameworks MCP server
Titan Frameworks provides a specialized service for developers working with LangChain, LlamaIndex, Ollama, and XRPL. It functions by reviewing and rewriting code to ensure compatibility with current APIs, preventing crashes caused by deprecated functions. Users can access the service via a remote HTTP connection or run it locally using stdio for free.
When using the production HTTP endpoint, the server requires micropayments via the x402 protocol. Payments can be made using USDC on the Base network or XRP and RLUSD on the XRPL mainnet. The server includes specific tools like review_framework_code for linting snippets, rewrite_framework_code for applying updates, and diagnose_framework_error for fixing stack traces. It also offers draft_xrpl_intent_tx to generate transaction skeletons that do not actually move funds, alongside tools to fetch working examples or search documentation.
What you can do with it
- 1Fix deprecated API callsProvide a stack trace to identify and resolve errors caused by outdated framework syntax.
- 2Update existing codebasesApply conservative rewrites to code snippets to align them with the latest framework versions.
- 3Generate XRPL transaction templatesCreate typed transaction skeletons for the XRPL without risking actual fund transfers.
- 4Retrieve functional code samplesRequest a complete, runnable file for specific tasks like building an agent or a RAG system.
Written from the project's README. Every use case is checked against a quote from it.
How to install Titan Frameworks MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Titan Frameworks MCP in Claude Code
$ claude mcp add --transport http titan-frameworks https://titan-frameworks-production.up.railway.app/mcpInstall Titan Frameworks MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"titan-frameworks": {
"url": "https://titan-frameworks-production.up.railway.app/mcp"
}
}
}Install Titan Frameworks MCP in VS Code
.vscode/mcp.json
{
"servers": {
"titan-frameworks": {
"type": "http",
"url": "https://titan-frameworks-production.up.railway.app/mcp"
}
}
}Install Titan Frameworks MCP in VS Code CLI
$ code --add-mcp '{"name":"titan-frameworks","type":"http","url":"https://titan-frameworks-production.up.railway.app/mcp"}'Install Titan Frameworks MCP in Codex
$ codex mcp add titan-frameworks --url https://titan-frameworks-production.up.railway.app/mcpInstall Titan Frameworks MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.titan-frameworks] url = "https://titan-frameworks-production.up.railway.app/mcp"
Install Titan Frameworks MCP in Gemini CLI
$ gemini mcp add -s user --transport http titan-frameworks https://titan-frameworks-production.up.railway.app/mcpInstall Titan Frameworks MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"titan-frameworks": {
"url": "https://titan-frameworks-production.up.railway.app/mcp",
"type": "http"
}
}
}Titan Frameworks MCP tools 10
Detected from the READMEreview_framework_coderewrite_framework_codediagnose_framework_errorresolve_symbolfetch_working_examplefetch_latest_syntaxsearch_ai_framework_docsdraft_xrpl_intent_txlist_supported_frameworkslist_known_deprecations
| review_framework_code | — | |
| rewrite_framework_code | — | |
| diagnose_framework_error | — | |
| resolve_symbol | — | |
| fetch_working_example | — | |
| fetch_latest_syntax | — | |
| search_ai_framework_docs | — | |
| draft_xrpl_intent_tx | — | |
| list_supported_frameworks | — | |
| list_known_deprecations | — |
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablebebopp187-stack/titan-frameworks is public and reachablegithub.com/bebopp187-stack/titan-frameworks ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-15github.com/bebopp187-stack/titan-frameworks ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model10 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeEndpoint did not answer initialize: HTTP 404Finding
README
View on GitHubTitan 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
Titan Frameworks MCP questions
How do I add Titan Frameworks MCP to Claude Code?
Run claude mcp add --transport http titan-frameworks https://titan-frameworks-production.up.railway.app/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Titan Frameworks MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Titan Frameworks MCP provide?
It exposes 10 tools, including review_framework_code, rewrite_framework_code, diagnose_framework_error, resolve_symbol, fetch_working_example.
What frameworks does Titan Frameworks support?
It supports LangChain, LlamaIndex, Ollama, and XRPL.
Does the XRPL tool actually send transactions?
No, the tool only generates typed transaction skeletons and never submits or moves funds.
Is there a cost to use the production server?
Yes, production tool calls require micropayments via USDC on Base or XRP/RLUSD on XRPL, though some discovery tools are free.