# Clawifi (remote · api.clawifi.dev)

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

- Trust score: 76/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.clawifi.dev`: 76/100 (this document), [markdown](https://verifymcp.io/servers/atakanelik34-clawifi-mcp/api-2.md), [page](https://verifymcp.io/servers/atakanelik34-clawifi-mcp/api-2)
- pypi · `clawifi`: 39/100, [markdown](https://verifymcp.io/servers/atakanelik34-clawifi-mcp/clawifi.md), [page](https://verifymcp.io/servers/atakanelik34-clawifi-mcp/clawifi)

## Channel facts

- Endpoint: `https://api.clawifi.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 917 tokens (~61/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http atakanelik34-clawifi-mcp 'https://api.clawifi.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "atakanelik34-clawifi-mcp": {
      "url": "https://api.clawifi.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "atakanelik34-clawifi-mcp": {
      "type": "http",
      "url": "https://api.clawifi.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.atakanelik34-clawifi-mcp]
url = "https://api.clawifi.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "atakanelik34-clawifi-mcp": {
      "type": "remote",
      "url": "https://api.clawifi.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add atakanelik34-clawifi-mcp --url 'https://api.clawifi.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  atakanelik34-clawifi-mcp:
    url: "https://api.clawifi.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "atakanelik34-clawifi-mcp": {
      "Transport": "http",
      "Url": "https://api.clawifi.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add atakanelik34-clawifi-mcp -t streamable-http -u 'https://api.clawifi.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "atakanelik34-clawifi-mcp": {
      "type": "http",
      "url": "https://api.clawifi.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 76, +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.

### 2026-11-03 (score 75, +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.

### 2026-11-01 (score 74, +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.

### 2026-10-30 (score 73, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] 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”

### 2026-10-28 (score 72, +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.

### 2026-10-27 (score 71, 0)

- [functional] Server version: 1.7.7 → 1.8.0

### 2026-10-26 (score 71, +1)

- [functional] Server version: 1.7.6 → 1.7.7

### 2026-10-24 (score 70, +1)

- [functional] Server version: 1.7.5 → 1.7.6

## MCP tools (15)

### `fetch_url` (~97 tokens)

Fetch a page

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).

Input parameters:

- `force_browser` (boolean)
- `max_pages` (integer)
- `query`
- `target_selector`
- `timeout_seconds`
- `top_k` (integer)
- `url` (string, required)

### `scrape_url` (~92 tokens)

Scrape a page

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.

Input parameters:

- `formats`
- `mode` (string)
- `query`
- `target_selector`
- `timeout_seconds`
- `top_k` (integer)
- `url` (string, required)

### `extract_url` (~51 tokens)

Extract fields from a page

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

Input parameters:

- `preset`
- `schema`
- `timeout_seconds`
- `url` (string, required)

### `search_free` (~49 tokens)

Search the web

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

Input parameters:

- `include_domains`
- `max_results` (integer)
- `query` (string, required)
- `time_range`

### `map_site` (~51 tokens)

Map a site

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

Input parameters:

- `max_urls` (integer)
- `search`
- `url` (string, required)

### `start_crawl` (~53 tokens)

Start a crawl

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

Input parameters:

- `max_depth` (integer)
- `max_pages` (integer)
- `seed_url` (string, required)

### `get_crawl` (~29 tokens)

Get crawl results

Status and pages of a crawl started with start_crawl.

Input parameters:

- `crawl_id` (string, required)

### `read_artifact` (~81 tokens)

Read a stored page

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.

Input parameters:

- `artifact_id` (string, required)
- `as_markdown` (boolean)
- `max_chars` (integer)

### `create_job` (~53 tokens)

Start a background job

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

Input parameters:

- `operation` (string, required)
- `payload` (object, required)

### `get_job` (~27 tokens)

Get job results

Status and result of a job started with create_job.

Input parameters:

- `job_id` (string, required)

### `list_history` (~45 tokens)

List past calls

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

Input parameters:

- `cursor`
- `limit` (integer)
- `operation`

### `list_monitors` (~23 tokens)

List monitors

The account's Evidence Monitor checks.

Input parameters:

- `limit` (integer)

### `estimate` (~89 tokens)

Estimate credits

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.

Input parameters:

- `args`
- `operation` (string, required)

### `account` (~20 tokens)

Show the account

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

### `credits` (~28 tokens)

Show credits

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/atakanelik34-clawifi-mcp/api-2#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 71
- 2026-10-26: 71
- 2026-10-25: 70
- 2026-10-24: 70
- 2026-10-23: 69
- 2026-10-22: 65

## 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.

## Links

- Remote endpoint: https://api.clawifi.dev/mcp
- Repository: https://github.com/atakanelik34/clawifi-mcp
- Website: https://clawifi.dev/
- Changelog RSS feed: https://verifymcp.io/servers/atakanelik34-clawifi-mcp/api-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/atakanelik34-clawifi-mcp/api-2.json
- HTML version of this page: https://verifymcp.io/servers/atakanelik34-clawifi-mcp/api-2