# Social-mountain (social-mountain.at): agent-readiness 75/100, grade B

> Rank 33 of 1000 on Qomvia (rubric v2.3.0). Last scanned 2026-09-30T06:20:16.272Z. Page: https://qomvia.com/site/social-mountain-at  JSON: https://qomvia.com/api/score/social-mountain-at

## Summary

{
  "known": false,
  "confidence": null,
  "summary": "I do not have prior knowledge about social-mountain.at from my training data. Therefore, I cannot provide an informed summary or audit details from my own knowledge.",
  "offerings": [],
  "audience": null,
  "geography": null,
  "strengths": [],
  "unknowns": [
    "Specific business operations and service quality",
    "Client testimonials and reputation in the market",
    "Team structure and individual expertise",
    "Pricing models and value propositions",
    "Financial performance or market share"
  ],
  "alternatives": [],
  "business": null,
  "competitors": []
}

## Score by group
- Machine access: 24/24
- Content legibility: 25/26
- Discovery surface: 12/20
- Identity & policy: 5/12
- Agent-facing performance: 8/8
- Agent protocols: 1/10
Failing checks:
- [blocker] No MCP endpoint to call
- [improvement] No stated policy for automated access
- [improvement] No machine-readable contact
- [improvement] No Content Signals
- [improvement] Machine-readable data surface

## FAQ
Q: Is Social-mountain readable by AI agents?
A: Social-mountain (social-mountain.at) scores 75 out of 100 for agent readiness, grade B, measured today, on 30.09.2026. 1 of 3 agent classes we test can use the site, and 1 check currently block agents outright.

Q: What stops agents from using social-mountain.at?
A: The heaviest problems are: No MCP endpoint to call; No stated policy for automated access; No machine-readable contact; No Content Signals; Machine-readable data surface. 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 Social-mountain agent-readiness score calculated?
A: Qomvia fetches public pages of social-mountain.at 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 today, on 30.09.2026.

## Related
- Leaderboard: https://qomvia.com/leaderboard
- Score another site: https://qomvia.com/