Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Clawifi

REMOTE · API.CLAWIFI.DEV · 2 COMPONENTS

Agent-native internet gateway: typed search, fetch, scrape, crawl, and extract via the Clawifi API.

+4 this week 76 Trust /100

Last scanned (4 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

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 Security83
Transport & Reachability100
Schema Quality & AI Usability56
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 917 tokens (~61/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 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
Changelog

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.

  • 5 Nov 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.

  • 3 Nov 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.

  • 1 Nov 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.

  • 30 Oct 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 99 → 61 ▲ functional
    • Server version: 1.8.0 → 1.9.2 functional
    • New tool “credits” functional
    • New tool “estimate” functional
    • New tool “extract_url” functional
    • New tool “get_crawl” functional
    • New tool “get_job” functional
    • New tool “list_history” functional
    • New tool “list_monitors” functional
    • New tool “read_artifact” functional
    • New tool “start_crawl” functional
    • New tool “account” functional
    • New tool “create_job” functional
  • 28 Oct 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.

  • 27 Oct 26 0
    • Server version: 1.7.7 → 1.8.0 functional
  • 26 Oct 26 +1
    • Server version: 1.7.6 → 1.7.7 functional
  • 24 Oct 26 +1
    • Server version: 1.7.5 → 1.7.6 functional
Diagnostics

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 5 Nov 2026 · Probed https://api.clawifi.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=clawifi.dev CN=YE2,O=Let's Encrypt,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA384 6e043691393d6c2529bcbcea2a6cfea9ba0
SANs: *.clawifi.dev, clawifi.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.clawifi.dev. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
clawifi.dev. present 2371 13 Verified
api.clawifi.dev. 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=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.clawifi.dev/mcp Verified 200
http (plaintext) http://api.clawifi.dev/mcp HTTPS enforced 301 https://api.clawifi.dev/mcp
MCP tools · 15 exposed · ~788 tokens

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 →

Tool Tokens
account ~20

The signed-in account: name, plan and this month's credits.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

create_job ~53

Run a billable operation (fetch, batch_fetch, extract, crawl, research, ...) as a background job. Returns a job id for get_job.

NameTypeReqDescription
operationstringyes–
payloadobjectyes–

Structured output declared, but exposes no named fields.

No examples provided.

credits ~28

The credit balance, what this month's calls were charged, the plan's monthly credits and when they renew.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

estimate ~89

What a call would cost in credits before running it: minimum (what the balance must cover), maximum or a caveat, what raises it, the balance and would_402. operation is a tool name (fetch_url, start_crawl, research, ...) or a job operation; args are that call's arguments. Runs nothing and charges nothing.

NameTypeReqDescription
args–––
operationstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

extract_url ~51

Extract structured fields from a URL: a preset (article, product, ...) or a field schema.

NameTypeReqDescription
preset–––
schema–––
timeout_seconds–––
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

fetch_url ~97

Fetch one URL (page or PDF) as clean markdown with route diagnostics. query returns only the top_k passages that answer it. force_browser renders it in a browser (3 credits instead of 1).

NameTypeReqDescription
force_browserboolean––
max_pagesinteger––
query–––
target_selector–––
timeout_seconds–––
top_kinteger––
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_crawl ~29

Status and pages of a crawl started with start_crawl.

NameTypeReqDescription
crawl_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_job ~27

Status and result of a job started with create_job.

NameTypeReqDescription
job_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_history ~45

The account's past calls, newest first; operation filters by name (e.g. search_free).

NameTypeReqDescription
cursor–––
limitinteger––
operation–––

Structured output declared, but exposes no named fields.

No examples provided.

list_monitors ~23

The account's Evidence Monitor checks.

NameTypeReqDescription
limitinteger––

Structured output declared, but exposes no named fields.

No examples provided.

map_site ~51

List a site's discoverable URLs (sitemap, robots, links) from a seed URL; search filters them.

NameTypeReqDescription
max_urlsinteger––
search–––
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

read_artifact ~81

Read a stored artifact of the account by its id, such as a page get_crawl or fetch_url lists: an HTML page comes back as markdown (as_markdown=false for the raw HTML), capped at max_chars. Free.

NameTypeReqDescription
artifact_idstringyes–
as_markdownboolean––
max_charsinteger––

Structured output declared, but exposes no named fields.

No examples provided.

scrape_url ~92

Scrape a URL into LLM-ready formats (markdown, text, links, metadata, html, screenshot, state_json). query keeps only the top_k passages of markdown and text that answer it.

NameTypeReqDescription
formats–––
modestring––
query–––
target_selector–––
timeout_seconds–––
top_kinteger––
urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

search_free ~49

Search the web and return ranked results (title, URL, snippet).

NameTypeReqDescription
include_domains–––
max_resultsinteger––
querystringyes–
time_range–––

Structured output declared, but exposes no named fields.

No examples provided.

start_crawl ~53

Start a crawl from a seed URL in the background. Returns a crawl id for get_crawl.

NameTypeReqDescription
max_depthinteger––
max_pagesinteger––
seed_urlstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Clawifi MCP server?

Clawifi is a hosted endpoint at https://api.clawifi.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 · api.clawifi.dev

# add to Claude Code
claude mcp add --transport http atakanelik34-clawifi-mcp 'https://api.clawifi.dev/mcp'
Common questions

What is the Clawifi MCP server?

Clawifi is an MCP server listed in the public MCP registry as io.github.atakanelik34/clawifi-mcp. Agent-native internet gateway: typed search, fetch, scrape, crawl, and extract via the Clawifi API. This page covers its hosted endpoint (https://api.clawifi.dev/mcp).

Is the Clawifi MCP server safe to use?

Clawifi scores 76 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 Clawifi MCP server expose?

Clawifi exposes 15 tools: fetch_url, scrape_url, extract_url, search_free, map_site, and 10 more. Their descriptions and schemas cost roughly 788 tokens of context every time the server is loaded.

Does the Clawifi MCP server require authentication?

No. We connected to Clawifi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Clawifi MCP server still maintained?

Clawifi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.