# Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) (remote · titan-frameworks-production.up.railway.app)

Review and rewrite LangChain, LlamaIndex, Ollama, and XRPL code against current APIs.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `titan-frameworks-production.up.railway.app`: 68/100 (this document), [markdown](https://verifymcp.io/servers/bebopp187-stack-titan-frameworks/titan-frameworks-production.md), [page](https://verifymcp.io/servers/bebopp187-stack-titan-frameworks/titan-frameworks-production)

## Channel facts

- Endpoint: `https://titan-frameworks-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1805 tokens (~164/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) MCP server?

Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) is a hosted endpoint at https://titan-frameworks-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http bebopp187-stack-titan-frameworks 'https://titan-frameworks-production.up.railway.app/mcp'
```

### Cursor

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

### VS Code

```json
{
  "servers": {
    "bebopp187-stack-titan-frameworks": {
      "type": "http",
      "url": "https://titan-frameworks-production.up.railway.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.bebopp187-stack-titan-frameworks]
url = "https://titan-frameworks-production.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bebopp187-stack-titan-frameworks": {
      "type": "remote",
      "url": "https://titan-frameworks-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bebopp187-stack-titan-frameworks --url 'https://titan-frameworks-production.up.railway.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bebopp187-stack-titan-frameworks:
    url: "https://titan-frameworks-production.up.railway.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "bebopp187-stack-titan-frameworks": {
      "Transport": "http",
      "Url": "https://titan-frameworks-production.up.railway.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bebopp187-stack-titan-frameworks -t streamable-http -u 'https://titan-frameworks-production.up.railway.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "bebopp187-stack-titan-frameworks": {
      "type": "http",
      "url": "https://titan-frameworks-production.up.railway.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 66, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-15 (score 65)

First indexed and scored.

## MCP tools (10)

### `review_framework_code` (~163 tokens)

Review Framework Code

Scan source against known dead APIs (LLMChain, initialize_agent, ServiceContext, ripple-lib, …) and return each hit with replacement plus a unified-diff hunk. Use before running agent-written code; diagnose_framework_error is for after a stack trace. Does not execute or submit. Paid tools/call: $0.001 USDC or 1000 drops XRP; catalog-backed, not LLM-invented.

Input parameters:

- `code` (string, required): Source to lint before running. Not a stack trace (use diagnose_framework_error)
- `filename` (string): Optional path used only in unified-diff headers
- `framework` (string, required): One of langchain, llamaindex, ollama, or xrpl — the library the snippet is written against

Output parameters:

- `framework` (string)
- `hints` (array)
- `issueCount` (integer)
- `issues` (array)
- `matched` (boolean)

### `rewrite_framework_code` (~164 tokens)

Rewrite Framework Code

Apply conservative catalog rewrites (imports/identifiers) to a snippet and return the patched file plus a full unified diff. Use when review_framework_code found hits and you want an applyable file. Leftover lists unsafe call-site transforms (e.g. LLMChain(...)) that stay for a human/agent. Does not execute or submit. Paid tools/call: $0.001 USDC or 1000 drops XRP.

Input parameters:

- `code` (string, required): Source to lint before running. Not a stack trace (use diagnose_framework_error)
- `filename` (string): Optional path used only in unified-diff headers
- `framework` (string, required): One of langchain, llamaindex, ollama, or xrpl — the library the snippet is written against

Output parameters:

- `applied` (array)
- `changed` (boolean)
- `code` (string)
- `diff` (string)
- `filename` (string)
- `framework` (string)
- `leftover` (array)
- `notes` (array)

### `diagnose_framework_error` (~165 tokens)

Diagnose Framework Error

Match a stack trace or exception against known deprecated APIs for langchain, llamaindex, ollama, or xrpl and return the replacement plus a fix. Use only when you have an error_log; matched=false means no catalog hit — then search_ai_framework_docs with the failing symbol. Lint source before it crashes with review_framework_code. Not for happy-path syntax (fetch_latest_syntax). Paid tools/call: $0.001 USDC or 1000 drops XRP; read-only, does not execute code.

Input parameters:

- `error_log` (string, required): Raw traceback or exception text. Paste the error, not a question about it
- `framework` (string, required): One of langchain, llamaindex, ollama, or xrpl — the library that threw the error

Output parameters:

- `framework` (string)
- `hints` (array)
- `matched` (boolean)
- `matches` (array)

### `resolve_symbol` (~146 tokens)

Resolve Symbol

Map an API name to the current package, install line, import, and call shape (ChatOpenAI, create_agent, VectorStoreIndex, xrpToDrops, …). Use when you know the symbol but not where it lives. Prefer search_ai_framework_docs for concepts and fetch_latest_syntax for topic snippets. Paid tools/call: $0.001 USDC or 1000 drops XRP; catalog-backed.

Input parameters:

- `framework` (string, required): One of langchain, llamaindex, ollama, or xrpl — the library that owns the symbol
- `symbol` (string, required): API name or import path, e.g. ChatOpenAI, ServiceContext, RippleAPI

Output parameters:

- `aliases` (array)
- `call` (string)
- `framework` (string)
- `hints` (array)
- `importLine` (string)
- `install` (string)
- `matched` (boolean)
- `note` (string)
- `package` (string)
- `symbol` (string)

### `fetch_working_example` (~193 tokens)

Fetch Working Example

Fetch one complete runnable file (filename, install/run, source) for a goal such as agent, rag, chat, payment, or rlusd. Use when fetch_latest_syntax snippets are too small to execute. matched=false means no catalog example — then fetch_latest_syntax. Paid tools/call: $0.001 USDC or 1000 drops XRP; does not execute the example.

Input parameters:

- `framework` (string, required): One of langchain, llamaindex, ollama, or xrpl — the library the example should use
- `goal` (string, required): What to build: agent, rag, chat, lcel, payment, rlusd, trustline, …
- `language` (string): python or typescript. Omit to take the best match
- `runtime` (string): openai, ollama, or xrpl-testnet. Omit to take the best match

Output parameters:

- `code` (string)
- `filename` (string)
- `framework` (string)
- `goals` (array)
- `hints` (array)
- `id` (string)
- `language` (string)
- `matched` (boolean)
- `run` (string)
- `runtime` (string)
- `versions` (array)

### `fetch_latest_syntax` (~173 tokens)

Fetch Latest Syntax

Curated working imports, snippets, and migration notes for one topic (agents, rag, wallet, payment, trustlines, …). Use when writing or migrating a fragment; unknown topics fall back to related doc chunks instead of failing. Prefer fetch_working_example for a complete runnable file, search_ai_framework_docs for open-ended lookup, and diagnose_framework_error for exceptions. Paid tools/call: $0.001 USDC or 1000 drops XRP; read-only catalog.

Input parameters:

- `framework` (string, required): One of langchain, llamaindex, ollama, or xrpl — the library the user is coding against
- `topic` (string, required): One topic word: agents, rag, chat, tools, streaming, wallet, payment, trustlines, channels, rlusd, hooks, or migration

Output parameters:

- `framework` (string)
- `imports` (array)
- `migrationNotes` (array)
- `relatedDocs` (array)
- `snippets` (array)
- `topic` (string)
- `versionNote` (string)

### `search_ai_framework_docs` (~166 tokens)

Search AI Framework Docs

Keyword search over a local Markdown index for langchain, llamaindex, ollama, or xrpl; returns compact chunks and never live-crawls. Use for concepts, symbols, or questions; hitCount 0 means no match — shorten the query. Do not use for stack traces (diagnose_framework_error), import/package lookup (resolve_symbol), or copy-paste current syntax (fetch_latest_syntax). Paid tools/call: $0.001 USDC or 1000 drops XRP.

Input parameters:

- `framework` (string, required): One of langchain, llamaindex, ollama, or xrpl — the library the user is coding against
- `query` (string, required): 2–8 keywords or an API symbol. Not a stack trace (use diagnose_framework_error)

Output parameters:

- `framework` (string)
- `hitCount` (integer)
- `hits` (array)
- `query` (string)

### `draft_xrpl_intent_tx` (~142 tokens)

Draft XRPL Intent Transaction

Draft a typed xrpl.js / xrpl-py skeleton for payment, trustline, rlusd, or channel, plus required fields and common tec/tem failure codes. Use when building an XRPL tx; never submits, signs, or moves funds. Prefer fetch_working_example for a full script and review_framework_code to lint Amount/address mistakes. Paid tools/call: $0.001 USDC or 1000 drops XRP.

Input parameters:

- `intent` (string, required): payment, trustline, rlusd, or channel — what the transaction should do
- `language` (string): typescript (default) or python

Output parameters:

- `failureCodes` (array)
- `hints` (array)
- `intent` (string)
- `language` (string)
- `matched` (boolean)
- `movesFunds` (boolean)
- `notes` (array)
- `requiredFields` (array)
- `skeleton` (string)
- `submits` (boolean)
- `transactionType` (string)

### `list_supported_frameworks` (~90 tokens)

List Supported Frameworks

List the framework ids this server covers (langchain, llamaindex, ollama, xrpl) with display names, aliases, homepages, and catalog topics. Use when you do not know which framework string to pass. Free tools/call (no x402). Not a docs search (search_ai_framework_docs) and not a deprecation dump (list_known_deprecations). Catalog-backed.

Output parameters:

- `count` (integer)
- `frameworks` (array)
- `ids` (array)

### `list_known_deprecations` (~131 tokens)

List Known Deprecations

Return the known-deprecated API catalog (id, old API, replacement, fix) for one framework or all four at once. Use when you want the full deprecation list without a stack trace or source snippet. Prefer diagnose_framework_error when you have an error_log and review_framework_code when you have code. Paid tools/call: $0.001 USDC or 1000 drops XRP; catalog-backed, does not execute code.

Input parameters:

- `framework` (string): Optional. One of langchain, llamaindex, ollama, or xrpl. Omit to list every known deprecation

Output parameters:

- `count` (integer)
- `deprecations` (array)
- `framework` (string)
- `hints` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/bebopp187-stack-titan-frameworks/titan-frameworks-production#diagnostics

## Score history

- 2026-09-20: 68
- 2026-09-19: 67
- 2026-09-18: 67
- 2026-09-17: 66
- 2026-09-16: 66
- 2026-09-15: 65

## Common questions

### What is the Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) MCP server?

Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) is an MCP server listed in the public MCP registry as io.github.bebopp187-stack/titan-frameworks. Review and rewrite LangChain, LlamaIndex, Ollama, and XRPL code against current APIs. This page covers its hosted endpoint (https://titan-frameworks-production.up.railway.app/mcp).

### Is the Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) MCP server safe to use?

Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) MCP server expose?

Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) exposes 10 tools: review_framework_code, rewrite_framework_code, diagnose_framework_error, resolve_symbol, fetch_working_example, and 5 more. Their descriptions and schemas cost roughly 1,533 tokens of context every time the server is loaded.

### Does the Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) MCP server require authentication?

No. We connected to Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) MCP server still maintained?

Titan Frameworks (LangChain, LlamaIndex, Ollama, XRPL) is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://titan-frameworks-production.up.railway.app/mcp
- Repository: https://github.com/bebopp187-stack/titan-frameworks
- Website: https://titan-frameworks-production.up.railway.app/llms.txt
- Changelog RSS feed: https://verifymcp.io/servers/bebopp187-stack-titan-frameworks/titan-frameworks-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/bebopp187-stack-titan-frameworks/titan-frameworks-production.json
- HTML version of this page: https://verifymcp.io/servers/bebopp187-stack-titan-frameworks/titan-frameworks-production