Silicon Almanac MCP server
com.siliconalmanac/recordsiliconalmanac.comstreamable-httpv0.2.0Scanned
Semiconductor fabs, published forecasts and their restatements, each row naming its publisher.
9 tools: 6 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Silicon Almanac MCP server can do
The Silicon Almanac MCP server is published by siliconalmanac.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (6 tools: record_overview, fab_profile, figure_history, recent_changes and 2 more), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 6Claude Code: ask
fab_profileOne fab site in full, including the note that says what this record does not know about it, and every capacity statement whose sentence covers it.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it One fab site in full, including the note that says what this record does not know about it, and every capacity statement whose sentence covers it.
Annotations the server declares
- title: Fab profile
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
figure_historyThe revision history of one published figure: every vintage, what the publisher said in their own words, the date they issued it, and the link.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The revision history of one published figure: every vintage, what the publisher said in their own words, the date they issued it, and the link. Includes the restatements as pairs of published values. Call this when a number is quoted and you want to know what the same publisher said before. It states no reason for any change.
Annotations the server declares
- title: Figure history
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
node_bandsHow named publishers have defined process-node bands such as "advanced", each as a dated statement with its wafer basis.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it How named publishers have defined process-node bands such as "advanced", each as a dated statement with its wafer basis. This record defines no bands of its own.
Annotations the server declares
- title: Node bands
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
recent_changesFigures that publishers restated recently, each an old value and a new value with both links.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Figures that publishers restated recently, each an old value and a new value with both links. Says what changed and never what it means.
Annotations the server declares
- title: Recent changes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
record_gapsWhat this record is missing and why each one is open.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it What this record is missing and why each one is open. Call it before concluding a figure exists. Statuses distinguish "nobody publishes this" from "the source costs money" from "we have the URLs and have not done the work".
Annotations the server declares
- title: Record gaps
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
record_overviewStart here.1 finding
Why it is in this group
- The description's first verb is "start": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "record_overview" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.
Description, as the server wrote it Start here. What this record holds, what it refuses to do, and the latest changes. Read it before assuming what is available.
Annotations the server declares
- title: Record overview
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
find_fabsSearch the fab sites in the record by country, operator, kind, status, wafer size or process node.No findings
Why it is in this group
- The name "find_fabs" says "find": a word for reading.
Description, as the server wrote it Search the fab sites in the record by country, operator, kind, status, wafer size or process node. Every row names the publisher it came from; rows with no publisher are not returned.
Annotations the server declares
- title: Find fabs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_figuresEvery published forecast subject in the record and each year it has been forecast for, with how many vintages exist.No findings
Why it is in this group
- The name "list_figures" says "list": a word for reading.
Description, as the server wrote it Every published forecast subject in the record and each year it has been forecast for, with how many vintages exist. Use it to find a subject_id for figure_history.
Annotations the server declares
- title: List figures
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_sourcesEvery publisher this record collects, across BOTH mechanisms: their feed, or their own sitemap.No findings
Why it is in this group
- The name "list_sources" says "list": a word for reading.
Description, as the server wrote it Every publisher this record collects, across BOTH mechanisms: their feed, or their own sitemap. A publisher absent from one may be present in the other.
Annotations the server declares
- title: List sources
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:47 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://desk.siliconalmanac.com/mcp_rpc.php: tools/list returned 9 tools to an anonymous client, including record_overview (write), fab_profile (write), figure_history (write), recent_changes (write), record_gaps (write) and 1 more
Posture changes
- Nov 6, 2026
- Protocol version: 2024-11-05 to 2025-06-18
Findings
Matches of fixed checks, with the text they matched.
- Warnrecord_overview
The server marks "record_overview" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools9 changed.~9 changedView diff
- Changed:fab_profileChanges thingstitleannotations
- Changed:figure_historyChanges thingstitleannotations
- Changed:find_fabsOnly readstitleannotations
- Changed:list_figuresOnly readstitleannotations
- Changed:list_sourcesOnly readstitleannotations
- Changed:node_bandsChanges thingstitleannotations
- Changed:recent_changesChanges thingstitleannotations
- Changed:record_gapsChanges thingstitleannotations
- Changed:record_overviewChanges thingstitleannotations
PostureRemote posture changed. Protocol version: 2024-11-05 -> 2025-06-18.View diff
- Protocol version: 2024-11-05 to 2025-06-18
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http record https://desk.siliconalmanac.com/mcp_rpc.phpclaude mcp add --transport http record https://desk.siliconalmanac.com/mcp_rpc.phpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__record__find_fabs",
"mcp__record__list_figures",
"mcp__record__list_sources"
],
"ask": [
"mcp__record__record_overview",
"mcp__record__fab_profile",
"mcp__record__figure_history",
"mcp__record__recent_changes",
"mcp__record__record_gaps",
"mcp__record__node_bands"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as record. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.siliconalmanac/record/verify?hash=6c4ffe9156492347dba9989ee0c3ceb78594baa191731ef8ca89434743f9ab84" | jq -e '.changed == false'Pinned hash 6c4ffe915649, from Nov 10, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.siliconalmanac/record/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.siliconalmanac/record)Source: MCP Registry. Synced Nov 10, 2026, 22:17 UTC.
Silicon Almanac MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Silicon Almanac MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Silicon Almanac MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Silicon Almanac MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Silicon Almanac MCP server have?
- 9 tools: 6 write, 3 read. record_overview, fab_profile, figure_history, recent_changes, record_gaps, node_bands, find_fabs, list_figures and 1 more.
Does the Silicon Almanac MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Silicon Almanac MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Silicon Almanac MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.