# walalook tools (remote · walalook.me)

File share, notes, convert, docs, photo tools + agent forum. Anonymous tier: no token, 30 calls/day.

- Trust score: 35/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `walalook.me`: 47/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-board.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-board)
- remote · `walalook.me`: 69/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-compress.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-compress)
- remote · `walalook.me`: 71/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-convert.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-convert)
- remote · `walalook.me`: 71/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-diagram.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-diagram)
- remote · `walalook.me`: 35/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-draw.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-draw)
- remote · `walalook.me`: 70/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-forum.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-forum)
- remote · `walalook.me`: 67/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-ics.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-ics)
- remote · `walalook.me`: 46/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-idphoto.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-idphoto)
- remote · `walalook.me`: 35/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-note.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-note)
- remote · `walalook.me`: 35/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-pdf.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-pdf)
- remote · `walalook.me`: 35/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-ppt.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-ppt)
- remote · `walalook.me`: 35/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-share.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-share)
- remote · `walalook.me`: 67/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-subs.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-subs)
- remote · `walalook.me`: 35/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-template.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-template)
- remote · `walalook.me`: 35/100 (this document), [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-tomd.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-tomd)
- remote · `walalook.me`: 35/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-word.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-word)
- remote · `walalook.me`: 35/100, [markdown](https://verifymcp.io/servers/me-walalook-tools/mcp-xlsx.md), [page](https://verifymcp.io/servers/me-walalook-tools/mcp-xlsx)

## Channel facts

- Endpoint: `https://walalook.me/mcp/tomd`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.11.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-10-17.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

### How do I install the walalook tools MCP server?

walalook tools is a hosted endpoint at https://walalook.me/mcp/tomd, 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 me-walalook-tools 'https://walalook.me/mcp/tomd'
```

### Cursor

```json
{
  "mcpServers": {
    "me-walalook-tools": {
      "url": "https://walalook.me/mcp/tomd"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "me-walalook-tools": {
      "type": "http",
      "url": "https://walalook.me/mcp/tomd"
    }
  }
}
```

### Codex

```toml
[mcp_servers.me-walalook-tools]
url = "https://walalook.me/mcp/tomd"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "me-walalook-tools": {
      "type": "remote",
      "url": "https://walalook.me/mcp/tomd",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add me-walalook-tools --url 'https://walalook.me/mcp/tomd' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  me-walalook-tools:
    url: "https://walalook.me/mcp/tomd"
```

### Netclaw

```json
{
  "McpServers": {
    "me-walalook-tools": {
      "Transport": "http",
      "Url": "https://walalook.me/mcp/tomd"
    }
  }
}
```

### Vellum

```bash
assistant mcp add me-walalook-tools -t streamable-http -u 'https://walalook.me/mcp/tomd'
```

### Other

```json
{
  "mcpServers": {
    "me-walalook-tools": {
      "type": "http",
      "url": "https://walalook.me/mcp/tomd"
    }
  }
}
```

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-10-17 (score 35, −35)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.13 → unverified
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified

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

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 69, +34)

- [security improvement] Injection markers: unverified → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] Tool coverage: unverified → 100

### 2026-10-14 (score 35, −33)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.03 → unverified
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-13 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 68, +33)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 100

### 2026-10-10 (score 35)

First indexed and scored.

## MCP tools (1)

### `to_markdown` (~182 tokens)

Convert a document to Markdown (input ≤8MiB): docx, xlsx, pptx, pdf, html, csv, txt — md passes through; pdf text is extracted with pdftotext (≤500 pages): tables are linearized as layout text, and a scanned PDF without a text layer is rejected. Conventions: docx headings map to # levels, tables to Markdown tables, numbered lists flatten to bullets; each xlsx sheet becomes a ## section with its table (truncated at 200 rows); each pptx slide becomes a ## Slide N section; the filename extension routes the parser, so send the real file name

Input parameters:

- `content_base64` (string, required): File content, base64
- `filename` (string, required): File name with its real extension (e.g. report.docx) — the extension routes the parser

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/me-walalook-tools/mcp-tomd#diagnostics

## Score history

- 2026-10-17: 35
- 2026-10-16: 70
- 2026-10-15: 69
- 2026-10-14: 35
- 2026-10-13: 68
- 2026-10-12: 68
- 2026-10-11: 35
- 2026-10-10: 35

## Common questions

### What is the walalook tools MCP server?

walalook tools is an MCP server listed in the public MCP registry as me.walalook/tools. File share, notes, convert, docs, photo tools + agent forum. Anonymous tier: no token, 30 calls/day. This page covers its hosted endpoint (https://walalook.me/mcp/tomd).

### Is the walalook tools MCP server safe to use?

walalook tools scores 35 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 walalook tools MCP server expose?

walalook tools exposes 1 tool: to_markdown. Their descriptions and schemas cost roughly 182 tokens of context every time the server is loaded.

### Does the walalook tools MCP server require authentication?

Its publisher declares no required credentials for walalook tools. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the walalook tools MCP server still maintained?

walalook tools is still listed as active in the MCP registry. We last reached this channel on 17 October 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://walalook.me/mcp/tomd
- Changelog RSS feed: https://verifymcp.io/servers/me-walalook-tools/mcp-tomd.xml
- Changelog JSON feed: https://verifymcp.io/servers/me-walalook-tools/mcp-tomd.json
- HTML version of this page: https://verifymcp.io/servers/me-walalook-tools/mcp-tomd