Fitter
OCI · GHCR.IO/PXYUP/FITTER-MCP:V1.7.0 · 6 COMPONENTS · SCANNED AUG 3
Turn any website or API into structured JSON with LLM-authored declarative scraping configs.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- CVE data not yet available for this package.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency-health data not yet available.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 579 tokens (~96/item across 6 items; 5 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 2 categories
Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
oci · ghcr.io/pxyup/fitter-mcp:v1.7.0
claude mcp add pxyup-fitter -- docker run --rm -i ghcr.io/pxyup/fitter-mcp:v1.7.0
codex mcp add pxyup-fitter -- docker run --rm -i ghcr.io/pxyup/fitter-mcp:v1.7.0
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pxyup-fitter": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/pxyup/fitter-mcp:v1.7.0"
],
"enabled": true
}
}
} mcp_servers:
pxyup-fitter:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/pxyup/fitter-mcp:v1.7.0"] {
"mcpServers": {
"pxyup-fitter": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/pxyup/fitter-mcp:v1.7.0"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Jul 26 −6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +35
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 28 Jul 26 11
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Analysed oci/ghcr.io/pxyup/fitter-mcp:v1.7.0
Provenance none
Ecosystem: oci · Outcome: none
Reason: no_attestation
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
fitter_config_reference ~55
Return a condensed reference of the Fitter config format (connectors, parsers, model/field schema, placeholders, notifiers, references, limits) with working examples. Use it before authoring a config for fitter_run.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
fitter_run ~152
Run a Fitter scraping/parsing config passed inline (JSON or YAML) and return the extracted data as JSON. Fitter fetches data via a connector (HTTP request, headless browser, static value, file, ...) and extracts structured data using json/HTML/XML/xpath selectors described by a declarative model. Call fitter_config_reference first if you are unsure about the config format.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | Fitter CliItem config as a JSON or YAML string. Top-level keys: item (required), limits, references. |
| input | string | — | Optional input value (plain string or JSON), available in the config via {{{FromInput=.}}} or {{{FromInput=json.path}}} placeholders. |
No output schema declared.
No examples provided.
fitter_run_file ~116
Run a Fitter scraping/parsing config from a local JSON or YAML file and return the extracted data as JSON. Same as fitter_run but reads the config from disk.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | — | Optional input value (plain string or JSON), available in the config via {{{FromInput=.}}} or {{{FromInput=json.path}}} placeholders. |
| path | string | yes | Absolute path to a Fitter config file (.json, .yaml or .yml) with top-level keys: item (required), limits, references. |
No output schema declared.
No examples provided.
fitter_run_url ~129
Run a Fitter scraping/parsing config downloaded from an HTTP(S) URL (JSON or YAML) and return the extracted data as JSON. Same as fitter_run but fetches the config from a remote location, e.g. a raw GitHub link.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | — | Optional input value (plain string or JSON), available in the config via {{{FromInput=.}}} or {{{FromInput=json.path}}} placeholders. |
| url | string | yes | HTTP(S) URL of a Fitter config (JSON or YAML) with top-level keys: item (required), limits, references. |
No output schema declared.
No examples provided.
fitter_validate_config ~108
Validate a Fitter config (JSON or YAML) without executing it. Checks the structural rules: item/connector_config/model presence, valid response_type, that the connector has a data source, and compiles every condition/item_condition expression in the model. Returns "valid" or the validation error. Cheap and safe — use it while iterating on a config before calling fitter_run.
| Name | Type | Req | Description |
|---|---|---|---|
| config | string | yes | Fitter CliItem config as a JSON or YAML string to validate without executing it. |
No output schema declared.
No examples provided.