Stobox Intelligence & Tokenization
Source-linked RWA tokenization knowledge for any AI: security tokens, regulation and standards.
Should I use this
Quality & Safety
Findings (1)
- LOWin stobox_term_lookup
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"intelligence-graph": {
"url": "https://mcp.stobox.io/mcp"
}
}
}Remote endpoints
https://mcp.stobox.io/mcpstreamable-httpWhat it can do
Tool inventory
Tools (6)
🟢stobox_knowledge_search(query, k)
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 Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "The question or search query."
},
"k": {
"type": "integer",
"description": "Max results (default 8).",
"default": 8
}
},
"required": [
"query"
]
}🟢stobox_term_lookup(name)
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 Schema
{
"type": "object",
"properties": {
"name": {
"type": "string"
}
},
"required": [
"name"
]
}🟢stobox_related_topics(name, hops)
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 Schema
{
"type": "object",
"properties": {
"name": {
"type": "string"
},
"hops": {
"type": "integer",
"default": 1
}
},
"required": [
"name"
]
}🟢stobox_fact_check(claim)
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 Schema
{
"type": "object",
"properties": {
"claim": {
"type": "string",
"description": "The factual claim to verify."
}
},
"required": [
"claim"
]
}⚪stobox_answer_context(query, max_chars)
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 Schema
{
"type": "object",
"properties": {
"query": {
"type": "string"
},
"max_chars": {
"type": "integer",
"default": 4000
}
},
"required": [
"query"
]
}🟡stobox_start_tokenization(email, asset_type, jurisdiction, name, company, ...)
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 Schema
{
"type": "object",
"properties": {
"email": {
"type": "string",
"description": "The user's contact email (required)."
},
"asset_type": {
"type": "string",
"description": "What they want to tokenize, e.g. real estate, a fund, private credit, company equity."
},
"jurisdiction": {
"type": "string",
"description": "Country/region of the asset or issuer."
},
"name": {
"type": "string",
"description": "The user's name, if given."
},
"company": {
"type": "string"
},
"notes": {
"type": "string",
"description": "Anything relevant they shared: asset size, timeline, goals. No sensitive IDs or financials."
}
},
"required": [
"email",
"asset_type"
]
}Recommended Prompts
stobox_knowledge_searchstobox_knowledge_searchCommunity
Evidence