cash.forage/forage
REMOTE · FORAGE.CASH · SCANNED SEP 20
Web search and URL-to-markdown for agents. Pay per call in USDC on Base, no signup.
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 220 tokens (~110/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the cash.forage/forage MCP server?
cash.forage/forage is a hosted endpoint at https://forage.cash/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 · forage.cash
claude mcp add --transport http cash-forage-forage 'https://forage.cash/mcp'
{
"mcpServers": {
"cash-forage-forage": {
"url": "https://forage.cash/mcp"
}
}
} {
"servers": {
"cash-forage-forage": {
"type": "http",
"url": "https://forage.cash/mcp"
}
}
} [mcp_servers.cash-forage-forage] url = "https://forage.cash/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cash-forage-forage": {
"type": "remote",
"url": "https://forage.cash/mcp",
"enabled": true
}
}
} openclaw mcp add cash-forage-forage --url 'https://forage.cash/mcp' --transport streamable-http
mcp_servers:
cash-forage-forage:
url: "https://forage.cash/mcp" {
"McpServers": {
"cash-forage-forage": {
"Transport": "http",
"Url": "https://forage.cash/mcp"
}
}
} assistant mcp add cash-forage-forage -t streamable-http -u 'https://forage.cash/mcp'
{
"mcpServers": {
"cash-forage-forage": {
"type": "http",
"url": "https://forage.cash/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 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.
- 18 Sept 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.
- 16 Sept 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.
- 14 Sept 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.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 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.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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 20 Sept 2026 · Probed https://forage.cash/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=forage.cash | CN=YR1,O=Let's Encrypt,C=US | 25 Aug 2026 | 23 Nov 2026 | RSA 2048 | SHA256-RSA | 5df9965e31552eb1fc5fdc027d49ec90b4e |
| SANs: forage.cash | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of forage.cash. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cash. | present | 38860 | 8 | Verified |
| forage.cash. | present | 45179 | 8 | Verified |
| forage.cash. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://forage.cash/mcp | Verified | 200 | |
| http (plaintext) | http://forage.cash/mcp | HTTPS enforced | 308 | https://forage.cash/mcp |
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 →
scrape ~68
Fetch any public URL and return the main content as LLM-ready markdown. Free 20/day, then pay-per-call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| maxChars | integer | – | Cap on returned markdown/text length (default 200000) |
| url | string | yes | Public http(s) URL to fetch |
No output schema declared.
No examples provided.
web_search ~104
Google web search — organic results, answer box, knowledge graph as JSON. Free 20/day, then pay-per-call via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| gl | string | – | Country code, e.g. us, fr |
| hl | string | – | Language code, e.g. en, fr |
| num | integer | – | Number of results (default 10) |
| page | integer | – | Results page (default 1) |
| q | string | yes | Search query |
No output schema declared.
No examples provided.
What is the cash.forage/forage MCP server?
cash.forage/forage is an MCP server listed in the public MCP registry as cash.forage/forage. Web search and URL-to-markdown for agents. Pay per call in USDC on Base, no signup. This page covers its hosted endpoint (https://forage.cash/mcp).
Is the cash.forage/forage MCP server safe to use?
cash.forage/forage scores 80 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 cash.forage/forage MCP server expose?
cash.forage/forage exposes 2 tools: web_search, scrape. Their descriptions and schemas cost roughly 172 tokens of context every time the server is loaded.
Does the cash.forage/forage MCP server require authentication?
No. We connected to cash.forage/forage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the cash.forage/forage MCP server still maintained?
cash.forage/forage is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.