Stobox Intelligence & Tokenization

Source-linked RWA tokenization knowledge for any AI: security tokens, regulation and standards.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
92%
Integridad del esquema
89%
Calidad de los nombres
80%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Hallazgos (1)

  • LOWTool 'stobox_term_lookup' description lacks action verben stobox_term_lookup

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~775Tokens (definiciones de herramientas)
~619 BTamaño de respuesta típico
Impacto moderado en la atención (0.61% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "intelligence-graph": {
      "url": "https://mcp.stobox.io/mcp"
    }
  }
}

Puntos de conexión remotos

https://mcp.stobox.io/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (6)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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.

Esquema de entrada

{
  "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"
  ]
}

Prompts recomendados

search_research
Search for information about [topic] using Stobox Intelligence & Tokenization
Herramientas esperadas: stobox_knowledge_search
find_specific
Find [specific item] using Stobox Intelligence & Tokenization
Herramientas esperadas: stobox_knowledge_search

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada6 herramientas
verificadoversión no registrada6 herramientas