# Joppnet (joppnet.de): agent-readiness 57/100, grade D > Rank 499 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T12:00:46.130Z. Page: https://qomvia.com/site/joppnet-de JSON: https://qomvia.com/api/score/joppnet-de ## Summary { "known": false, "confidence": "low", "summary": "I do not have specific information about joppnet.de within my knowledge base.", "offerings": [], "audience": null, "geography": null, "strengths": [], "unknowns": [ "Specific details about their services and product offerings beyond generic categories.", "Their target clientele, market positioning, and operational history.", "Any unique selling propositions, competitive advantages, or client testimonials.", "Their geographical focus beyond general industry presence.", "The scale of their operations or typical project size." ], "alternatives": [], "business": null, "competitors": [] } ## Score by group - Machine access: 24/24 - Content legibility: 23/26 - Discovery surface: 5/20 - Identity & policy: 0/12 - Agent-facing performance: 5/8 - Agent protocols: 0/10 Failing checks: - [blocker] No llms.txt - [blocker] The site does not say who it is - [blocker] No API or feed to read - [blocker] No MCP endpoint to call - [improvement] No stated policy for automated access ## Add-on packs - E-commerce & product feeds: 15/100 (not part of the public score) ## FAQ Q: Is Joppnet readable by AI agents? A: Joppnet (joppnet.de) scores 57 out of 100 for agent readiness, grade D, measured 2 days ago, on 28.09.2026. 0 of 3 agent classes we test can use the site, and 4 checks currently block agents outright. Q: What stops agents from using joppnet.de? A: The heaviest problems are: No llms.txt; The site does not say who it is; No API or feed to read; No MCP endpoint to call; No stated policy for automated access. Each one is scored from a public HTTP response, and the fix for each is listed in the signed-in report. Q: How is the Joppnet agent-readiness score calculated? A: Qomvia fetches public pages of joppnet.de as an AI agent would and runs the core checks every site gets across 6 groups: Machine access, Content legibility, Discovery surface, Identity & policy, Agent-facing performance, Agent protocols. Checks are weighted by how much an agent loses when they fail, and the score is expressed out of 100. E-commerce & product feeds checks are scored separately (15/100) and do not affect the public score or rank. Q: How often is this score updated? A: Public scores are re-checked when the site is re-scanned; tracked domains are re-scanned weekly and their owners are alerted when a check regresses. This page shows the scan from 2 days ago, on 28.09.2026. ## Related - Leaderboard: https://qomvia.com/leaderboard - Score another site: https://qomvia.com/