Staan
PYPI · STAAN-MCP
Web search with full-page content and grounded answers from the Staan API.
Available components
Last scanned (14 hours ago)
Scores higher than 92% of PyPI servers
Category Search and Retrieval
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to MarcinWolnyEU/Staan-MCP). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 24 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 528 tokens (~264/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −14
- Malware scan: pass → unverified ▼ security
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 pypi/staan-mcp@1.0.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | MarcinWolnyEU/Staan-MCP |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/MarcinWolnyEU/Staan-MCP/.github/workflows/release.yml@refs/tags/v1.0.1 |
| Rekor log index | 3223335587 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:3537a2b518df4dc50d777e5d24560a4748cc614bbc1bc45ef094990d8ee84fed |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | uv_build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| 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 →
answer Staan answer ~178
Answer a question with citations, grounded in web pages or in sources you supply. Use it instead of web_search when you want a ready answer created by another LLM.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | – | – | Restrict the answer to one website, a bare domain such as 'lemonde.fr'. Ignored when sources is given. |
| language | string | – | Language of the answer. |
| mode | string | – | 'short' is concise, 'long' detailed. |
| query | string | yes | The question to answer. |
| simple_response | boolean | – | false returns the complete raw Staan response instead of {answer}. |
| sources | – | – | Your own sources to answer from, instead of a web search. |
| sources_mode | string | – | With sources: 'search' fetches and ranks the URLs, 'context' uses the given content directly without fetching. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | Answer text in Markdown; footnote citations ([^1]) and the cited URLs at the end, unless simple_response=false. |
No examples provided.
web_search Staan web search ~317
Search the internet. Returns ranked results as a JSON array of {"title", "url", "snippet", "full_content"?}.
| Name | Type | Req | Description |
|---|---|---|---|
| exclude_domains | – | – | Drop results from these sites, e.g. ['pinterest.com']; subdomains too. At most 10. Not with include_domains. |
| full_content | string | – | Page text returned with each result. Default 'none' omits it; 'markdown' adds it and makes the response very large; 'html' is much larger still. |
| include_domains | – | – | Only return results from these sites, e.g. ['wikipedia.org']; subdomains match. At most 10. Not with exclude_domains. |
| market | – | – | Language-country market(s) to search: fr-fr, de-de, en-us, en-gb, en-fr, en-ca, en-au, en-in, en-ie, en-nz, en-za, en-sg. Pass one, a list, or wildcards ('en-*' for all English markets, '*' for all).… |
| offset | integer | – | Offset of the first result, for paging: pages hold up to 10 results, at most 40 per query. |
| query | string | yes | Search query in natural language. |
| simple_response | boolean | – | false returns the raw Staan response, one entry per market, instead of the flat list. |
No output schema declared.
No examples provided.
How do I install the Staan MCP server?
Staan runs locally as a PyPI package, launched with uvx staan-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · staan-mcp
claude mcp add marcinwolnyeu-staan-mcp -- uvx staan-mcp
What is the Staan MCP server?
Staan is an MCP server listed in the public MCP registry as io.github.MarcinWolnyEU/staan-mcp. Web search with full-page content and grounded answers from the Staan API. This page covers its PyPI package (staan-mcp).
Is the Staan MCP server safe to use?
Staan scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Staan MCP server expose?
Staan exposes 2 tools: web_search, answer. Their descriptions and schemas cost roughly 495 tokens of context every time the server is loaded.
Is the Staan MCP server still maintained?
Staan is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Staan MCP server under?
Staan declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Staan MCP server?
VerifyMCP ran 16 checks on Staan, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.