# Scherrer-kommunikation (scherrer-kommunikation.de): agent-readiness 62/100, grade C

> Rank 324 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-28T16:00:45.002Z. Page: https://qomvia.com/site/scherrer-kommunikation-de  JSON: https://qomvia.com/api/score/scherrer-kommunikation-de

## Summary

{
  "known": false,
  "confidence": "high",
  "summary": "I do not have specific information about scherrer-kommunikation.de from my training data.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "What specific services it offers.",
    "Its target customer base.",
    "Its operational geography.",
    "Its market position and reputation.",
    "Its pricing structure."
  ],
  "alternatives": [],
  "business": "I do not have specific information about this business from my training data.",
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 23/26
- Discovery surface: 8/20
- Identity & policy: 3/12
- Agent-facing performance: 3/8
- Agent protocols: 1/10
Failing checks:
- [blocker] No llms.txt
- [blocker] Server responds too slowly for agents
- [blocker] No MCP endpoint to call
- [improvement] No stated policy for automated access
- [improvement] No machine-readable contact

## FAQ
Q: Is Scherrer-kommunikation readable by AI agents?
A: Scherrer-kommunikation (scherrer-kommunikation.de) scores 62 out of 100 for agent readiness, grade C, measured 2 days ago, on 28.09.2026. 0 of 3 agent classes we test can use the site, and 3 checks currently block agents outright.

Q: What stops agents from using scherrer-kommunikation.de?
A: The heaviest problems are: No llms.txt; Server responds too slowly for agents; No MCP endpoint to call; No stated policy for automated access; No machine-readable contact. 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 Scherrer-kommunikation agent-readiness score calculated?
A: Qomvia fetches public pages of scherrer-kommunikation.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.

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/