Fiperly
REMOTE · WWW.FIPERLY.DE
Fiperly: AI websites, Agent-Ready, KI-Gedaechtnis, talks and the book on AI. Read-only.
Available components
Last scanned (17 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 403 tokens (~80/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 25% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 20 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 19 Nov 26 +34
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Nov 26 33
First indexed and scored.
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 21 Nov 2026 · Probed https://www.fiperly.de/mcp.php
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fiperly.de | CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB | 5 Oct 2026 | 3 Apr 2027 | RSA 2048 | SHA256-RSA | afcf80d3da65f2a8080d4f528679db83 |
| SANs: fiperly.de, www.fiperly.de | ||||||
| CN=Sectigo Public Server Authentication CA DV R36,O=Sectigo Limited,C=GB (CA) | CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB | 22 Mar 2021 | 21 Mar 2036 | RSA 3072 | SHA384-RSA | 397a66cc2756362e0daa87ca6eabe3b1 |
| CN=Sectigo Public Server Authentication Root R46,O=Sectigo Limited,C=GB (CA) | CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US | 22 Mar 2021 | 18 Jan 2038 | RSA 4096 | SHA384-RSA | d27fbbc1de359e5216ad6149586099c4 |
| CN=USERTrust RSA Certification Authority,O=The USERTRUST Network,L=Jersey City,ST=New Jersey,C=US (CA) | CN=AAA Certificate Services,O=Comodo CA Limited,L=Salford,ST=Greater Manchester,C=GB | 12 Mar 2019 | 31 Dec 2028 | RSA 4096 | SHA384-RSA | 3972443af922b751d7d36c10dd313595 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.fiperly.de. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| de. | DS published | 26755 | 8 | Verified |
| fiperly.de. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.fiperly.de/mcp.php | Verified | 200 | |
| http (plaintext) | http://www.fiperly.de/mcp.php | HTTPS enforced | 301 | https://www.fiperly.de/mcp.php |
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 →
analysen Fiperly analyses on AI, work and economy ~45
Topic pages (kipode.de) on AI, jobs of the future, labour market, economy, robotics, energy in Germany. Optional: query.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
No output schema declared.
No examples provided.
fiperly_info About Fiperly ~41
Who Fiperly is: independent AI development in Germany. Analysis of AI, work and the economy, websites for businesses, Agent-Ready, book.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
kontakt Contact Fiperly ~34
Phone, WhatsApp, email, booking link for a 30-minute call and the free website check form. Does not send anything.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
leistungen_und_preise Website services and fixed prices ~77
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).
| Name | Type | Req | Description |
|---|---|---|---|
| branche | string | – | – |
| lang | string | – | – |
No output schema declared.
No examples provided.
website_pruefen Check a website (Agent-Ready quick check) ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Website address, e.g. www.example.de |
No output schema declared.
No examples provided.
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.
remote · www.fiperly.de
claude mcp add --transport http de-fiperly-fiperly 'https://www.fiperly.de/mcp.php'
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.