Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Semiotic

REMOTE · SEMIOTIC-MCP-SERVER-481507046413.US-WEST1.RUN.APP · 2 COMPONENTS · SCANNED SEP 21

Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.

0 this week 84 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 602 tokens (~37/item across 16 items; 5 tools + 11 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 30% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the Semiotic MCP server?

Semiotic is a hosted endpoint at https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · semiotic-mcp-server-481507046413.us-west1.run.app

# add to Claude Code
claude mcp add --transport http nteract-semiotic 'https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "nteract-semiotic": {
      "url": "https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "nteract-semiotic": {
      "type": "http",
      "url": "https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.nteract-semiotic]
url = "https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nteract-semiotic": {
      "type": "remote",
      "url": "https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nteract-semiotic --url 'https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  nteract-semiotic:
    url: "https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "nteract-semiotic": {
      "Transport": "http",
      "Url": "https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add nteract-semiotic -t streamable-http -u 'https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp'
// mcp.json
{
  "mcpServers": {
    "nteract-semiotic": {
      "type": "http",
      "url": "https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 0
    • Server version: 3.10.2 → 3.10.3 functional
  • 19 Sept 26 0
    • Server version: 3.10.1 → 3.10.2 functional
  • 15 Sept 26 0
    • Schema quality: 530 → 602 functional
    • New resource “semiotic-task-index” functional
    • New resource “semiotic-artifact-contract-schema” functional
    • Server version: 3.9.2 → 3.10.1 functional
  • 1 Sept 26 +1
    • The server now declares the “completions” capability functional
    • New resource “semiotic-schema-index” functional
    • Server version: 3.9.1 → 3.9.2 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 20 Aug 26 0
    • Schema quality: 32 → 39 functional
    • Tool coverage: 13% → 30% functional
    • Server version: 3.8.7 → 3.9.1 functional
    • “improveChart” added an optional parameter “identifiers” cosmetic
    • “createChart” added an optional parameter “fieldRoles” cosmetic
    • “createChart” added an optional parameter “identifiers” cosmetic
    • “improveChart” added an optional parameter “fieldRoles” cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.a.run.app CN=WR2,O=Google Trust Services,C=US 4 Sept 2026 27 Nov 2026 ECDSA 256 SHA256-RSA a6993fec773504b312550b7de9609011
SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more
CN=WR2,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a07c4cded100ad9d66a5107b98
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of semiotic-mcp-server-481507046413.us-west1.run.app. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
run.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp Verified 200
http (plaintext) http://semiotic-mcp-server-481507046413.us-west1.run.app/mcp HTTPS enforced 302 https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp
MCP tools · 5 exposed · ~337 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
auditChart ~44

Run design diagnostics plus accessibility and mobile audits, returning prioritized structured findings.

NameTypeReqDescription
componentstringyes
propsobjectyes
viewportWidthinteger
NameTypeReqDescription
componentstringyes
evidenceEnvelopeobject
evidenceGateobject
statusstringyes
surfaceVersionstringyes

No examples provided.

createChart ~133

Select, validate, diagnose, render, and prove a static-data Semiotic chart. This is the default public workflow.

NameTypeReqDescription
audienceobject
componentstringOptional chart preference; the fit-ranked result remains authoritative.
dataarrayyes
fieldRolesobjectPer-field semantic or exact encoding-role hints used before chart ranking.
identifiersarrayFields that identify records and must not be used as visual encodings or measures.
intent
propsobjectOptional props to merge over the selected chart recipe.
themeobject
NameTypeReqDescription
componentstring
evidenceEnvelopeobject
evidenceGateobject
statusstringyes
surfaceVersionstringyes

No examples provided.

explainChart ~39

Return reader grounding: chart description, communicative intent, and navigable data structure.

NameTypeReqDescription
componentstringyes
propsobjectyes
NameTypeReqDescription
evidenceFragmentobject
groundingobjectyes
statusstringyes
surfaceVersionstringyes

No examples provided.

getChartSchema ~30

Return canonical Semiotic prop-schema guidance for code editing and advanced configuration.

NameTypeReqDescription
componentstring
NameTypeReqDescription
accessibilityobject
availableComponentsarray
behaviorContractsarray
componentstring
renderableboolean
schemaobject
statusstringyes
surfaceVersionstringyes

No examples provided.

improveChart ~91

Diagnose a chart configuration, assess data fit, and propose repairs or variants.

NameTypeReqDescription
componentstringyes
dataarray
fieldRolesobjectPer-field semantic or exact encoding-role hints used before chart ranking.
identifiersarrayFields that identify records and must not be used as visual encodings or measures.
intent
propsobjectyes
NameTypeReqDescription
accessibilityRecommendationobject
componentstringyes
diagnosticsarrayyes
evidenceFragmentobject
repairobjectyes
statusstringyes
surfaceVersionstringyes
variantsarrayyes

No examples provided.

Common questions

What is the Semiotic MCP server?

Semiotic is an MCP server listed in the public MCP registry as io.github.nteract/semiotic. Verified React chart generation: select, validate, repair, render, and inspect charts through MCP. This page covers its hosted endpoint (https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp).

Is the Semiotic MCP server safe to use?

Semiotic scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Semiotic MCP server expose?

Semiotic exposes 5 tools: createChart, improveChart, explainChart, auditChart, getChartSchema. Their descriptions and schemas cost roughly 337 tokens of context every time the server is loaded.

Does the Semiotic MCP server require authentication?

No. We connected to Semiotic without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Semiotic MCP server still maintained?

Semiotic is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.