scamgate
PYPI · SCAMGATE
Offline scam check for agents: verify links and payments before acting (allow, ask or deny).
Available components
Last scanned (17 hours ago)
Scores higher than 66% of PyPI servers
Category Security
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 4 of 37 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 odaiameera/scamgate). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 500 tokens (~166/item across 3 items; 3 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 Management30
- Stability observed for 9 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 (100% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- 26 Oct 26 81
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 4 Nov 2026 · Analysed pypi/scamgate@0.3.3
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 | odaiameera/scamgate |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/odaiameera/scamgate/.github/workflows/release.yml@refs/tags/v0.3.3 |
| Rekor log index | 3474760605 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8abc3194dca387f67a4ecdcaa77a8f30430267b94ea84dace6d2b78ed3ab3ed4 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 37 packages
| Packages resolved | 37 |
|---|---|
| Stale | 3 |
| 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 →
check_payment ~238
Check a payment before making it. Returns a verdict: decision (allow | ask | deny), risk_score 0-100 and plain-English reasons. If the decision is ask, stop and show the reasons to the human. If deny, do not proceed. Results are advisory, not a guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | Amount to pay. |
| bank_details_changed | – | – | True if the payee's account details changed recently. |
| budget | – | – | The spending limit the human gave for this task. |
| context_text | – | – | The messages or page text that led to this payment. |
| currency | string | yes | e.g. EUR, GBP, USDT. |
| is_new_payee | – | – | True if this payee has never been paid before. scamgate checks your payee history rather than taking this on trust. |
| method | string | yes | card, bank_transfer, crypto, gift_card or other. |
| payee_account | string | yes | IBAN, wallet address, merchant id, etc. |
| payee_name | string | yes | Who is being paid. |
| vop_result | – | – | Verification of Payee result, if available. |
| Name | Type | Req | Description |
|---|---|---|---|
| advisory | string | – | – |
| checked_host | – | – | For links: the host scamgate judged, the one a browser would open. If it isn't where you expected the link to go, treat that as a warning. Empty for payments and unreadable links. |
| decision | – | yes | – |
| reasons | array | – | – |
| risk_score | integer | yes | – |
| summary | string | yes | – |
| warnings | array | – | Notes about the check itself, e.g. a stale feed cache |
No examples provided.
check_url ~117
Check a link before opening it. Returns a verdict: decision (allow | ask | deny), risk_score 0-100, plain-English reasons, and checked_host, the host the link really opens. If the decision is ask, stop and show the reasons to the human. If deny, do not proceed. Results are advisory, not a guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| intent | – | – | What the agent is trying to do, e.g. "book a hotel in Galway". |
| url | string | yes | The full URL the agent is about to open. |
| Name | Type | Req | Description |
|---|---|---|---|
| advisory | string | – | – |
| checked_host | – | – | For links: the host scamgate judged, the one a browser would open. If it isn't where you expected the link to go, treat that as a warning. Empty for payments and unreadable links. |
| decision | – | yes | – |
| reasons | array | – | – |
| risk_score | integer | yes | – |
| summary | string | yes | – |
| warnings | array | – | Notes about the check itself, e.g. a stale feed cache |
No examples provided.
update_feeds ~77
Refresh scamgate's phishing lists now. Use it when a scamgate verdict or status says the lists are missing or stale. Takes no arguments: it always downloads the default lists from their fixed sources, and does nothing if they were refreshed in the last hour. With automatic refresh on, the lists also refresh by themselves every 6 hours.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| failed | object | yes | Lists that couldn't be downloaded; their old copy is kept. |
| not_configured | object | yes | Optional lists that need a key first. |
| skipped | string | yes | "fresh" (refreshed in the last hour), "busy" (another refresh is running) or empty. |
| summary | string | yes | One line per list, for the human. |
| updated | array | yes | Lists downloaded now. |
No examples provided.
How do I install the scamgate MCP server?
scamgate runs locally as a PyPI package, launched with uvx scamgate. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · scamgate
claude mcp add odaiameera-scamgate -- uvx scamgate
What is the scamgate MCP server?
scamgate is an MCP server listed in the public MCP registry as io.github.odaiameera/scamgate. Offline scam check for agents: verify links and payments before acting (allow, ask or deny). This page covers its PyPI package (scamgate).
Is the scamgate MCP server safe to use?
scamgate scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 scamgate MCP server expose?
scamgate exposes 3 tools: check_url, check_payment, update_feeds. Their descriptions and schemas cost roughly 432 tokens of context every time the server is loaded.
Is the scamgate MCP server still maintained?
scamgate is still listed as active in the MCP registry. We last reached this channel on 4 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 scamgate MCP server under?
scamgate declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.