A remote MCP endpoint that gives an assistant source-linked knowledge about real-world asset tokenization, security tokens, regulation and standards.
What you can do
Stobox Intelligence & Tokenization is a remote MCP server reached over streamable HTTP at a hosted endpoint. According to its registry description, it supplies source-linked knowledge on real-world asset (RWA) tokenization, covering security tokens, regulation and standards. No individual tools are listed in the supplied manifest, so the exact operations an assistant can call are not documented here.
When to use it
Consider it when an assistant needs background or reference material on tokenized real-world assets, security tokens, or the regulations and standards around them, and a hosted endpoint is acceptable. It is not a general-purpose tool server; the manifest lists no tools, so its usefulness depends on the knowledge it returns.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the provider's hosted endpoint. The manifest declares no authentication, no environment variables and no headers, and no local package or runtime.
Before you install
The manifest declares no authentication, so requests may be unauthenticated and anything sent to the endpoint leaves the user's machine for a third party. No tools, write actions, payments or credentials are documented, so the practical risk cannot be judged from the supplied information; verify the provider's terms and data handling before relying on it.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.stobox%2Fintelligence-graph/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
Parameterskqueryrequired
stobox_term_lookup
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.
Parametersnamerequired
stobox_related_topics
Show what is connected to a term in the Stobox knowledge graph — the related products, standards, regulations, and concepts, 1–2 relationship hops out.
Parametershopsnamerequired
stobox_fact_check
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.
Parametersclaimrequired
stobox_answer_context
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.
Parametersqueryrequiredmax_chars
stobox_start_tokenization
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.
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.