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.

io.github.codebiwan/semi-data

REMOTE · SEMIDATA.DEV

US-government semiconductor & quantum supply-chain intelligence: controls, entities, funding.

Available components

0 this week 71 Trust /100

Last scanned (18 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

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 Security49
Transport & Reachability100
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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

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 →

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 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
  • 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 0
    • Stability: 0.97 → pass security
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 Nov 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 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA256 4ca0d407228b03e80e87838ccfcea0be
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. DS published 60074 8 Verified
semidata.dev. DS published 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
MCP tools · 6 exposed · ~1,170 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
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.

NameTypeReqDescription
agencystring–Awarding agency or sub-agency (partial match), e.g. Energy, NSF, Defense, DARPA.
award_typestring–Award type.
limitinteger–limit (default 50, max 200)
min_amountnumber–Minimum award amount in USD.
offsetinteger–offset (default 0)
qstring–Full-text search (ranked) across recipient, description, and agency.
recipientstring–Recipient/organization name (partial match), e.g. IonQ, Rigetti, a university.
sincestring–ISO date; awards on or after this action date.
yearstring–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.

NameTypeReqDescription
hs_codestring–HS-6 commodity code, e.g. 280491 for gallium.
limitinteger–limit (default 100, max 500)
materialstring–Material name (synonym-expanded), e.g. Gallium, Cobalt, Lithium.
min_valuenumber–Minimum trade value in USD.
offsetinteger–offset (default 0)
periodstring–Year, e.g. "2022".
reporterstring–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.

NameTypeReqDescription
active_onlyboolean–Only return active producers/plants.
commoditystring–Commodity name with synonym expansion (e.g. Gallium, Lithium, Cobalt).
countrystring–Country name (exact match), e.g. "United States", "China".
limitinteger–limit (default 50, max 200)
min_scoreinteger–Minimum semiconductor relevance score (1-10).
offsetinteger–offset (default 0)
qstring–Full-text search (ranked) across site name, commodity, ore controls, and location.
statestring–US state filter (exact match).
statusstring–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.

NameTypeReqDescription
countrystring–Country NAME (full name, e.g. "China", "Russia") - matched within countries_affected. Not an ISO code.
importancestring–strategic_importance level.
limitinteger–limit (default 50, max 200)
materialstring–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…
offsetinteger–offset (default 0)
qstring–Full-text search across title, abstract, and summary.
sectorstring–Filter to a tech vertical. quantum = quantum-relevant records (export controls on qubits, cryogenics, etc.). Omit for all.
sincestring–ISO date; records published on or after this date.
typestring–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.

NameTypeReqDescription
countrystring–ISO-2 country code (e.g. CN, RU, IR).
limitinteger–limit (default 50, max 200)
list_namestring–Source list fragment, e.g. "Entity List", "SDN", "Military End User".
namestring–Entity name or alias (partial match).
offsetinteger–offset (default 0)
qstring–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.

NameTypeReqDescription
entitystring–Company / filer name (partial match).
formstring–SEC form type.
importancestring–strategic_importance level.
limitinteger–limit (default 50, max 200)
materialstring–Material mentioned in filing (synonym-expanded).
offsetinteger–offset (default 0)
qstring–Full-text search (ranked) across entity name, summary, materials, and companies.
sectorstring–Filter to a tech vertical (quantum = quantum-relevant filings). Omit for all.
sentimentstring–Supply chain sentiment.
sincestring–ISO date; filings on or after.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http codebiwan-semi-data 'https://semidata.dev/v1/mcp'
Common questions

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 21 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 io.github.codebiwan/semi-data MCP server?

VerifyMCP ran 12 checks on io.github.codebiwan/semi-data, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.codebiwan/semi-data: Authorization. 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.