Semiotic
REMOTE · SEMIOTIC-MCP-SERVER-481507046413.US-WEST1.RUN.APP · 2 COMPONENTS
Verified React chart generation: select, validate, repair, render, and inspect charts through MCP.
Available components
Last scanned (10 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Design and Media
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Oct 26 0
- Server version: 3.13.2 → 3.13.3 functional
- 28 Oct 26 0
- Server version: 3.13.1 → 3.13.2 functional
- 26 Oct 26 0
- Server version: 3.13.0 → 3.13.1 functional
- 23 Oct 26 0
- Server version: 3.12.1 → 3.13.0 functional
- 1 Oct 26 0
- Server version: 3.11.2 → 3.12.0 functional
- 29 Sept 26 0
- Server version: 3.11.1 → 3.11.2 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 3.10.4 → 3.11.1 functional
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 6 Nov 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 | 7 Oct 2026 | 30 Dec 2026 | ECDSA 256 | SHA256-RSA | 53da11951e5eb49012fb872c3cb3e54d |
| 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. | DS published | 23684 | 8 | Verified |
| run.app. | No DS | 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 |
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 →
auditChart Audit chart quality and accessibility ~44
Run design diagnostics plus accessibility and mobile audits, returning prioritized structured findings.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | – |
| props | object | yes | – |
| viewportWidth | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | – |
| evidenceEnvelope | object | – | – |
| evidenceGate | object | – | – |
| status | string | yes | – |
| surfaceVersion | string | yes | – |
No examples provided.
createChart Create and prove a chart ~133
Select, validate, diagnose, render, and prove a static-data Semiotic chart. This is the default public workflow.
| Name | Type | Req | Description |
|---|---|---|---|
| audience | object | – | – |
| component | string | – | Optional chart preference; the fit-ranked result remains authoritative. |
| data | array | yes | – |
| fieldRoles | object | – | Per-field semantic or exact encoding-role hints used before chart ranking. |
| identifiers | array | – | Fields that identify records and must not be used as visual encodings or measures. |
| intent | – | – | – |
| props | object | – | Optional props to merge over the selected chart recipe. |
| theme | object | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | – |
| evidenceEnvelope | object | – | – |
| evidenceGate | object | – | – |
| status | string | yes | – |
| surfaceVersion | string | yes | – |
No examples provided.
explainChart Explain a chart without pixels ~39
Return reader grounding: chart description, communicative intent, and navigable data structure.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | – |
| props | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| evidenceFragment | object | – | – |
| grounding | object | yes | – |
| status | string | yes | – |
| surfaceVersion | string | yes | – |
No examples provided.
getChartSchema Get a chart schema ~30
Return canonical Semiotic prop-schema guidance for code editing and advanced configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accessibility | object | – | – |
| availableComponents | array | – | – |
| behaviorContracts | array | – | – |
| component | string | – | – |
| renderable | boolean | – | – |
| schema | object | – | – |
| status | string | yes | – |
| surfaceVersion | string | yes | – |
No examples provided.
improveChart Improve an existing chart ~91
Diagnose a chart configuration, assess data fit, and propose repairs or variants.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | – |
| data | array | – | – |
| fieldRoles | object | – | Per-field semantic or exact encoding-role hints used before chart ranking. |
| identifiers | array | – | Fields that identify records and must not be used as visual encodings or measures. |
| intent | – | – | – |
| props | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accessibilityRecommendation | object | – | – |
| component | string | yes | – |
| diagnostics | array | yes | – |
| evidenceFragment | object | – | – |
| repair | object | yes | – |
| status | string | yes | – |
| surfaceVersion | string | yes | – |
| variants | array | yes | – |
No examples provided.
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
claude mcp add --transport http nteract-semiotic 'https://semiotic-mcp-server-481507046413.us-west1.run.app/mcp'
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 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Semiotic MCP server?
VerifyMCP ran 14 checks on Semiotic, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.