@orkestrel/probeSAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A claim prover that checks a case and its negative control with the workspace’s TypeScript, Oxlint, and Vitest, with eager lint and runtime onset and type warming before proof.
A claim carries a case — the edit you believe is correct — and a control, the same edit deliberately broken, naming the stage it must fail at. The receipt a proven claim earns is a one-line token naming the claim, the stage, the tool versions, and the TypeScript project that judged the candidates.
Read guides/probe.md before you make a claim. It states the prerequisites, the receipt's verification method and its limits, and what a receipt does not vouch for.
Install
npm install --save-dev @orkestrel/probe
The typescript and vitest packages are optional peers, and the oxlint package carries no peer range; probe resolves all three from the workspace it inspects.
The probe binary
Startup waits for lint and runtime while type warming continues before the first proof. For the Codex required = true setting and measured initialization times, see Registering the server.
The package installs a probe binary that serves the prove Model Context Protocol tool over a newline-delimited JSON stdio transport. Register the resolved JavaScript entry rather than a global install, an npx invocation, or the node_modules/.bin shim:
{
"mcpServers": {
"probe": {
"command": "node",
"args": ["node_modules/@orkestrel/probe/dist/bin/main.js"],
"cwd": "/srv/checkout"
}
}
}Proving a claim in process
import type { Claim } from '@orkestrel/probe'
import { Probe } from '@orkestrel/probe/server'
const claim: Claim = {
project: 'configs/src/tsconfig.core.json',
case: {
files: [
{
path: 'src/core/factories.ts',
text: "export function createGreeting(): string {\n\treturn 'hi'\n}\n",
},
],
test: {
path: 'tmp/probes/greeting.test.ts',cbeb38c1cf96OBSERVED · 2026-10-12Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add probe -- npx -y @orkestrel/[email protected]
{
"mcpServers": {
"probe": {
"command": "npx",
"args": [
"-y",
"@orkestrel/[email protected]"
]
}
}
}Exposed tools (1)
0 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
prove | write | Answers whether a TypeScript edit compiles, lints, and passes its test |
Trust audit
SAFEgrade B · trust 87/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (5 observation(s))
- Network
- declared (6 observation(s))
- Shell
- declared (2 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (15)
host_input='http://127.0.0.1:11434'
.oxfmtrc.json
.oxlintignore
.oxlintrc.json
.prettierignore
import { peers, srcBin } from '../../vite.config.ts'import { peers, srcCore, resolveWorkspacePath } from '../../vite.config.ts'import { srcServer, resolveWorkspacePath } from '../../vite.config.ts'import { peerDependencies } from '../../package.json' with { type: 'json' }import { version } from '../../package.json' with { type: 'json' }new Request('https://server.example/mcp', { headers: { origin: 'http://127.0.0.1:37757' } }),`scripts/ollama.sh` defaults to `http://127.0.0.1:11434` and `qwen3.5:2b-q4_K_M`. It requires Node
number, read off `address()`. `url` is `http://127.0.0.1:<port>` with no trailing slash, and the
loopback.url === `http://127.0.0.1:${loopback.port}` // true — IPv4 loopback, no trailing slash@orkestrel/contract, @orkestrel/emitter, @orkestrel/lsp, @orkestrel/mcp, @orkestrel/pool, @orkestrel/timeout, @orkestrel/tool, @microsoft/api-extractor
Gates applied: no_behavioural_pass.
cbeb38c1cf96full audit observations/trust-audit/mcp-server/orkestrel__probe.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-12 | cbeb38c1cf96 | SAFE | B | 87 | first audit |
Questions
What tools does @orkestrel/probe expose?
1 in total: 0 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is @orkestrel/probe safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (87/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does @orkestrel/probe need?
No credential environment variables were found in its source, so it appears to need none.
How current is this page?
The grade is for one exact copy of the source (cbeb38c1cf96), read on 2026-10-12. The repository is watched and re-audited when it changes.