How it works
Pairwise distance statistics, k-nearest isolation in the Method Lab convention, centroid centrality, PCA collinearity, mirror residual across the better principal axis when those axes are determined, an eight-bin distance histogram and a rounded fingerprint. Deterministic and geometry-only.
Inputs and units
Provide 3 to 256 planar points with finite coordinates in consistent units, and optionally a reference distance fraction between 0.01 and 0.5 for the close-pair test.
What the result contains
The full descriptor set, the histogram and a rounded fingerprint, with explicit limits. The principal-axis mirror residual is null for isotropic noncoincident covariance. It recommends no method, promotes nothing and validates no benefit.
Example MCP call
{
"name": "tour_profile",
"arguments": {
"points": [
{
"x": 0,
"y": 0
},
{
"x": 1,
"y": 0
},
{
"x": 1,
"y": 1
},
{
"x": 0,
"y": 1
},
{
"x": 0.5,
"y": 0.5
}
]
}
}Send this tool name and arguments through a connected MCP client. Discover the authoritative input schema with tools/list.
Call this engine in one command
Node.js 20+ and npm. This downloads a small remote MCP client; it does not install the engine locally.
npx --yes --package https://scorecompute.com/downloads/scorecompute-call-0.14.1.tgz scorecompute-call tour_profile --arguments '{"points":[{"x":0,"y":0},{"x":1,"y":0},{"x":1,"y":1},{"x":0,"y":1},{"x":0.5,"y":0.5}]}'Client download, PowerShell input and verification →
Direct MCP access
tour_profile is independently callable. Its generated registration deliberately disables orchestration: no planner binding or approved adapter is supplied. Do not infer composability from matching JSON fields.
Cite this engine
Version 0.2.0, source SHA-256 51b1943a8409…, release 0.16.1. Replace the access date when you cite it.
ScoreCompute. Planar tour instance profile (tour_profile), version 0.2.0, source SHA-256 51b1943a84091457dc87d71e4cd2895bd6b92271fc7fc807e66bf48ebadb213e. Release 0.16.1. https://scorecompute.com/engines/tour-profile/ (accessed YYYY-MM-DD).
All engine citations · Evidence card
Execution and availability
ScoreCompute exposes this tool through MCP Streamable HTTP. Rust computation runs on a connected worker; the public website and MCP gateway run separately. Among these 22 scientific tools, CUDA is implemented for simulate_pi; the other engines currently run on CPU. The separate contributor network has its own fixed integer Monte Carlo workload. Requests are bounded and concurrent work may be refused when capacity is occupied.
Record inputs, assumptions and returned provenance when sharing a result. The public observatory displays software client names and tool activity, without publishing calculation arguments or results.