io.github.APProj/vendor-status-mcp
MCPB · VENDOR-STATUS-MCP.MCPB
Status-page map for 1,100+ SaaS/cloud vendors plus 15,700+ incidents. No API key.
Available components
Last scanned (3 hours ago)
Scores higher than 90% of MCPB servers
Category Monitoring and Observability
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 Security0
- 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 could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).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 45 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 743 tokens (~106/item across 7 items; 7 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 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
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.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 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/APVentureEngine/vendor-status-mcp/releases/download/v0.1.2/vendor-status-mcp.mcpb@0.1.2
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 →
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 →
dataset_status ~49
Coverage and freshness of the underlying dataset: vendors mapped, how many have machine-readable feeds, incidents on record, incidents in the last 30 days, platform breakdown, poll cadence, license and bulk downloads.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
find_vendor ~132
Resolve a SaaS/cloud vendor by name, slug or status-page domain to its entry in the 1,100+ vendor status-page map: status page URL, platform (Statuspage, Instatus, status.io, Better Stack, ...), whether a machine-readable feed exists, and its state in the newest poll. Use this first when unsure of the exact vendor slug.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max matches returned, 1-25 (default 8). |
| query | string | yes | Vendor name, slug or domain, e.g. 'cloudflare', 'status.stripe.com', 'twilio'. |
No output schema declared.
No examples provided.
status_feed_urls ~77
The machine-readable endpoints for one vendor's status page — summary JSON, incidents JSON, RSS and Atom where the platform provides them — so an agent or a script can poll the vendor directly without a key. Also returns this dataset's normalized history JSON for the vendor.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor | string | yes | Vendor name, slug or status-page domain. |
No output schema declared.
No examples provided.
vendor_incidents ~139
One vendor's incident history as its status page posted it: title, state, impact, start/resolve timestamps, latest update text and the incident URL, newest first. Histories go back weeks to years depending on what the vendor's page exposes.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max incidents returned, 1-200 (default 20). |
| since | string | – | Only incidents that started on/after this date, YYYY-MM-DD. |
| state | string | – | Only this incident state, e.g. 'resolved', 'investigating', 'monitoring'. |
| vendor | string | yes | Vendor name, slug or status-page domain. |
No output schema declared.
No examples provided.
vendor_resolution_times ~79
How long one vendor's incidents take to be declared resolved: median, 90th percentile, count over 24h and the longest on record, computed from the vendor's own posted start and resolve timestamps (maintenance and inferred resolutions excluded). Not an uptime or SLA number.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor | string | yes | Vendor name, slug or status-page domain. |
No output schema declared.
No examples provided.
vendor_status ~75
Current state of one vendor from the newest daily poll: ok / degraded / partial / major / maintenance / unknown, the vendor's own status line, open incident count and the poll timestamp. Says plainly that it is a daily poll, not a live probe.
| Name | Type | Req | Description |
|---|---|---|---|
| vendor | string | yes | Vendor name, slug or status-page domain. |
No output schema declared.
No examples provided.
vendors_down_now ~128
Every vendor that was NOT fully operational in the newest poll, worst first (major, partial, degraded, then maintenance), with counts by state across all polled vendors. Use for 'which SaaS vendors have incidents right now'.
| Name | Type | Req | Description |
|---|---|---|---|
| include_maintenance | boolean | – | Include scheduled maintenance (default true). |
| include_unknown | boolean | – | Include vendors whose page could not be read (default false). |
| limit | integer | – | Max vendors returned, 1-500 (default 50). |
| state | string | – | Only this state: major, partial, degraded, maintenance or unknown. |
No output schema declared.
No examples provided.
How do I install the io.github.APProj/vendor-status-mcp server?
io.github.APProj/vendor-status-mcp 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 · vendor-status-mcp.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 io.github.APProj/vendor-status-mcp server?
io.github.APProj/vendor-status-mcp is listed in the public MCP registry as io.github.APProj/vendor-status-mcp. Status-page map for 1,100+ SaaS/cloud vendors plus 15,700+ incidents. No API key. This page covers its MCPB bundle (https://github.com/APVentureEngine/vendor-status-mcp/releases/download/v0.1.2/vendor-status-mcp.mcpb).
Is the io.github.APProj/vendor-status-mcp server safe to use?
io.github.APProj/vendor-status-mcp 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 io.github.APProj/vendor-status-mcp server expose?
io.github.APProj/vendor-status-mcp exposes 7 tools: find_vendor, vendor_status, vendors_down_now, vendor_incidents, vendor_resolution_times, and 2 more. Their descriptions and schemas cost roughly 679 tokens of context every time the server is loaded.
What licence is the io.github.APProj/vendor-status-mcp server under?
io.github.APProj/vendor-status-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.