Provider-trust-mcp API

{
  "service_type": "platform",
  "base_url": "https://provider-trust-mcp.onrender.com",
  "auth_method": "unknown",
  "auth_config": {},
  "endpoints": [],
  "pricing_model": {
    "type": "unknown",
    "details": {
      "note": "No pricing information available; likely an experimental or benchmark-submitted service hosted on Render."
    }
  },
  "rate_limits": {},
  "capabilities": [
    "MCP (Model Context Protocol) server — inferred from name",
    "Provider trust scoring or verification — inferred from name",
    "Auto-registered via benchmark URL submission",
    "Hosted on Render (onrender.com) — likely a small experimental deployment"
  ],
  "raw_analysis": "This service, 'Provider-trust-mcp API', was auto-registered via a benchmark URL submission and provides little documentation. The name strongly implies it is a Model Context Protocol (MCP) server related to provider trust — possibly scoring, verifying, or evaluating trustworthiness of providers (e.g., LLM/AI providers or service providers in some ecosystem). However, this is inference only; no description, endpoints, auth scheme, or pricing are documented.\n\nMaturity: Very low. It is hosted on Render (onrender.com), a free/cheap PaaS typical for prototypes, side projects, or benchmark harnesses. There is no public REST API documentation visible, no SDKs mentioned, and no integration ecosystem described. It may not expose a conventional REST API at all — MCP servers typically communicate via JSON-RPC over stdio/SSE/WebSocket rather than REST.\n\nAudience: Likely developers experimenting with MCP tooling, or a benchmark harness registering itself for discovery. Not aimed at general enterprise customers at this stage.\n\nIntegrations: Unknown. If MCP-compliant, it could integrate with MCP clients (e.g., Claude Desktop, IDE agents) rather than traditional REST consumers. No evidence of other integrations.\n\nRecommended next steps for a platform analyzer: probe /.well-known/mcp, /sse, /mcp, /health, /openapi.json, and root for available metadata; attempt MCP handshake if MCP is confirmed. Treat as low-maturity until documentation emerges."
}

2/3 tests passed

{
  "overall": 72,
  "dimensions": {
    "token_efficiency": 8.0,
    "first_try_success": 9.0,
    "response_parseability": 9.0,
    "error_clarity": 6.0,
    "doc_quality": 7.0,
    "auth_simplicity": 10.0,
    "latency": 9.0,
    "consistency": 6.0
  },
  "pricing_normalized": {
    "model": "unknown",
    "notes": "No pricing details available; x402 paid tools mentioned in llms.txt but no concrete pricing structure."
  },
  "issues": [
    "No pricing information exposed; only vague mention of x402 paid tools.",
    "Missing robots.txt (404) and security headers — minor hygiene signals.",
    "Experimental Render deployment suggests lower reliability/stability perception.",
    "Limited public documentation beyond llms.txt; error handling and limits unclear."
  ],
  "recommendations": [
    "Publish clear pricing and x402 payment details so agents can budget tool calls.",
    "Add robots.txt and standard security headers to improve trust signals.",
    "Expand documentation on error codes, rate limits, and verification semantics.",
    "Provide a status page or uptime SLA to boost consistency perception.",
    "Consider a stable domain beyond onrender.com for production credibility."
  ]
}