Utility runtime
One utility runtime. Many ways in.
21 tested capabilities share one implementation across the browser, Node and compatible agents. Every catalogue tool has an audited capability record.
Shared runtime coverage
- Tools audited
- 400
- Headless candidates
- 335
- Typed canary tools
- 21
- Executable locally
- 21
- Remote shared capabilities enabled
- 21
- Browser or device dependent
- 23
- Local file and media
- 30
- Network or provider dependent
- 12
Audit candidates describe extraction potential. Only tested canaries are marked executable. Legacy PHP execution is counted separately.
Application telemetry records metadata only. Submitted text, files, URLs, generated secrets and results are excluded. Remote metrics unavailable from this WordPress page are shown as unavailable, not zero.
Local execution
Install the versioned package directly:
npm install https://ursy.io/wp-content/themes/ursy-io/downloads/ursy-runtime-1.0.0.tgzimport { run } from '@ursy/runtime';
const result = await run('percentage-calculator', { value: 200, percentage: 12.5 });
console.log(result);Remote execution
Send an explicit HTTPS request to the isolated service. The same typed result is returned with remote execution and retention metadata.
const response = await fetch('https://api.ursy.io/v1/run', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({
tool: 'percentage-calculator',
input: { value: 200, percentage: 12.5 }
})
});
console.log(await response.json());Developer kit
The source archive includes local MCP, workflow composition, locked dependencies and tested connection examples. Extract it, follow its README and use Node 24 or newer for the MCP service.
Start with the contract
Read the v2 catalogue, choose a capability, and inspect its input_schema, output_schema, examples, limits and execution modes. A null runtime or schema means that tool has not been migrated to headless execution yet.
Choose where work runs
Browser and Node execution are local by default. Calling the separate remote API sends the submitted input to that service for transient processing. Existing v1 discovery and the separately versioned legacy PHP lane remain available.