io.github.mapizarro1/foragex402
REMOTE · FORAGEX402.TABLINT.DEV · SCANNED SEP 7
Meta-search MCP for x402 agent-payable services -- find paid APIs across every registry.
Available components
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.mapizarro1/foragex402 MCP server?
io.github.mapizarro1/foragex402 is a hosted endpoint at https://foragex402.tablint.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 · foragex402.tablint.dev
claude mcp add --transport http mapizarro1-foragex402 'https://foragex402.tablint.dev/mcp'
{
"mcpServers": {
"mapizarro1-foragex402": {
"url": "https://foragex402.tablint.dev/mcp"
}
}
} {
"servers": {
"mapizarro1-foragex402": {
"type": "http",
"url": "https://foragex402.tablint.dev/mcp"
}
}
} [mcp_servers.mapizarro1-foragex402] url = "https://foragex402.tablint.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mapizarro1-foragex402": {
"type": "remote",
"url": "https://foragex402.tablint.dev/mcp",
"enabled": true
}
}
} openclaw mcp add mapizarro1-foragex402 --url 'https://foragex402.tablint.dev/mcp' --transport streamable-http
mcp_servers:
mapizarro1-foragex402:
url: "https://foragex402.tablint.dev/mcp" {
"McpServers": {
"mapizarro1-foragex402": {
"Transport": "http",
"Url": "https://foragex402.tablint.dev/mcp"
}
}
} assistant mcp add mapizarro1-foragex402 -t streamable-http -u 'https://foragex402.tablint.dev/mcp'
{
"mcpServers": {
"mapizarro1-foragex402": {
"type": "http",
"url": "https://foragex402.tablint.dev/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.
- 7 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 6 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 5 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 3 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 1 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass 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 7 Sept 2026 · Probed https://foragex402.tablint.dev/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of foragex402.tablint.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| tablint.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://foragex402.tablint.dev/mcp | Unreachable | ||
| http (plaintext) | http://foragex402.tablint.dev/mcp | HTTPS enforced |
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 →
report_missing_service ~97
Report a paid service or capability you needed but could not find in any registry -- the search returned nothing, or the results did not actually do what you needed. Describe the task you were trying to accomplish. Optionally include the price per call you would have been willing to pay. Reporting helps this capability get built.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| would_pay_usdc | – | – | – |
No output schema declared.
No examples provided.
search_services ~179
Find and compare paid API services that AI agents can purchase per-call with instant crypto/stablecoin payment -- data feeds, web search, file conversion, inference, scraping, market data, and any other pay-per-use endpoint. Searches every known service registry in one query and returns each service's URL, price per call, and payment details. Use this when you need a capability you don't have, when a task requires an external API, or when a resource responds 402 Payment Required and you want alternatives, or when the capability you need is a paid remote service rather than an installable tool. Optionally filter by max price in USDC (0.01 = one cent/call).
| Name | Type | Req | Description |
|---|---|---|---|
| max_price_usdc | – | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.mapizarro1/foragex402 MCP server?
io.github.mapizarro1/foragex402 is an MCP server listed in the public MCP registry as io.github.mapizarro1/foragex402. Meta-search MCP for x402 agent-payable services -- find paid APIs across every registry. This page covers its hosted endpoint (https://foragex402.tablint.dev/mcp).
Is the io.github.mapizarro1/foragex402 MCP server safe to use?
io.github.mapizarro1/foragex402 scores 0 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.mapizarro1/foragex402 MCP server expose?
io.github.mapizarro1/foragex402 exposes 2 tools: search_services, report_missing_service. Their descriptions and schemas cost roughly 276 tokens of context every time the server is loaded.
Does the io.github.mapizarro1/foragex402 MCP server require authentication?
Its publisher declares no required credentials for io.github.mapizarro1/foragex402. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.mapizarro1/foragex402 MCP server still maintained?
io.github.mapizarro1/foragex402 has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 31 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.