io.github.codebiwan/semi-data
REMOTE · SEMIDATA.DEV · SCANNED SEP 28
US-government semiconductor & quantum supply-chain intelligence: controls, entities, funding.
Available components
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 Security49
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1237 tokens (~206/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.codebiwan/semi-data MCP server?
io.github.codebiwan/semi-data is a hosted endpoint at https://semidata.dev/v1/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 · semidata.dev
claude mcp add --transport http codebiwan-semi-data 'https://semidata.dev/v1/mcp'
{
"mcpServers": {
"codebiwan-semi-data": {
"url": "https://semidata.dev/v1/mcp"
}
}
} {
"servers": {
"codebiwan-semi-data": {
"type": "http",
"url": "https://semidata.dev/v1/mcp"
}
}
} [mcp_servers.codebiwan-semi-data] url = "https://semidata.dev/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"codebiwan-semi-data": {
"type": "remote",
"url": "https://semidata.dev/v1/mcp",
"enabled": true
}
}
} openclaw mcp add codebiwan-semi-data --url 'https://semidata.dev/v1/mcp' --transport streamable-http
mcp_servers:
codebiwan-semi-data:
url: "https://semidata.dev/v1/mcp" {
"McpServers": {
"codebiwan-semi-data": {
"Transport": "http",
"Url": "https://semidata.dev/v1/mcp"
}
}
} assistant mcp add codebiwan-semi-data -t streamable-http -u 'https://semidata.dev/v1/mcp'
{
"mcpServers": {
"codebiwan-semi-data": {
"type": "http",
"url": "https://semidata.dev/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 25 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
- 3 Sept 26 +1
- Stability: 0.97 → pass security
- 1 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 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
- 11 Aug 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
- 5 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Aug 26 0
First indexed and scored.
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 28 Sept 2026 · Probed https://semidata.dev/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=semidata.dev | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 575e88a51f47b2830e5fcf060b5e3003 |
| SANs: semidata.dev, www.semidata.dev, *.www.semidata.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of semidata.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| semidata.dev. | present | 2371 | 13 | Verified |
| semidata.dev. | Verified address RRset verified with the apex keys |
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://semidata.dev/v1/mcp | Verified | 200 | |
| http (plaintext) | http://semidata.dev/v1/mcp | Served over HTTP | 200 |
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 →
get_quantum_funding ~237
US federal contracts and grants for quantum technology (DOE, NSF, DARPA/DoD, and others), from USAspending.gov. Shows which organizations receive quantum-related federal money, how much, and from which agency. Use to track the quantum supply chain and policy push downstream of the 2026 quantum executive orders.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Awarding agency or sub-agency (partial match), e.g. Energy, NSF, Defense, DARPA. |
| award_type | string | – | Award type. |
| limit | integer | – | limit (default 50, max 200) |
| min_amount | number | – | Minimum award amount in USD. |
| offset | integer | – | offset (default 0) |
| q | string | – | Full-text search (ranked) across recipient, description, and agency. |
| recipient | string | – | Recipient/organization name (partial match), e.g. IonQ, Rigetti, a university. |
| since | string | – | ISO date; awards on or after this action date. |
| year | string | – | Fiscal/action year, e.g. "2025". |
No output schema declared.
No examples provided.
get_trade_flows ~152
UN Comtrade annual export volumes by country and HS code for semiconductor-critical materials.
| Name | Type | Req | Description |
|---|---|---|---|
| hs_code | string | – | HS-6 commodity code, e.g. 280491 for gallium. |
| limit | integer | – | limit (default 100, max 500) |
| material | string | – | Material name (synonym-expanded), e.g. Gallium, Cobalt, Lithium. |
| min_value | number | – | Minimum trade value in USD. |
| offset | integer | – | offset (default 0) |
| period | string | – | Year, e.g. "2022". |
| reporter | string | – | Exporting country name (partial match), e.g. China, Chile, Germany. |
No output schema declared.
No examples provided.
search_mineral_deposits ~205
USGS MRDS mineral deposit records for semiconductor-critical materials. 1,233 deposits. NOTE: this is a 2011 historical snapshot - use as_of in the response meta.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | Only return active producers/plants. |
| commodity | string | – | Commodity name with synonym expansion (e.g. Gallium, Lithium, Cobalt). |
| country | string | – | Country name (exact match), e.g. "United States", "China". |
| limit | integer | – | limit (default 50, max 200) |
| min_score | integer | – | Minimum semiconductor relevance score (1-10). |
| offset | integer | – | offset (default 0) |
| q | string | – | Full-text search (ranked) across site name, commodity, ore controls, and location. |
| state | string | – | US state filter (exact match). |
| status | string | – | development_status (exact match). |
No output schema declared.
No examples provided.
search_regulatory_signals ~256
Federal Register regulatory signals on semiconductor-critical materials: export controls, sanctions, import restrictions, and strategic-reserve actions. LLM-structured with importance scoring.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country NAME (full name, e.g. "China", "Russia") - matched within countries_affected. Not an ISO code. |
| importance | string | – | strategic_importance level. |
| limit | integer | – | limit (default 50, max 200) |
| material | string | – | Material name; matched within materials_mentioned, with synonym expansion (e.g. Gallium also matches GaN). Free-text values: Gallium, Germanium, Indium, Silicon, Rare Earth, Cobalt, Lithium, Telluriu… |
| offset | integer | – | offset (default 0) |
| q | string | – | Full-text search across title, abstract, and summary. |
| sector | string | – | Filter to a tech vertical. quantum = quantum-relevant records (export controls on qubits, cryogenics, etc.). Omit for all. |
| since | string | – | ISO date; records published on or after this date. |
| type | string | – | signal_type to filter by. |
No output schema declared.
No examples provided.
search_restricted_entities ~138
US Consolidated Screening List. Use for supplier / counterparty due diligence against export-control and sanctions lists.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | ISO-2 country code (e.g. CN, RU, IR). |
| limit | integer | – | limit (default 50, max 200) |
| list_name | string | – | Source list fragment, e.g. "Entity List", "SDN", "Military End User". |
| name | string | – | Entity name or alias (partial match). |
| offset | integer | – | offset (default 0) |
| q | string | – | Full-text search across name, aliases, and addresses. |
No output schema declared.
No examples provided.
search_sec_filings ~182
SEC EDGAR filings processed with an LLM to extract supply chain signals, sentiment, and material mentions.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | Company / filer name (partial match). |
| form | string | – | SEC form type. |
| importance | string | – | strategic_importance level. |
| limit | integer | – | limit (default 50, max 200) |
| material | string | – | Material mentioned in filing (synonym-expanded). |
| offset | integer | – | offset (default 0) |
| q | string | – | Full-text search (ranked) across entity name, summary, materials, and companies. |
| sector | string | – | Filter to a tech vertical (quantum = quantum-relevant filings). Omit for all. |
| sentiment | string | – | Supply chain sentiment. |
| since | string | – | ISO date; filings on or after. |
No output schema declared.
No examples provided.
What is the io.github.codebiwan/semi-data MCP server?
io.github.codebiwan/semi-data is an MCP server listed in the public MCP registry as io.github.codebiwan/semi-data. US-government semiconductor & quantum supply-chain intelligence: controls, entities, funding. This page covers its hosted endpoint (https://semidata.dev/v1/mcp).
Is the io.github.codebiwan/semi-data MCP server safe to use?
io.github.codebiwan/semi-data scores 71 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 io.github.codebiwan/semi-data MCP server expose?
io.github.codebiwan/semi-data exposes 6 tools: search_regulatory_signals, search_mineral_deposits, search_sec_filings, search_restricted_entities, get_trade_flows, get_quantum_funding. Their descriptions and schemas cost roughly 1,170 tokens of context every time the server is loaded.
Does the io.github.codebiwan/semi-data MCP server require authentication?
No. We connected to io.github.codebiwan/semi-data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.codebiwan/semi-data MCP server still maintained?
io.github.codebiwan/semi-data is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.