Sancho Fetch
MCPB · SANCHO.MCPB · 2 COMPONENTS
Local-first public-data MCP server that writes inspectable records and working files.
Available components
Last scanned (8 hours ago)
Scores higher than 90% of MCPB servers
Category Data and Analytics
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 → Why this is hard to score →
Supply Chain Security11
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 10 of 10 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Install-script risk not yet assessed.Unverified
- 2 of 10 dependencies flagged as unhealthy. View diagnostics → Partial
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 (MPL-2.0).Pass
- Actively maintained (last published 48 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1002 tokens (~58/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 47. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed mcpb/https://github.com/panth-net/sancho-fetch/releases/download/v0.3.1/sancho.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 10 packages
| Packages resolved | 10 |
|---|---|
| Stale | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch_world_bank fetch.world_bank ~313
World Bank development indicators for every country and year: population, GDP, poverty, unemployment, inflation, life expectancy, health, education, energy, climate. Path-driven API client covering the data API (indicators by country/region/source) and companion search APIs for projects and DDH datasets. Use `;` to separate multiple countries/indicators in a single call, or `all` for everything. catalog.json enumerates 10 families across both APIs.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Catalog base alias: "v2" (data API), "search_v2" (project search), "ddh" (DDH catalog). |
| body | object | – | Body payload (rare). |
| method | string | – | HTTP method (World Bank API is GET-only). |
| params | object | – | Query parameters. `format` (must be "json" for our usage), `per_page` (1-32500), `page`, `date` (year or "YYYY:YYYY"), `source` (DB ID, e.g. 2 for WDI), `mrv` (most recent N), `frequency` (Y/Q/M). Fo… |
| path | string | yes | World Bank API path. `/country/{ISO3}/indicator/{INDICATOR}` for time-series, `/indicator`/`/sources`/`/topic` for catalog browsing, `/projects` for project search. |
No output schema declared.
No examples provided.
sancho_cache_status Cache status ~66
Report cache status for a module or a specific request. Optional inspection only -- fetch tools reuse the cache automatically, so there is no need to check before running.
| Name | Type | Req | Description |
|---|---|---|---|
| max_age_seconds | integer | – | – |
| module_id | string | yes | – |
| request | object | – | – |
No output schema declared.
No examples provided.
sancho_custom_status Custom overrides ~22
List custom modules and whether upstream is newer than each override.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sancho_env_open API key file info ~34
Surface the .env path and which env vars a provider needs. Never reads values.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | – | – |
No output schema declared.
No examples provided.
sancho_env_recommend Recommend API keys ~78
Given a natural-language description of the data the user wants, return ranked provider candidates with the env-var NAMES they need and which of those are missing in the user's .env. Values are never read or printed -- only names + missing status + sign-up URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
sancho_export_to_project Export to project ~48
Copy a cached record into a project's 'sancho-downloads/' folder.
| Name | Type | Req | Description |
|---|---|---|---|
| cache_record | string | yes | – |
| label | string | – | – |
| project | string | – | – |
No output schema declared.
No examples provided.
sancho_fetch_run Run data fetch ~57
Execute one fetch module with the given input payload. Returns a run summary with a truncated preview; the full dataset is written to the file at primary_output_path.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | – |
| module_id | string | yes | – |
No output schema declared.
No examples provided.
sancho_fetched_data_audit Fetched-data audit ~23
Find fetched-data records produced by older module versions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sancho_find_sources Find data sources ~50
Rank module candidates for a natural-language data request. The cheap first step for choosing a source.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
sancho_inventory Full data catalog ~54
List built-in starter packs and fetch providers, plus the workspace's custom modules. This is the full catalog and it is large -- when you already know what data is wanted, sancho_find_sources returns just the relevant candidates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sancho_log_show Run details ~40
Show every event plus the full repair packet for one run_id -- the deep-dive after a failed run.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | string | yes | – |
No output schema declared.
No examples provided.
sancho_log_tail Recent run log ~73
Tail recent run/error events from logs/runs.jsonl (or errors.jsonl). Useful after a playbook/multi-unit run or a failure; a single run's summary already contains its own evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| errors | boolean | – | – |
| limit | integer | – | – |
| module_id | string | – | – |
No output schema declared.
No examples provided.
sancho_mode Developer mode ~23
Return only the Sancho developer-mode boolean without exposing .env contents.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sancho_module_show Inspect module ~32
Inspect one module: manifest, schema, override status, last run.
| Name | Type | Req | Description |
|---|---|---|---|
| module_id | string | yes | – |
No output schema declared.
No examples provided.
sancho_paths Workspace paths ~30
Return every relevant Sancho Fetch path (workspace, source, fetched-data, logs, env, library).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sancho_update_check Update check ~32
Non-mutating status report: module versions, local edits, custom overrides, gitignore, .env presence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sancho_update_preview Update preview ~27
Per-module preview with risk and recommended action.
| Name | Type | Req | Description |
|---|---|---|---|
| module_id | string | – | – |
No output schema declared.
No examples provided.
How do I install the Sancho Fetch MCP server?
Sancho Fetch ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. The MCP registry declares no SHA-256 for this bundle, so there is no published digest to check the download against.
mcpb · sancho.mcpb
Download bundleThe MCP registry declares no SHA-256 for this bundle, so there is no published digest to check it against. Open it with an MCPB-capable host such as Claude Desktop.
What is the Sancho Fetch MCP server?
Sancho Fetch is an MCP server listed in the public MCP registry as io.github.panth-net/sancho-fetch. Local-first public-data MCP server that writes inspectable records and working files. This page covers its MCPB bundle (https://github.com/panth-net/sancho-fetch/releases/download/v0.3.1/sancho.mcpb).
Is the Sancho Fetch MCP server safe to use?
Sancho Fetch scores 56 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sancho Fetch MCP server expose?
Sancho Fetch exposes 17 tools: fetch_world_bank, sancho_cache_status, sancho_custom_status, sancho_env_open, sancho_env_recommend, and 12 more. Their descriptions and schemas cost roughly 1,002 tokens of context every time the server is loaded.
What licence is the Sancho Fetch MCP server under?
Sancho Fetch declares the MPL-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.