_ registry / mcp streamable-http · checked 1h ago

silicon-almanac

https://desk.siliconalmanac.com

Registry code: 68fa633b1399de4f

api record

Silicon Almanac hands you rows, each naming the publisher that said it and linking where they said it. It answers no questions and states no views. Call record_overview first. Before concluding a figure does not exist, call record_gaps: this record publishes what nobody publishes, and an absent number is not a licence to estimate one. Quote the publisher named on the row, not this record. No account is needed for anything here.

endpoint
https://desk.siliconalmanac.com/mcp_rpc.php
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is silicon-almanac live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is silicon-almanac free to use?
Yes — the hub reached it with no key and no payment.
What tools does silicon-almanac have?
9 tools: recent_changes, record_gaps, record_overview, fab_profile, figure_history, node_bands, list_sources, find_fabs, ….
Is silicon-almanac safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
348ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 9 tools
3 open 6 never probed 3 of 9 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_sources open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "q": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "description": "Rows to return, 1 to 200. Default 50. The envelope always reports the true total separately."
    },
    "bucket": {
      "type": "string"
    },
    "offset": {
      "type": "integer",
      "description": "Rows to skip, for paging."
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • find_fabs open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "q": {
      "type": "string"
    },
    "node": {
      "type": "string"
    },
    "type": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "description": "Rows to return, 1 to 200. Default 50. The envelope always reports the true total separately."
    },
    "offset": {
      "type": "integer",
      "description": "Rows to skip, for paging."
    },
    "status": {
      "type": "string"
    },
    "country": {
      "type": "string"
    },
    "operator": {
      "type": "string"
    },
    "wafer_mm": {
      "type": "integer"
    }
  },
  "additionalProperties": false
}
    arguments 36 lines
  • list_figures open 1h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "limit": {
      "type": "integer",
      "description": "Rows to return, 1 to 200. Default 50. The envelope always reports the true total separately."
    },
    "offset": {
      "type": "integer",
      "description": "Rows to skip, for paging."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • recent_changes unknown never probed

    Figures that publishers restated recently, each an old value and a new value with both links. Says what changed and never what it means.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "days": {
      "type": "integer"
    },
    "limit": {
      "type": "integer",
      "description": "Rows to return, 1 to 200. Default 50. The envelope always reports the true total separately."
    },
    "offset": {
      "type": "integer",
      "description": "Rows to skip, for paging."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • record_gaps unknown never probed

    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".

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "q": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "description": "Rows to return, 1 to 200. Default 50. The envelope always reports the true total separately."
    },
    "offset": {
      "type": "integer",
      "description": "Rows to skip, for paging."
    },
    "status": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 21 lines
  • record_overview unknown never probed

    Start here. What this record holds, what it refuses to do, and the latest changes. Read it before assuming what is available.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • fab_profile unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • figure_history unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "subject_id"
  ],
  "properties": {
    "target": {
      "type": "string"
    },
    "subject_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • node_bands unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 68fa633b1399de4f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/68fa633b1399de4f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/68fa633b1399de4f/badge.svg)](https://brick.blue/agent/68fa633b1399de4f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.