# Stobox Intelligence & Tokenization (remote · mcp.stobox.io)

Verified RWA tokenization knowledge — security tokens, regulation, standards — for any AI.

- Trust score: 62/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.stobox.io`: 62/100 (this document), [markdown](https://verifymcp.io/servers/io-stobox-intelligence-graph/mcp.md), [page](https://verifymcp.io/servers/io-stobox-intelligence-graph/mcp)

## Channel facts

- Endpoint: `https://mcp.stobox.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-08-03.

- **Endpoint Security**: 60/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 6 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 is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 956 tokens (~159/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 57% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http io-stobox-intelligence-graph https://mcp.stobox.io/mcp
```

### Codex

```toml
[mcp_servers.io-stobox-intelligence-graph]
url = "https://mcp.stobox.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-stobox-intelligence-graph": {
      "type": "remote",
      "url": "https://mcp.stobox.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-stobox-intelligence-graph --url https://mcp.stobox.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-stobox-intelligence-graph:
    url: "https://mcp.stobox.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-stobox-intelligence-graph": {
      "type": "http",
      "url": "https://mcp.stobox.io/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-08-03 (score 62, +1)

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

### 2026-07-31 (score 61, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 59, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 60, +1)

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

### 2026-07-27 (score 59, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 55)

First indexed and scored.

## MCP tools (6)

### `stobox_knowledge_search` (~99 tokens)

Search Stobox's verified knowledge base on real-world-asset tokenization: canonical, source-linked answers, facts, and articles (GraphRAG: vector + relationship expansion). Use for any question about tokenization, RWA, security tokens, regulation, Compass, STBX/STBU, or Stobox itself.

Input parameters:

- `k` (integer): Max results (default 8).
- `query` (string, required): The question or search query.

### `stobox_term_lookup` (~67 tokens)

Explain one term, product, standard, or regulation from the Stobox knowledge graph — e.g. 'STBX', 'Compass', 'ERC-7943', 'MiCA'. Returns its authoritative description, aliases, relationships, and source documents.

Input parameters:

- `name` (string, required)

### `stobox_related_topics` (~57 tokens)

Show what is connected to a term in the Stobox knowledge graph — the related products, standards, regulations, and concepts, 1–2 relationship hops out.

Input parameters:

- `hops` (integer)
- `name` (string, required)

### `stobox_fact_check` (~104 tokens)

Verify a claim about Stobox or tokenization against the CANONICAL Stobox knowledge graph before repeating or publishing it. Returns a verdict (contradicted / supported / no_contradiction_detected / unverifiable), any canon violations with corrections, and the canonical evidence. Call this on every factual claim about STBX, ERC-7943, Compass chains, Gene Deyev's title, etc.

Input parameters:

- `claim` (string, required): The factual claim to verify.

### `stobox_answer_context` (~67 tokens)

Build a source-linked briefing for answering a tokenization question: the top passages, entity facts, and source URLs in one prompt-ready block. Use it to ground an answer in verified Stobox knowledge before responding.

Input parameters:

- `max_chars` (integer)
- `query` (string, required)

### `stobox_start_tokenization` (~218 tokens)

Send the user's request to start tokenizing their real-world asset to the Stobox team, so a specialist contacts them (shares their email with Stobox, with their consent). Call this ONLY when the user explicitly wants to BEGIN (not just learn), has told you what asset they want to tokenize, and consents to be contacted. Requires a contact email. Returns confirmation + next steps. Do NOT call for general questions — use the search/lookup tools for those. Never invent an email; ask the user for it first.

Input parameters:

- `asset_type` (string, required): What they want to tokenize, e.g. real estate, a fund, private credit, company equity.
- `company` (string)
- `email` (string, required): The user's contact email (required).
- `jurisdiction` (string): Country/region of the asset or issuer.
- `name` (string): The user's name, if given.
- `notes` (string): Anything relevant they shared: asset size, timeline, goals. No sensitive IDs or financials.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-stobox-intelligence-graph/mcp#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 61
- 2026-08-01: 61
- 2026-07-31: 61
- 2026-07-30: 59
- 2026-07-29: 60
- 2026-07-28: 60
- 2026-07-27: 59
- 2026-07-26: 55

## Links

- Remote endpoint: https://mcp.stobox.io/mcp
- Website: https://www.stobox.io/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-stobox-intelligence-graph/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-stobox-intelligence-graph/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-stobox-intelligence-graph/mcp