# Fiperly (remote · www.fiperly.de)

Fiperly: AI websites, Agent-Ready, KI-Gedaechtnis, talks and the book on AI. Read-only.

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

## Components

- remote · `www.fiperly.de`: 68/100 (this document), [markdown](https://verifymcp.io/servers/de-fiperly-fiperly/mcp-php.md), [page](https://verifymcp.io/servers/de-fiperly-fiperly/mcp-php)

## Channel facts

- Endpoint: `https://www.fiperly.de/mcp.php`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

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

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 403 tokens (~80/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 25% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Fiperly MCP server?

Fiperly is a hosted endpoint at https://www.fiperly.de/mcp.php, 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 de-fiperly-fiperly 'https://www.fiperly.de/mcp.php'
```

### Cursor

```json
{
  "mcpServers": {
    "de-fiperly-fiperly": {
      "url": "https://www.fiperly.de/mcp.php"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "de-fiperly-fiperly": {
      "type": "http",
      "url": "https://www.fiperly.de/mcp.php"
    }
  }
}
```

### Codex

```toml
[mcp_servers.de-fiperly-fiperly]
url = "https://www.fiperly.de/mcp.php"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "de-fiperly-fiperly": {
      "type": "remote",
      "url": "https://www.fiperly.de/mcp.php",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add de-fiperly-fiperly --url 'https://www.fiperly.de/mcp.php' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  de-fiperly-fiperly:
    url: "https://www.fiperly.de/mcp.php"
```

### Netclaw

```json
{
  "McpServers": {
    "de-fiperly-fiperly": {
      "Transport": "http",
      "Url": "https://www.fiperly.de/mcp.php"
    }
  }
}
```

### Vellum

```bash
assistant mcp add de-fiperly-fiperly -t streamable-http -u 'https://www.fiperly.de/mcp.php'
```

### Other

```json
{
  "mcpServers": {
    "de-fiperly-fiperly": {
      "type": "http",
      "url": "https://www.fiperly.de/mcp.php"
    }
  }
}
```

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-21 (score 68, +1)

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

### 2026-11-20 (score 67, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-19 (score 67, +34)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [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: fair
- [functional] First check of Destructive annotations: pass
- [functional] First check of Tool coverage: 25
- [functional] First check of Schema quality: pass

### 2026-11-06 (score 33, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-03 (score 33)

First indexed and scored.

## MCP tools (5)

### `fiperly_info` (~41 tokens)

About Fiperly

Who Fiperly is: independent AI development in Germany. Analysis of AI, work and the economy, websites for businesses, Agent-Ready, book.

### `leistungen_und_preise` (~77 tokens)

Website services and fixed prices

Fixed-price website packages for car repair shops and trades, estate agents, and the Agent-Ready audit for mid-sized companies, with what is included. Optional: lang (de|en), branche (werkstatt|makler|pruefung).

Input parameters:

- `branche` (string)
- `lang` (string)

### `analysen` (~45 tokens)

Fiperly analyses on AI, work and economy

Topic pages (kipode.de) on AI, jobs of the future, labour market, economy, robotics, energy in Germany. Optional: query.

Input parameters:

- `query` (string)

### `kontakt` (~34 tokens)

Contact Fiperly

Phone, WhatsApp, email, booking link for a 30-minute call and the free website check form. Does not send anything.

### `website_pruefen` (~150 tokens)

Check a website (Agent-Ready quick check)

Free instant Agent-Ready check of any public website, answers in German. Two scores: Grundlagen 0-100 (can ChatGPT, Claude, Perplexity and Google find, read and understand the site today: HTTPS, robots.txt for AI crawlers, Schema.org, readable without JavaScript, sitemap, llms.txt, title/description/contact, speed, bot protection) and Zukunft 0-100 plus level 0-5 (Cloudflare agent-readiness scan, isitagentready.com). Returns gaps, top tips and a result page link. Takes up to 60 seconds. Required: url.

Input parameters:

- `url` (string, required): Website address, e.g. www.example.de

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/de-fiperly-fiperly/mcp-php#diagnostics

## Score history

- 2026-11-21: 68
- 2026-11-20: 67
- 2026-11-19: 67
- 2026-11-18: 33
- 2026-11-17: 33
- 2026-11-16: 33
- 2026-11-15: 33
- 2026-11-14: 33
- 2026-11-13: 33
- 2026-11-12: 33
- 2026-11-11: 33
- 2026-11-10: 33
- 2026-11-09: 33
- 2026-11-08: 33
- 2026-11-07: 33
- 2026-11-06: 33
- 2026-11-05: 33
- 2026-11-04: 33
- 2026-11-03: 33

## Common questions

### What is the Fiperly MCP server?

Fiperly is an MCP server listed in the public MCP registry as de.fiperly/fiperly. Fiperly: AI websites, Agent-Ready, KI-Gedaechtnis, talks and the book on AI. Read-only. This page covers its hosted endpoint (https://www.fiperly.de/mcp.php).

### Is the Fiperly MCP server safe to use?

Fiperly scores 68 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 Fiperly MCP server expose?

Fiperly exposes 5 tools: fiperly_info, leistungen_und_preise, analysen, kontakt, website_pruefen. Their descriptions and schemas cost roughly 347 tokens of context every time the server is loaded.

### Does the Fiperly MCP server require authentication?

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

### Is the Fiperly MCP server still maintained?

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

### What did VerifyMCP test on the Fiperly MCP server?

VerifyMCP ran 13 checks on Fiperly, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.fiperly.de/mcp.php
- Website: https://www.fiperly.de/
- Changelog RSS feed: https://verifymcp.io/servers/de-fiperly-fiperly/mcp-php.xml
- Changelog JSON feed: https://verifymcp.io/servers/de-fiperly-fiperly/mcp-php/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/de-fiperly-fiperly/mcp-php.json
- HTML version of this page: https://verifymcp.io/servers/de-fiperly-fiperly/mcp-php
