Stobox Intelligence & Tokenization
Measured conclusion: Deep-tested. L2 outcome: tools_ok.
Source-linked RWA tokenization knowledge for any AI: security tokens, regulation and standards.
| Author | io.stobox |
|---|---|
| Access | remote |
| Publisher key required | No |
| Measured state | Deep-tested |
| L1 liveness | alive |
| L1 latency | 181 ms |
| Last measured | 2026-10-26 |
Add to your agent
Copy this into your MCP client config:
{
"mcpServers": {
"Stobox Intelligence & Tokenization": {
"url": "https://mcp.stobox.io/mcp",
"transport": "streamable-http"
}
}
}
Measured tools (6)
stobox_knowledge_searchSearch 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.
Parameters:
query(required) — string — The question or search query.k— integer — Max results (default 8).
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
stobox_term_lookupExplain 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.
Parameters:
name(required) — string
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
stobox_related_topicsShow what is connected to a term in the Stobox knowledge graph — the related products, standards, regulations, and concepts, 1–2 relationship hops out.
Parameters:
name(required) — stringhops— integer
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
stobox_fact_checkVerify 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.
Parameters:
claim(required) — string — The factual claim to verify.
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
stobox_answer_contextBuild 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.
Parameters:
query(required) — stringmax_chars— integer
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
stobox_start_tokenizationSend 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.
Parameters:
email(required) — string — The user's contact email (required).asset_type(required) — string — What they want to tokenize, e.g. real estate, a fund, private credit, company equity.name— string — The user's name, if given.notes— string — Anything relevant they shared: asset size, timeline, goals. No sensitive IDs or financials.company— stringjurisdiction— string — Country/region of the asset or issuer.
Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared
Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.