silicon_truth_bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STB_BACKEND | No | Default backend. Set to 'verdi' for real Verdi NPI access. | fake |
| STB_LAUNCHER | No | Worker launcher. V1 only implements local. | local |
| STB_DEV_TOOLS | No | Set to 'true' to register admin_* development tools. | false |
| STB_VERDI_HOME | No | Verdi installation path; required when STB_BACKEND=verdi. Defaults to $VERDI_HOME if set. | $VERDI_HOME |
| STB_ALLOWED_ROOTS | No | Colon-separated list of root directories that the server is allowed to access (design DB, source, FSDB, artifacts). | current directory |
| STB_ARTIFACT_ROOT | No | Directory where artifact files are written. | .stb/artifacts |
| STB_VERDI_RELEASE | No | Explicit Verdi release declaration for custom installation layouts. | auto-detect |
| STB_WORKER_PYTHON | No | Python interpreter used to start the NPI worker. | MCP server current Python |
| STB_HARD_TIMEOUT_SEC | No | Supervisor hard timeout in seconds. | 300 |
| STB_MAX_ARTIFACT_BYTES | No | Maximum size in bytes for a single artifact. | 1073741824 |
| STB_MAX_OBJECT_HANDLES | No | Maximum number of language object handles to retain. | 100000 |
| STB_DEFAULT_TIMEOUT_SEC | No | Soft deadline for worker requests in seconds. | 120 |
| STB_HARD_RESPONSE_BYTES | No | Hard response size limit in bytes. | 16777216 |
| STB_MAX_ACTIVE_CONTEXTS | No | Maximum number of active worker/contexts. | 4 |
| STB_NORMAL_RESPONSE_BYTES | No | Normal response size limit in bytes. | 4194304 |
| STB_ALLOW_UNVERIFIED_VERDI | No | Set to 'true' to allow unverified Verdi releases to run after capability probe. | false |
| STB_MAX_ARTIFACT_TOTAL_BYTES | No | Maximum total bytes for all artifacts. | 21474836480 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| context_manageC | Open, reload, close, list, get status, or release context objects. |
| wave_manageC | Attach, reload, detach, list, or get status for waveform resources. |
| catalogC | Discover context-specific models, properties, relations, and operators. |
| object_resolveC | Resolve an exact object. For waveform signals set model='waveform', wave_id, and name; netlist is the default model. |
| object_getA | Read properties for exact ObjectRef entries returned by resolve or query. |
| object_queryB | Run a bounded declarative object query. Set model, scope, npi_types or semantic_classes; waveform queries also require wave_id. |
| object_traverseC | Traverse a cataloged relation from ObjectRef roots with bounded depth. |
| connectivity_directA | Return one-hop driver or load evidence for exact design signal names. |
| traceB | Return a bounded driver, load, path, fanin, or fanout evidence graph. |
| trace_active_driverB | Evaluate active and feasible driver branches for signals at a wave time. |
| trace_value_originC | Trace sampled value origin across state boundaries at a wave time. |
| wave_valueA | Read typed waveform values. Request requires signals and unit-bearing times such as ['200ns']; set wave_id when multiple waves are attached. |
| wave_changesC | Read bounded waveform transitions. Request requires signals, start, and end. |
| wave_computeC | Run a typed bounded waveform operation such as sample, statistics, compare, period, pulse, xz, or first_divergence. |
| source_contextC | Read bounded source context anchored to an exact ObjectRef. |
| mappingC | Resolve, validate, or explain deterministic design-to-wave mappings. |
| artifactD | Manage bounded evidence artifacts and asynchronous jobs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nomatic163/silicon_truth_bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server