Search, save and rate AI tools people shared in chats. Local catalogue, any model or none.
Nothing to run from here
Verify API is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
AI claim verification MCP endpoint with x402 payments and stealth web fetch
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http verify-api-mcp https://verify.drain54.my.id
# 2 — ask your agent for something these tools do
# verify_ai_claim, check_endpoint_health, solve_captcha and 5 more
Verify API costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
DRAll 1 server
drain541 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http verify-api-mcp https://verify.drain54.my.idReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Verify whether an AI model, API provider, pricing claim, or infrastructure assertion is true today using live web evidence. Returns deterministic verdicts (TRUE, FALSE, PARTIALLY_TRUE, UNREACHABLE, UNVERIFIED) with cited sources and confidence scores. Requires x402 micropayment (0.01 USDC on Base). When to use: Fact-checking an AI provider's claims, pricing, or model availability. When NOT to use
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The specific AI infrastructure claim or assertion to verify. |
| depth | string | no | Verification depth: 'standard' (0.01 USDC) or 'deep' (0.03 USDC). |
Probe and verify the reachability, HTTP status code, latency, and operational health of an AI API endpoint or web service. Follows redirects with a 15-second timeout. Requires x402 micropayment (0.01 USDC on Base). When to use: Check if a specific API URL or model endpoint is online, responding, or returning 5xx/402 errors. When NOT to use: Do NOT use for general domain WHOIS or DNS record lookup
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The target API or service endpoint URL to probe. |
Solve web CAPTCHA challenges (Turnstile, hCaptcha, reCAPTCHA v2, Arkose, Cloudflare) and return a valid solution token. Automatically retries once on failure without double charging. Requires x402 payment on Base. When to use: Use when an agent encounters a bot wall or CAPTCHA challenge during automated web workflows. When NOT to use: Do NOT use for non-CAPTCHA auth, 2FA/OTP codes, or general log
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | yes | The specific type of CAPTCHA challenge encountered on the target page. |
| sitekey | string | yes | The CAPTCHA sitekey parameter extracted from the target page DOM or iframe. |
| url | string | yes | The full target page URL where the CAPTCHA challenge is hosted. |
Retrieve current x402 pricing per 1,000 CAPTCHA solves across all supported types (Turnstile, hCaptcha, reCAPTCHA v2, Arkose, Cloudflare). Free endpoint with zero parameters. When to use: Check current rates and atomic USDC requirements before calling solve_captcha. When NOT to use: Do NOT use to submit or solve CAPTCHA challenges.
No parameter schema on file.
Extract clean, readable Markdown and metadata from any public webpage for LLM ingestion, stripping ads, popups, and navigational clutter. Returns clean markdown, title, description, character count, and estimated tokens. Requires x402 micropayment (0.005 USDC on Base). When to use: Ingesting articles, blog posts, documentation, or news pages into LLM context. When NOT to use: Do NOT use for raw b
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Full target webpage URL to extract markdown from. |
| include_links | boolean | no | Preserve markdown hyperlinks. |
| include_images | boolean | no | Preserve markdown image tags. |
Execute live web searches using multi-engine chain (TinyFish, DuckDuckGo, Jina) without monthly API subscriptions. Returns fresh source URLs, titles, and snippets. Requires x402 micropayment (0.005 USDC on Base). When to use: Real-time web browsing and information retrieval for AI agents. When NOT to use: Do NOT use for deep recursive crawling of entire sites. Parameters: - query (string, requ
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Web search query. |
| limit | integer | no | Number of results to return. |
Extract structured JSON data matching a custom schema directly from any webpage. Extracts clean content and processes schema mapping via fast LLM parsing. Requires x402 micropayment (0.015 USDC on Base). When to use: Scraping structured data (product specs, prices, jobs, articles) into clean JSON. When NOT to use: Do NOT use for general open-ended chat without a defined schema. Parameters: - `ur
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Target webpage URL. |
| schema | object | yes | Schema definition or list of fields to extract. |
| instructions | string | no | Optional instructions for parsing or field formatting. |
Fetch webpage HTML with modern browser TLS and header impersonation (Sec-Ch-Ua, realistic headers) to bypass bot protection and detect anti-bot challenges. Requires x402 micropayment (0.01 USDC on Base). When to use: Fetching websites that block standard cURL or basic HTTP libraries with 403 Forbidden. When NOT to use: Do NOT use for downloading giant binary files (videos, zip archives). Paramet
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Target webpage URL. |
| custom_headers | object | no | Optional custom headers. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Verify API or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 93 / 100
Release 1.0.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest9f98799f9421bfcb1756fa9be0a5684de877ea95d5f4695bbf9f767aa183b726
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| verify_ai_claim | untrusted-input | untrusted-input: keyword "web_search" |
| check_endpoint_health | no tags | |
| solve_captcha | state-write | state-write: declares readOnlyHint: false |
| get_captcha_pricing | no tags | |
| read_web_page | no tags | |
| search_web | untrusted-input | untrusted-input: keyword "web_search" |
| extract_json_from_web | no tags | |
| fetch_stealth_web | untrusted-input | untrusted-input: keyword "fetch" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest9f98799f9421bfcb
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Verify API can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.