MONEYGRID
REMOTE · MONEYGRID.SKIBUNYI.WORKERS.DEV
Four x402 tools: endpoint checks, extraction, evidence verification, domain intelligence.
Available components
Last scanned (19 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 405 tokens (~81/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 23 Oct 26 0
- Server version: 1.3.0 → 1.4.0 functional
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 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.
- 14 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 77. That category is still filling its 30-day observation window: 21 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.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 60 to 70. That category is still filling its 30-day observation window: 18 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.
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 · Probed https://moneygrid.skibunyi.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=skibunyi.workers.dev | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 41fa19643bba938513a5c89c05cf6056 |
| SANs: skibunyi.workers.dev, *.skibunyi.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of moneygrid.skibunyi.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://moneygrid.skibunyi.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://moneygrid.skibunyi.workers.dev/mcp | Served over HTTP | 200 |
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 →
griddata_domain ~63
Paid read-only domain intelligence. Resolves current public DNS A-record data and returns timestamped hashed evidence. Use when an agent needs current domain/DNS evidence without maintaining its own resolver.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http/https URL whose hostname should be inspected. |
No output schema declared.
No examples provided.
gridextract_markdown ~62
Paid read-only web extraction for agents. Fetches one public web URL and returns bounded clean text plus evidence hash and receipt metadata. Use when an agent needs compact machine-readable page content.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http/https page URL including scheme. |
No output schema declared.
No examples provided.
gridverify_evidence ~68
Paid read-only URL evidence preflight ($0.05). Checks HTTP accessibility and operational risk flags, with response-sample hash and timestamp. Does not fact-check claims, establish source credibility, or verify factual truth.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http/https evidence URL including scheme. |
No output schema declared.
No examples provided.
gridwatch_preflight ~98
$0.02 read-only endpoint preflight. Use before an agent depends on or pays an unfamiliar API, webhook or URL. Returns reachability, HTTP status, latency, risk flags and SHA-256 evidence. Rejects private/local hosts and malformed URLs; unreachable/upstream failures are returned explicitly rather than fabricated.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public http/https endpoint URL including scheme. Private/local hosts and nonstandard ports are rejected. |
No output schema declared.
No examples provided.
moneygrid_fetch ~114
DEFAULT ($0.01/call). Fetch fresh content from one public HTTP/HTTPS URL and return up to 100k characters of machine-ready text with source metadata, timestamp and SHA-256 provenance. Use for web retrieval when you need current source content. Rejects private/local hosts, unsupported schemes, invalid URLs, oversized inputs, and upstream timeouts; failed upstream requests return explicit status/error information.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public HTTP/HTTPS URL including scheme. Private/local hosts and nonstandard ports are rejected. |
No output schema declared.
No examples provided.
How do I install the MONEYGRID MCP server?
MONEYGRID is a hosted endpoint at https://moneygrid.skibunyi.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · moneygrid.skibunyi.workers.dev
claude mcp add --transport http scimo2021-moneygrid-gridwatch 'https://moneygrid.skibunyi.workers.dev/mcp'
What is the MONEYGRID MCP server?
MONEYGRID is an MCP server listed in the public MCP registry as io.github.scimo2021/moneygrid-gridwatch. Four x402 tools: endpoint checks, extraction, evidence verification, domain intelligence. This page covers its hosted endpoint (https://moneygrid.skibunyi.workers.dev/mcp).
Is the MONEYGRID MCP server safe to use?
MONEYGRID scores 82 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 MONEYGRID MCP server expose?
MONEYGRID exposes 5 tools: moneygrid_fetch, gridwatch_preflight, gridextract_markdown, gridverify_evidence, griddata_domain. Their descriptions and schemas cost roughly 405 tokens of context every time the server is loaded.
Does the MONEYGRID MCP server require authentication?
No. We connected to MONEYGRID without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MONEYGRID MCP server still maintained?
MONEYGRID 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.